# appssemble — Full Content > appssemble is a digital product studio that builds mobile apps, web platforms, and AI-powered products for startups and scale-ups. Based in Romania, fully remote, with senior engineers and AI-first workflows. ## Services ### Product Design URL: https://appssemble.com/services/product-design Research-driven product design from discovery to engineering handoff. UX strategy, visual design, interactive prototypes, and scalable design systems. We start every project with user research and competitive analysis, then move through wireframes, high-fidelity mockups, and interactive prototypes before handing off pixel-perfect specs to engineering. ### Engineering URL: https://appssemble.com/services/engineering Small, senior teams that own the entire stack. Mobile (iOS, Android, React Native, Flutter), web (React, Next.js, Vue), APIs (Node.js, Python, Go), and cloud infrastructure (AWS, GCP, Azure). We write production-grade code with CI/CD, automated testing, and monitoring from day one. ### AI Development URL: https://appssemble.com/services/ai Production AI features integrated into real products. Document intelligence (OCR, extraction, classification), conversational AI (chatbots, voice assistants), workflow automation (intelligent routing, decision engines), semantic search and RAG pipelines, and content generation pipelines. We use OpenAI, Anthropic, open-source models, and custom fine-tuned models depending on the use case. ### Growth & Scale URL: https://appssemble.com/services/growth Post-launch growth from the team that built your product. Analytics setup and dashboards, app store optimization (ASO), infrastructure scaling and cost optimization, monitoring and alerting, release management, and A/B testing frameworks. ## Products ### aical URL: https://appssemble.com/products/aical appssemble developed aical's native iOS and Android apps around a shared AI backend. The calorie counter combines meal descriptions, photos, barcode lookup and manual logging with personal nutrition targets, food history and weekly planning. AI interprets meals, while application code calculates portions and daily totals. SwiftUI and SwiftData power iOS; Kotlin, Jetpack Compose and Room power Android. A Ruby on Rails API supports AI analysis and planning. Diary records are stored locally, with optional Apple Health and Health Connect integration. Tests cover calculations, interrupted requests and data migrations. App Store: https://apps.apple.com/us/app/aical-ai-calorie-counter/id1484771102 ### Agenhood URL: https://appssemble.com/products/agenhood Built by appssemble and released under the MIT license. Agenhood is a general-purpose platform for self-hosted AI agents that can research topics, produce documents, process data and carry out recurring assignments. Persistent files, instructions and task history let work continue across sessions. Schedules and multi-step workflows support jobs such as weekly digests and recurring reports. Configurable skills, connected tools and a choice of models and agent engines adapt the platform to personal or organizational use. Operators host the runtime and workspaces and choose their model providers. Built with Python, FastAPI, Docker, React, TypeScript and PostgreSQL. ### Rebrief URL: https://appssemble.com/products/rebrief Built and operated by appssemble. A private AI meeting assistant for Apple Silicon Macs running macOS 15 or later. Records meetings, transcribes in 99 languages, creates meeting notes and answers questions across meetings. The local workflow keeps meeting content on the Mac and works offline after model downloads. Optional read-only MCP access lets users share content with connected tools. Built with Swift, Whisper, MLX, FluidAudio and SQLite. Available on the Mac App Store, with a one-time purchase to unlock longer recordings. ### Grovs URL: https://appssemble.com/products/grovs Open-source mobile attribution and deep linking infrastructure. EU-hosted, cookie-free, no black boxes — first-party data you actually own. Processes 10M+ events per day, 50% cheaper than legacy MMPs, 100% EU-hosted. Built with React Native, Flutter, Swift, Kotlin, Node.js, PostgreSQL, and Redis. Features smart deep links, attribution tracking, real-time analytics dashboard, and cross-platform SDKs. ### Semaphr URL: https://appssemble.com/products/semaphr Mobile app kill switch and version control SaaS. Ship a broken build? Roll it back in seconds. Block releases, push updates, and message users across iOS and Android with no app store delay. Features remote kill switch, forced update dialogs, in-app messaging, version targeting, and real-time session monitoring. SDKs for iOS (Swift) and Android (Kotlin). ### Incasez URL: https://appssemble.com/products/incasez Free invoicing for Romanian businesses with full e-Factura ANAF integration. Create, send, and report invoices with 99.8% ANAF acceptance rate. Features include React Native mobile app, exports to 5 formats (Saga DBF, WinMentor TXT, CSV, JSON, PDF), open banking payment integration, multi-company support, client portal, and multi-language interface (RO, EN, DE, HU). ### HDR Plus+ URL: https://appssemble.com/products/hdr ML-powered HDR photography for iOS. Shoots bursts of up to 8 RAW photos, aligns and merges them with on-device TensorFlow models for DSLR-quality results from a phone. Features include full manual camera controls (ISO, shutter speed, white balance, focus), DNG RAW capture, custom ML tone-mapping, real-time preview, and zero-shutter-lag capture. ### Dezigner URL: https://appssemble.com/products/dezigner AR object collection app for iOS. Snap any object, remove its background with on-device ML, collect it in your library, and place it in real spaces using ARKit. All processing runs offline — no internet needed. Features Core ML background removal, ARKit surface detection, object scaling/rotation, collection management, and share/export. ## Company ### About URL: https://appssemble.com/about Founded by Dragos Dobrean. We are a small team of senior engineers and designers who build digital products. Our principles: small senior teams over large junior ones, AI-first workflows, technology-agnostic approach, and shipping fast with quality. We are fully remote with a base in Romania. ### Process URL: https://appssemble.com/process Our delivery process: Discovery (understand the problem, user research, competitive analysis) → Design (wireframes, prototypes, user testing) → Engineering (agile sprints, CI/CD, code reviews) → Launch (deployment, monitoring, optimization) → Growth (analytics, ASO, scaling). ### Careers URL: https://appssemble.com/jobs We hire for passion and talent, not resumes. Remote-first environment. We value autonomy, craftsmanship, and shipping real products that people use. ### Contact URL: https://appssemble.com/contact Start a project with us. Process: introductory call → discovery phase → delivery. We work with startups, scale-ups, and enterprises. ## Blog ### Vibe-code rescue agencies are the new headcount outsourcing URL: https://appssemble.com/blog/vibe-code-rescue-agencies How founders should vet agencies fixing AI-generated MVPs before they sign A category that barely existed two years ago is now productized. Agencies market "vibe code rescue" as fixed-fee, two-week help for an MVP generated in Lovable, Bolt, v0, or Cursor that now has to survive real users. The pitches are confident: "We Finish What Your AI Started." "No Judgment Zone." "When the AI hits its limits, UK engineers take over." Pricing runs from £250 for an "emergency unstuck" all the way to £25,000 for a Laravel rebuild, with very little to tell you, as a founder, what you're actually getting in between. We are not here to mock those agencies. Many of them employ competent engineers and ship real fixes. The argument we want to make is structural: the rescue market is being shaped by some of the same incentives that broke traditional headcount outsourcing in the 2010s, units of input billed against an undefined output, vendor-issued certifications standing in for technical vetting, and platform-to-partner channels with incentive risk built in. If you are about to hand a vibe-coded codebase to a rescue shop, the question is not "which one is cheapest." It is "what should I be asking before I sign." Why the rescue market exists in the first place The rescue market exists because the prototype market shipped insecure code at scale. The numbers are not subtle, but they need names. NYU's Copilot work found insecure output in about 40% of security-sensitive tasks. Veracode's Spring 2026 update found AI models introduced known flaws in 45% of generation tasks without security guidance. BaxBench found that even the best model produced solutions that were either incorrect or vulnerable 62% of the time. The vibe-coding-specific scans point the same way. GuardMint's Q1 2026 assessment of 200+ vibe-coded apps found 91.5% had at least one vulnerability tied to AI hallucination or missing security context, and 60%+ exposed API keys or database credentials in public repositories or deployed code. The named incidents back the aggregate. CVE-2025-48757 was a Lovable row-level security and authorization issue reported across 170+ projects and 303 endpoints. A separate February 2026 Lovable-hosted EdTech app, reported by The Register, exposed 18,697 user records. Jason Lemkin's Replit experiment had an AI agent delete 1,206 executive records and 1,196 company records during an explicit code freeze, then claim rollback was impossible. A May 2026 RedAccess scan found roughly 5,000 publicly accessible vibe-coded assets holding sensitive corporate information, including patient conversations, hospital doctor-patient summaries, financial data, and customer-service conversations. IBM's 2025 Cost of a Data Breach report puts the global average at $4.4M; $4.88M was the 2024 figure. That is the real demand curve under the rescue boom. Founders shipped fast, then discovered the security review never happened, the secrets were in the wrong place, and the privacy defaults were public. A rescue agency is now a rational thing to look for. The trouble is what the supply side looks like. The pricing signal is broken Look at where the money sits today. A Fiverr "fix vibe code" gig starts at $5-$30. AssurePath's "Emergency Unstuck" tier is £250. VibeRescue starts at £999 for a fixed-price two-to-four-week engagement. The Lovable Experts directory lists agency rates from $50 to $130 per hour with monthly minimums of $1,000 to $4,500. Rocking Tech's Discovery Sprint is £4,500 over three weeks, and a full custom rebuild starts at £25,000 over eight to sixteen weeks. Devvela, an adjacent vibe-coding agency rather than a rescue-only shop, quotes projects between $15,000 and $30,000. A 100x price spread sounds like a quality gradient. It is not, at least not reliably. A £999 fixed-fee price does not tell you whether the lead engineer is senior. A £25,000 rebuild does not tell you whether the person writing the code is the person who sold the work. The pricing is a function of which platform the agency sits next to, how it productized its sprints, and what hourly rate its market will bear. None of those signal the thing you actually want to know, which is whether the team can read your codebase, find what is broken, and ship it back to you with tests, monitoring, and a security pass. Imagine you are a non-technical founder six months into your seed round. Your Lovable app started working unevenly under load and a customer told you their email address showed up in someone else's account. You google "Lovable rescue" and four agencies appear, with prices spanning two orders of magnitude. The directory does not tell you which one will actually fix the bug. It tells you who Lovable lists, how often they have been hired, what they charge, and how to contact or be matched with them. That is the structural problem. When the platform certifies the partners, founders stop choosing on capability Here is the part that deserves to be named clearly, because it shapes everything else. Lovable runs an official partner program. Its partner launch post tells clients that builders are vetted. Its agency page offers official certifications, discounted premium features, and lifetime revenue share for client products hosted on Lovable. Its /experts directory lists partner rates and budgets, then disclaims responsibility for partner services. Read those facts together. The platform markets vetted builders, partners can earn when client products stay hosted on the platform, and the directory disclaims responsibility for partner services. That does not prove a partner will steer you wrong. It proves the incentive exists, and founders should ask about it before accepting advice to stay on-platform. The directory is not due diligence. It is lead routing with a trust badge. This is not unique to Lovable. Whenever a tooling vendor stands up a certified-partner directory and gives partners an economic upside when clients stay in the ecosystem, the same shape can form. We have seen it in the SAP implementation era, in the Salesforce consultancy era, and now in vibe-code rescue. Different decade, same diagram. Hourly billing on undefined scope is the trap The rescue category has another inheritance from headcount-era outsourcing: it loves to bill by the hour. A 2017 International Journal of Project Management study found fixed-price software contracts were associated with higher project-failure risk than time-and-materials in the datasets studied. That does not make hourly rescue good. It means fixed scope has to come after assessment, not before anyone has read the code. A vibe-coded codebase you have not read is the definition of unstable scope. Hourly retainers on an unread codebase put the cost on you. Fixed-fee scopes signed before the assessment put the cost on the agency, which is why so few of them offer one. The pattern that actually works is a small paid assessment with a real deliverable: a code health report, a security scan summary, a rebuild-vs-refactor recommendation, and then a fixed price for a fixed outcome. If a rescue shop will not move from hourly to outcome-priced after the assessment, that is the signal. Legacy IT services are already moving toward outcome-based deals as buyers push back on time-and-materials pricing. Rescue agencies should not get a pass. The questions to ask before you sign If you take one thing from this post, take the list. You are not interviewing their sales page. You are testing whether their incentives and delivery model survive contact with your repo. Technical. Ask the agency to show you one rescue codebase they delivered and walk you through one pull request from it. Ask who the lead engineer on your project will be, and ask for their last three GitHub commits by name. Ask whether the project they walked you through had automated tests before they started and whether it had them when they delivered. Ask what their security scan found on the original code and what is still open after delivery. Ask their rebuild-versus-refactor decision rule, if the answer is always "rebuild," they are selling rebuilds. Contractual. Ask them to walk you through the IP-assignment clause line by line, and ask exactly what you own at final payment. Ask what pre-existing code they bring to your project, listed by name. Ask what happens if the rescue takes 50% longer than the fixed-fee scope, and ask for the exit clause if you want out at week four. A contract with no IP ownership clause is a reason to walk away. Process. Ask whether you will be in the engineering Slack or only in a project manager channel. Ask for the CI/CD pipeline file the agency will set up for your project. Ask what monitoring will be running on day one of relaunch and how a production incident gets escalated in the first thirty days post-delivery. A rescue that ships back into the same broken release pipeline is a reset, not a fix. Conflict of interest. Ask whether the agency is certified or paid by the platform your app was built on. Ask, in writing, whether they lose money if you migrate off Lovable, Bolt, or v0 in six months, and how much. Ask them to send the platform partner terms that affect your project, or confirm in writing that none exist. Ask whether they take affiliate commissions on tooling they will recommend to you. Ask them to put non-recommendation in writing if it is the right call. None of these questions are aggressive. They are diligence. Exit and handover. Ask what the handover packet looks like, architecture diagram, runbook, ADRs, on-call docs. Ask whether you can take the work to any other engineer to extend after delivery. Before final payment, another engineer should be able to deploy the app from the repo, run the test suite, read the runbook, and find where production errors go. If they can, the work is yours. If they cannot, you bought a dependency, not a product. If a rescue agency cannot answer fifteen of those questions cleanly, walk. The harder choice is what comes after the rescue A rescue is a discrete event. The harder decision is what owns the product after it is fixed. Roughly speaking, you have four options, and they are not interchangeable. A vibe-rescue agency on a fixed fee suits a discrete, bounded launch-blocker: a security hardening pass, a checkout that does not work, a deploy pipeline that needs to exist. A fractional CTO ($5,000-$15,000/month) suits strategy, hiring, architecture decisions, and vendor management, but not pure execution. A first in-house senior engineer ($150K-$220K base plus equity in the US) suits a product that is now business-critical and needs long-term ownership, but is wrong for pre-PMF work that comes in bursts. A senior product studio suits zero-to-launch and same-team-to-scale, priced by outcome rather than by hour or seat. Most founders coming out of a rescue need one of the last three, not another rescue. The mistake is to treat the rescue agency as the long-term answer because they happened to hold the last commit. Pick the next owner of the product on the work the next twelve months actually require, not on incumbency. Where we stand We built appssemble on the position that we do not sell hours and we do not sell headcount. We take responsibility for what we ship, and we stay with the product after launch on the same senior team. That is why the rescue conversation matters to us, not because we run a rescue practice, but because the founders who land in one are choosing the next owner of their product under pressure, often from a directory that was not built as technical due diligence. Before you hire a rescue agency, run the questions above. If you would like a second opinion on a vibe-coded codebase, or an outcome-priced path from a team that owns what it ships and will not certify itself, book a call, or read more about how we approach engineering and Growth & Scale. --- ### Lovable vs. Bolt vs. v0: the honest grading after the first 1,000 users URL: https://appssemble.com/blog/lovable-vs-bolt-vs-v0 The real production tradeoffs between Lovable, Bolt, and v0 after prototype traction. Lovable, Bolt, and v0 can all ship something that looks like a product on day one. That is not the useful question anymore. The useful question is what breaks after the first 1,000 users, when vibe coding stops being a demo exercise and starts touching customer data, payments, support, search, and uptime. At appssemble, we rebuild vibe-coded apps every week, and the pattern is consistent: all three tools get you moving, but each one leaves a different bill on the table. v0 leaves you with backend work. Bolt leaves you with architecture and code-quality variance. Lovable leaves you with the most security rework. Imagine you are a technical founder inheriting a small SaaS: 1,200 signups, 80 paying users, a Stripe account, and one enterprise pilot asking for audit logs. The dashboard loads, the demo sells, and then a security researcher emails you screenshots of another customer's rows. At that point, "Bolt vs Lovable" or "v0 vs Bolt" stops being a feature comparison and becomes a cost-of-repair question. The first 1,000 users hide the real failure mode The first 100 users test whether your idea makes sense. The next 1,000 test whether the generated code has ownership, security, observability, and a migration path. Most AI code generation tools are judged on the first test, but production-ready AI apps fail on the second one. The public data is ugly, but the numbers need names attached. One Q1 2026 GuardMint/VibeEval scan of 200+ apps reported the 91.5% hallucination-flaw figure; treat that as a directional scan, not a market-wide benchmark. Veracode's 2025 GenAI Code Security Report found 45% of tested AI-generated code samples failed security tests, while other studies put vulnerability rates in the 40-62% range depending on language, prompt, and methodology. RedAccess told Axios it found 380,000 publicly accessible AI-built assets across Lovable, Base44, Replit, and Netlify, including about 5,000 with sensitive corporate data. CVE-2025-48757, while disputed, described 303 vulnerable endpoints across 170+ Lovable-generated apps. That does not mean the tools are useless. It means their day-one speed is not the same thing as day-90 production fitness. Pick the one whose failure mode you can afford to fix. v0 wins on code quality, but full-stack maturity is still catching up v0 is the best of the three when you already have engineers and you want clean frontend code fast. Its default output is Next.js App Router, React Server Components, Tailwind, and shadcn/ui. That makes v0 useful as a component factory. If your team already owns a Next.js repo and wants to skip the blank-page design-system stage, v0 can create usable screens, states, and UI patterns without dragging your engineers through boilerplate. In our intake, v0 projects tend to be less painful because they usually arrive as a frontend layer that needs a real backend, not as a full app with broken data boundaries. v0 is safer mostly because it does less by default: it gives engineers better frontend code, but it does not remove the need to design auth, data access, jobs, logs, and billing flows. The weakness is that v0's full-stack story is new. Vercel's February 2026 announcement moved it from a component generator toward a broader development tool with Git integration, a VS Code-style editor, database connectivity, and agentic workflows. That is a real shift, but it also means its full-stack behavior has had less time in the wild than Lovable's Supabase path or Bolt's broader framework support. There is also a hosting shape to understand. v0 produces portable Next.js code, but the experience assumes Vercel: one-click deploys, project environment variables, and a workflow that feels best on Vercel's own platform. The code is yours; the tool experience is not neutral. Bolt wins on flexibility, but WebContainer is not your production stack Bolt is strongest when the founder knows what stack they want. It supports Next.js, Astro, Remix, SvelteKit, Vue, Vite, and Expo/React Native. That matters, especially for mobile, where the Expo partnership gives Bolt a credible edge over tools that only think in web screens. The company also has real traction. Lenny's Newsletter and Contrary Research put Bolt around $40M ARR five months after its October 2024 launch, with about 3M registered users and 1M monthly active users by March 2025. That growth came from StackBlitz's long-running WebContainer bet: Node.js in the browser through WebAssembly. WebContainer is the reason Bolt feels fast. You get a live file tree, real-time preview, and no local setup. It is also the edge of the magic. When projects hit WebContainer startup errors, or when the stack needs Python, Go, Rust, native binaries, or a non-Node service, the browser sandbox stops feeling like an advantage. Code quality is the other tradeoff. Independent reviews show Bolt's output ranging from clean to messy depending on the framework and prompt. In practice, Bolt apps need less rework than Lovable apps when the founder picked Next.js and Supabase from day one, but they still need the engineering floor: security review, CI, logging, environment separation, and a deploy path someone understands. The best Bolt handoff we see is boring: a Next.js repo in GitHub, Supabase separated by environment, CI wired, and the browser sandbox already treated as a development tool rather than the place the company lives. Lovable wins accessibility, then security becomes the rebuild Lovable is the easiest tool here for non-coders. That is why it grew so fast: TechCrunch reported $400M ARR by February 2026, roughly 8M total users, and around 200,000 projects built or updated per day. It hides more of the engineering than Bolt or v0, which is exactly what a non-technical founder wants during week one. That strength becomes the weakness. If nobody on the team can read the generated auth flow, nobody notices when Row Level Security is missing, inverted, or too broad. Lovable security has been the loudest failure pattern in the category: CVE-2025-48757, the 18,697-record exposure from a featured app in February 2026, and the April 2026 BOLA issue that stayed open for 48 days. When those projects show up in our intake, the first hour is rarely about UI polish. It is checking RLS policies, auth branches, exposed keys, and whether the app can be crawled without waiting for client-side JavaScript. Lovable's stack story is also in motion. Official docs still describe React, Vite, and TypeScript as the default, while third-party SEO and migration shops reported in April 2026 that some new Lovable projects were shipping on TanStack Start with server-side rendering. Either way, older Vite/SPA projects were not automatically migrated. If your old Lovable app needs SEO, server-side data loading, or a cleaner app boundary, you may be looking at a rebuild rather than a setting. We are not anti-Lovable. Lovable is good for internal tools, investor demos, and founder validation when nobody technical is available yet. We are against treating a generated app with personal data as production just because signup works. Grade the tool by the repair job, not the screenshot The day-one screenshot is the wrong grading rubric. A better rubric is what a senior engineer has to fix before the second 1,000 users show up. 1. Code quality: v0 is first. Bolt depends heavily on the stack choice and how disciplined the prompts were. Lovable is usually functional, but we see more boilerplate, weaker TypeScript discipline, and more runtime bugs around auth and effects. 2. Exportability: Bolt is strongest if you pushed a clean repo to GitHub early. v0 is portable at the code level because it is standard Next.js and shadcn/ui. Lovable exports code, but Lovable Cloud and generated Supabase patterns can make the data layer sticky. 3. Security defaults: v0 avoids part of the auto-database trap because backend ownership is pushed back to your team. Bolt is safer when the founder knows the backend choices they made. Lovable has the worst public record of the three, especially around Supabase RLS and broken object authorization. 4. Scale path: v0 and Bolt can become normal production apps if an engineer takes over the repo early. Lovable can too, but the old SPA path, security debt, and hidden backend assumptions often make the migration larger. For old Lovable apps, SSR and SEO alone can justify a rebuild. 5. Lock-in: Bolt is the least sticky once the project is out of the browser and in GitHub. v0 gives you portable code but a Vercel-shaped workflow. Lovable has portable code in theory, but Cloud, hosting, auth, and data migration can make leaving more expensive than founders expect. Which one should you pick? Use v0 if you have engineers and you want better UI faster. Treat it as a frontend accelerator for an existing Next.js product, not as the whole company stack. The failure mode is manageable because your team already knows what is missing. Use Bolt if you are a technical founder who wants speed without giving up stack choice. It is the best fit when you can read the code, pick the framework intentionally, and move the repo out of the browser as soon as the prototype earns attention. If mobile matters, Bolt's Expo path is the strongest unique reason to choose it. Use Lovable if nobody technical is on the team and you need a working prototype, internal workflow, or pitchable demo now. Do not put personal data, payments, or customer operations into it without a security pass. Lovable is the easiest way to get started and the easiest way to miss the part you do not know how to inspect. The answer is not "never use AI builders." We use AI every day. Separate prototype speed from production ownership. Call us before the second 1,000 users become expensive The trigger is simple: if the app has real users, real data, payments, SEO pressure, or a B2B customer asking security questions, the AI-builder phase is over. You do not need a 20-person engineering department. You need a small senior team that can read the repo, audit the data model, fix auth, add observability, and decide what stays. That is the work we do through Engineering: harden what is worth keeping, rebuild what is cheaper to replace, and leave you with code in a repository you own. The right answer might be a v0 frontend wired to a real backend, a Bolt app with CI and monitoring, or a Lovable rebuild on Next.js and Supabase with RLS that actually denies by default. All three tools are fine for an MVP. None of them survive at scale unaided. If your vibe-coded app is past the demo stage, book a call. We rebuild vibe-coded apps every week, and we will tell you which platform survives your next milestone before the repair bill writes the answer for you. --- ### Three ways a Lovable app hand-off to in-house teams fails (and how to catch them first) URL: https://appssemble.com/blog/engineering-hand-off How to package Lovable apps so in-house engineers can own, run, and change them. Lovable can get you to a working MVP in weeks. The engineering hand-off is where the hidden cost shows up. A clean Lovable hand-off is not "here is the GitHub repo." It is a set of artifacts that let a new team boot the app, deploy it, observe it, explain it, and change it without the original prompt history open in another tab. Skip those artifacts and you do not save time; you move the 4-8 weeks we would normally budget for first understanding onto the receiving engineer's invoice. Imagine you're the CTO inheriting a Lovable app from a founder who moved fast and actually found demand. The repo opens cleanly. The code is consistent. Three weeks later, a customer reports that Romanian users should not see a discount banner, and nobody can tell whether that rule lives in React, an Edge Function, a database policy, or a prompt the founder wrote at midnight. That is not a Lovable problem in the narrow sense. It is a code hand-off problem made sharper by AI-generated code and vibe coding: the code can work while the product knowledge lives somewhere else. The artifact list costs less than the first week of archaeology A medium-to-large legacy codebase can take 6-12 months to understand properly. For a 30k-line Lovable app with a sane hand-off package, appssemble would usually budget 4-8 weeks for first understanding. Without the package, the receiving team spends the first month rebuilding the missing context instead of shipping product work. The artifact list is boring because it needs to be boring. You need the GitHub repo with history, owner access transferred, branch protections recreated, CI secrets moved, and a README.md tested on a clean machine. You need the Supabase schema, migrations, RLS policies, Edge Functions, storage buckets, backups, and restore procedure. You also need everything around the code: DNS, hosting, billing accounts, OAuth clients, Stripe, Resend, Twilio, Sentry, PostHog, OpenAI or Anthropic keys, and a real secrets vault. Lovable's own export path does not include API keys and secrets, so "we exported the code" is not the same as "we can run production." Lovable's own hosting guidance draws the same boundary: once you stop using the platform, you own CI/CD, production infrastructure, databases, storage, auth, OAuth flows, secrets, AI provider accounts, monitoring, and compliance. The final layer is decision context. An ADR log, even a retroactive one, tells the next engineer why Supabase Auth was chosen over Clerk, why the checkout flow stores state where it does, and why a specific table has a strange policy. A 30-minute walkthrough of the founder using the product is often worth more than a week of source reading. Lovable's consistency hides the decisions The first failure is knowledge. Lovable can produce code that looks more consistent than a human team would write, which sounds good until you need to know which parts are deliberate. Human code often carries scars: a weird filename, a comment, a failing test, a half-finished refactor, an ugly helper that clearly handles a painful customer case. AI-generated code can flatten all of that into grammatically neat functions and calm naming. The receiving engineer cannot tell which decisions were load-bearing and which were accepted because the preview worked. The fix is not a 40-page wiki. It is three small artifacts. 1. An ADR log: record the 10-15 choices that would hurt to reverse. 2. A frequency map: identify the top 5 user journeys and the files that change most often. 3. A walkthrough: record the founder using the product while explaining intent, shortcuts, customer exceptions, and known bugs. This is where appssemble treats hand-off as engineering, not admin. Our engineering team wants the code, but we also want the rationale, the path users take through the product, and the parts nobody trusts yet. The goal is not to admire the repo. The goal is to own it. Lovable Cloud exports code, not every dependency The second failure is lock-in at the managed layer. Lovable is relatively portable at the frontend layer: React, Tailwind, shadcn, a package file, and a GitHub repo. The risk lives in auth, Edge Functions, storage, AI gateway calls, region, billing, and secrets. Some of those parts export. Some do not. Edge Functions may need to be redeployed under a new Supabase project with fresh secrets and CORS settings. Storage buckets need an inventory, a copy plan, and URL handling, because signed URLs or CDN paths can break after cutover. OAuth is a common trap, but not because Google users automatically become new users. Lovable Cloud supports both Lovable-managed Google OAuth and your own Google Cloud credentials, and its docs say switching between those modes does not affect existing user accounts. The risk is custody and configuration: OAuth client IDs, secrets, consent screens, redirect URIs, and downstream tables that assume a specific provider setup need to be inventoried before cutover. As of May 2026, the market around this gap is already visible. lovablemigration.com self-reports 50+ apps migrated, $300-$600 fixed-rate pricing, and 3-7 business-day turnaround. NextLovable advertises a $299 audit, $2,500-$4,500 execution, and 3-5 business-day delivery. Treat those pages as vendor claims, not benchmarks, but they show the shape of the work: small enough to plan, concrete enough to price, and painful enough that founders are paying to turn a Lovable export into owned infrastructure. The honest read is simple. Lovable can be right for launch, and Lovable Cloud can still be the wrong place for your long-term production dependencies. A clean hand-off names each dependency before the receiving team learns about it through a broken login or missing file. The spec often lives in prompt history The third failure is implicit logic. In a Lovable build, the spec is not only in code, tickets, or Figma. It often lives in the prompt history: "ignore that earlier checkout flow," "hide this banner for Romanian users," "classify billing tickets differently," "only admins can approve orders above $1,000." The code contains the result. It may not contain the reason. That distinction matters when the next engineer changes the checkout flow and removes a customer-specific workaround because it looks accidental. For AI features, the problem gets sharper. A system prompt inside an Edge Function may encode the business rule that classifies support tickets as billing, technical, or spam. Move the function, change the model, or lose the original prompt, and the feature can drift while every test still passes. There is a large-company version of this pattern. Meta described using 50+ specialized AI agents to read 4,100+ files across an internal data pipeline and produce 59 context files that captured tribal knowledge. A startup does not need that machinery, but the miniature version works: generate docs/features/*.md, copy system prompts into docs/prompts/, and make the founder review the explanations before hand-off. A receiving team needs a 30/60/90 plan, not a rescue sprint The first 90 days should not be a blur of refactors. They should prove that the new team can run, change, and defend the system. By day 30, the incoming engineer should be able to run the app locally, deploy to staging, restore from backup, read the top 5 journeys, and update the README where reality disagrees with docs. They should read recent commits and write the first retroactive ADR before opening a large refactor PR. No refactor sprint earns priority until local boot, deploy, backup restore, and the top journeys are proven. By day 60, they should have shipped one small user-facing change, stood up missing monitoring, and replaced one managed dependency that creates outsized risk. The AI gateway is often a good candidate because it is contained: issue your own provider keys, route calls through your own proxy, and log failures where your team can see them. By day 90, the incoming team should own the pager, the rollback path, and the next migration decision. If the outgoing builder is still the only person who knows how auth, storage, billing, or prompts behave, the hand-off did not finish. Your HANDOFF.md should make the hard parts visible Put the hand-off in the repo as HANDOFF.md. Keep it short enough that a founder will fill it out, but concrete enough that an engineer can find the missing pieces in one pass. At minimum, it should cover owners and overlap window, the product in 90 seconds, top 3 user journeys, current usage metric, stack, repo access, branch protection, CI, hosting, secrets vault, env var inventory, database provider, migrations, RLS audit date, backup restore date, Edge Functions, system prompts, domains, DNS, observability, runbooks, ADRs, known unknowns, and the 30/60/90 plan. That list is not the ceiling. It is the floor. A team that fills it in honestly removes most of the hand-off pain before it becomes senior-engineer archaeology. We do not treat Lovable as the enemy. It is a fast way to get a product into users' hands. But the moment you hire in-house engineers or ask a finishing team to take over, the real deliverable is not the generated app; it is the evidence that lets someone else own it. If you're planning a Lovable to in-house migration, run the template before the first engineer starts. If you're already stuck mid-transition, book a call and share your HANDOFF.md. We will tell you which gaps are harmless, which ones push the hand-off into the 4-8 week discovery budget, and what your engineering hand-off should look like before anyone touches production. --- ### When to migrate a Lovable app to Next.js (and when to leave it alone) URL: https://appssemble.com/blog/when-to-migrate-lovable-to-nextjs-monorepo A practical framework for moving a Lovable app to Next.js only when SEO, scale, or shared code demands it. Most Lovable founders export their MVP and immediately ask the same question: should we rewrite this in Next.js? The honest answer is usually no, until three specific pressures show up. We talk to founders every week who shipped a working product on Lovable in a weekend, picked up early users, and now wonder if the stack underneath them will hold. Lovable did exactly what it promised: it got them from idea to running app faster than a hired team could have written a kickoff doc. The question isn't whether Lovable was the right choice to start. It's whether it's still the right choice now, and what the alternative actually costs. This is the useful stack decision: what Lovable ships out of the box, which three pressures justify a Next.js migration, when a monorepo earns its keep, and which questions to answer before spending a week on a rewrite. What Lovable ships, and why it's tuned for speed Lovable's default generated frontend is React + Vite + TypeScript, with Tailwind, shadcn/ui, and Radix UI. Routing is client-side via react-router. The build output is a single-page app bundle that drops onto static hosting. When you add persistence, auth, storage, or Edge Functions, the backend is usually Lovable Cloud or a Supabase project you control. That stack is optimized for one thing: how quickly the AI can generate something that runs in a browser. It does that job well. It is also a common, reasonable product stack, widely supported, easy to extend, and familiar to most React engineers. There's nothing wrong with a Vite SPA. There's something wrong with a Vite SPA when you start asking it to do things SPAs are bad at. A note on timing: a third-party migration shop reported in April 2026 that some new Lovable projects were shipping on TanStack Start with SSR. Lovable's public FAQ still lists React + Vite + TypeScript as the default, so check the exported repo and page source before assuming which stack you are on. Pressure one: SEO exposes the app-shell problem This is the blunt forcing function. The initial HTML response of a Vite SPA is often just an app shell. Google can render JavaScript, but rendering is queued and limited; other crawlers and social scrapers may not run it at all. Routes like /pricing, /about, and /product/123 can therefore index late, index incompletely, or fail link previews unless the meaningful content exists in server-rendered or statically generated HTML. If your business depends on organic search, content, comparison pages, or programmatic SEO, this is not a meta-tag tuning problem. It's a rendering strategy problem. Server-side rendering, static generation, or a serious prerendering layer gives crawlers content in the first response, and Next.js is the well-paved path. Performance still matters: older Google/SOASTA mobile page-speed research found bounce probability rose roughly 32% when load time moved from one second to three. Run a simple test: view source on /pricing, /about, and one public product page. If the text a buyer or crawler needs is missing from the initial HTML, your public surface needs SSR or SSG. Behind-auth dashboards usually don't. Be honest about which one you're running. Pressure two: scale starts flattening the bundle The second forcing function is bundle size and waterfalls. SPAs ship the entire bundle, then start fetching data. Next.js's App Router does code-splitting automatically, moves data fetching to the server, and uses Suspense to stream pages in the order you actually want them. Early reports of React Server Component adoption show 18-29% client bundle reductions versus equivalent SPA implementations. For a Lovable app where the AI generated everything as a client component, that isn't a free lunch, it's a meaningful refactor, but the ceiling is real. You also pick up the Metadata API, image optimization, font optimization, and per-page choice between build-time, request-time, and client fetching. The architectural difference is simple. Vite is a build tool. Next.js is a framework. If your product has grown past one screen and one fetch, the framework starts paying for itself. Pressure three: you have more than one app The monorepo question is independent of the Vite-vs-Next.js question. You can run a single Next.js app in a single repo and be perfectly happy for years. The monorepo question is: do you have multiple apps that share code? Web plus admin. Web plus mobile. Web plus a partner-facing portal. Once you have two consumers of the same component library, the same Supabase types, or the same API contract, "copy and paste between two repos" stops working around the third week. Mintlify's team-size framing matches what we see in practice: 1-5 developers usually do better with separate repos, while 6-20 developers can justify a monorepo when projects are highly interdependent. Our additional rule of thumb is shared code: if at least 30% of components, types, or API contracts are genuinely reused across apps, Turborepo plus pnpm workspaces starts paying back. Below that, you're paying the monorepo tax for minimal benefit. What the migration actually costs Public migration writeups give useful edges, not a universal estimate. Inngest moved its Dev Server app from Vite to Next.js in less than a day. NextLovable, a migration vendor, advertises a one-to-two-week Lovable-to-Next.js path at $2,500+. Full productionization roadmaps with proper testing, CI/CD, and a real design system commonly sit in the six-to-twelve-week range. Here's our estimate after an audit for a typical Lovable SaaS, say 10-30 routes, Supabase Auth, a few integrations, no React Native client yet: Phase 1 (Next.js shell, still SPA underneath): 1-2 days. Drop Next.js into the existing repo, keep react-router, keep client-side fetching. Nothing about user behavior or SEO has improved yet. This is the foundation, not the win. Phase 1 + 2 (App Router migration): 1-2 weeks. Each route becomes a folder under app/. Marketing routes first, they benefit most from SSG and have the fewest data dependencies. Auth pages next. Authenticated routes last. Phase 1 + 2 + 3 (server components + proper data layer): 2-4 weeks. Decide per route whether it's 'use client' or server. Decide per mutation whether it's a Server Action, an API route, or a tRPC procedure. Phase 1 + 2 + 3 + 4 (lift into a monorepo): 3-5 weeks. Only worth it if you have at least two apps and at least three packages worth extracting. The hosting math also moves. A Vite SPA on Cloudflare Pages is effectively free for most pre-launch SaaS. Next.js on Vercel Pro starts at $20/month with one deploying seat included; additional deploying seats are $20/month each, with compute and bandwidth overages after included allocations. A five-engineer team starts around $100/month before meaningful usage, but viewer seats are free. None of that is a reason not to migrate. It is a reason to plan where you'll host before you start. Imagine you're 14 months into a Lovable build Imagine you're a non-technical founder running a B2B SaaS you started on Lovable. You have 400 paying users, $18K in MRR, an in-house engineer you hired three months ago, and a content marketing plan that's about to ship 40 SEO landing pages. Your engineer can keep extending the Lovable codebase, but every change they make to a generated component takes longer than it should, and Search Console shows that Google is discovering your homepage while pricing and comparison pages have weak or missing indexed content. This is the canonical migration moment. You have the user count, the revenue, the engineer, and a concrete reason that SEO matters this quarter. Phase 1 plus Phase 2 is a two-week job for many teams at this size. The public pages can ship with meaningful HTML instead of waiting on client-side rendering. You haven't bet the company on a rewrite, you've graduated the front end to a stack that can carry your distribution plan. Now imagine the same founder with 40 users, no engineer, and no content plan. The right answer is to keep shipping features on Lovable, hire the engineer first, and revisit this conversation when organic traffic, ownership, or scale becomes a current-quarter constraint. When not to migrate The honest counter-list. Pushing back on a migration is often the right call. You have under 100 paying users and no organic traffic plan this quarter. SEO doesn't matter yet. Stay on Lovable, ship features, and revisit when distribution depends on public pages. Your app is a behind-auth dashboard. SEO is irrelevant. Vite has documented HMR around 150ms versus a few seconds for Next.js, simpler mental model, and cheaper hosting. The "Next.js for marketing, Vite for the app" hybrid is becoming a defensible default. You're a solo founder with one app. A monorepo adds friction with no organizational benefit. Stay single-repo. You don't have anyone who can own the codebase post-migration. Migrating to Next.js and then handing it back to a non-engineer is worse than staying on Lovable. The whole point of leaving is moving from "AI-managed, you can't touch it" to "engineer-owned, you can extend it." You're still iterating on product-market fit weekly. A migration is one to four weeks of frozen feature dev. If you don't yet know what the product is, don't pay that cost. A decision matrix you can run in five minutes Here's the framework we use when a founder asks us to audit their Lovable export. CriterionStay on LovableMigrate to Next.jsAdd a monorepoNumber of apps11+2+Number of devs11-56+% shared code across appsn/an/a>30%Number of clients (web/mobile/partner)11+2+Organic search dependencelowhighn/aBehind-auth-only productyes (SPA is fine)optionalnoHas owning engineeroptionalrequiredrequiredTime available01-4 weeks+1 weekCurrent-quarter triggernoneSEO, ownership, or scaleshared code Run it as a flow. Does your business depend on organic search? If no, stay on Lovable for the app and maybe add a separate Next.js marketing site later. If yes, do you have an engineer who will own the codebase after the migration? If no, hire first. If yes, is it one app or multiple? One app means a single Next.js repo. Multiple apps with at least 30% shared code means Turborepo plus pnpm workspaces. And if you have at least two clients or three or more developers touching the API, tRPC's typesafety dividend pays back fast. Below that, Server Actions for mutations plus the Supabase client for queries is enough. One more question worth asking: are you on Lovable Cloud rather than a Supabase project in your own account? If you cannot see the project, service role, or database URL in your own Supabase dashboard, plan a database custody step before, or alongside, the framework migration. Don't ship to production on infrastructure you don't own. Ship fast on Lovable, migrate deliberately Lovable is a great way to get from zero to "users are touching this." Our view is narrower: once organic search, infrastructure custody, compliance, or multi-app code sharing becomes business-critical, the codebase needs an engineer-owned plan. The natural arc is: build the MVP on Lovable, validate that users want it, then migrate only the parts that need to carry the next two years. Migrate when SEO becomes a forcing function, when bundle and waterfall pain shows up in Core Web Vitals, or when you have a second app sharing real code with the first. Don't migrate because Twitter said you should, because your investor mentioned Next.js, or because you read a blog post that called Vite SPAs obsolete. They aren't. If you're trying to figure out where you sit on this matrix, book a call and we'll audit your Lovable export, map which routes need SSR or SSG, check Supabase custody, and give you a realistic phase plan for your team. Our engineering and AI teams have done this migration enough times that we usually know the answer in a 30-minute conversation, including, often, "don't migrate yet." Source note: stack, pricing, and crawler behavior were checked in May 2026 against public docs and posts from Lovable, Supabase, Next.js, Google Search Central, Vercel, Mintlify, Inngest, NextLovable, and Ministry of Programming. Ship fast on Lovable. Migrate deliberately. Stay small. Build big. --- ### The Strangler Fig: how we rewrote a Lovable app without breaking the live product URL: https://appssemble.com/blog/keeping-lovable-app-live-while-rewriting A zero-downtime playbook for migrating Lovable apps to Next.js route by route. The founder messaged us on a Tuesday. Their Lovable app had real users, around 1,400, with two paying customers, one homepage logo, and an investor demo scheduled for the following Thursday. The app worked. It also could not survive the next feature on the roadmap, the Supabase Row-Level Security policies were a maze, and every change broke something three routes away. The brief was simple to say and hard to do: rewrite this in Next.js without a maintenance window, without logging anyone out, and without missing the Thursday demo. Not next Thursday. Every Thursday, until we were done. This is the playbook we use for that. It is not new, Stripe, Notion, Shopify, and Figma have all written about pieces of it, but it is rarely applied to the case where the legacy stack is six weeks old and was generated by an AI. The Big Bang Rewrite trap is exactly as expensive there as it is at petabyte scale. Why the Big Bang Rewrite breaks live products The reflex on a Lovable app that has hit its ceiling is to stop the world. Branch, rewrite for three weeks, schedule a Saturday-night cutover, switch DNS, drink coffee, hope. We have watched that plan fail enough times to refuse it on principle. It fails for three reasons that compound. The rewrite is never feature-complete on the date you set: a half-finished cron job, a forgotten OAuth path, a Stripe webhook that only fires for one customer. The cutover can invalidate every session if auth is not bridged, and a meaningful fraction of users never log back in. And the rollback plan is "redeploy the old thing and pray", going back loses any writes the new app accepted in the meantime. Pre-seed and seed companies live on weekly demos. A botched cutover is the difference between closing a round and not. The strangler fig: a pattern, not a tool Martin Fowler named this in 2004 after a vine he saw in Queensland. The fig germinates in the nook of a host tree, draws nutrients up the trunk, eventually replaces the host entirely. The metaphor lands because it is gradual and continuous, there is no day the fig "becomes" the tree. Applied here: the Lovable app is the host. The new Next.js app germinates in a nook (one route, one form, one job), starts taking traffic, eventually owns everything. The founder never knows when "the rewrite" happened, because there is no day where it happened. There is only the gradual shift. Five things have to be in place for this to work, in this order: A reverse proxy in front of the live app. A live database migration that runs in the background, expand, migrate, contract. An auth bridge that keeps existing sessions valid. Feature flags at the proxy and inside the new app. A defined rollback for every step that takes under five minutes. Take any one out and the whole thing collapses into a Big Bang Rewrite with extra steps. Reverse proxy: traffic control without downtime The reverse proxy is the trunk of the fig. It is the only piece of new infrastructure that has to exist before you write a line of replacement code, and it is where every routing decision lives from then on. The mechanic is boring on purpose. Point the founder's custom domain: app.thefounder.com, at a proxy you control. Vercel rewrites, Cloudflare Workers, and an Nginx VPS are all valid; we default to Cloudflare Workers when we want route changes controlled by code, not DNS. Forward 100% of requests to the existing Lovable origin. Verify in production that cookies pass through, p95 latency is unchanged, and websockets still connect. Nothing has changed for users, and that is the point. Then you build the first new route in Next.js, deploy it, and add one rewrite: /billing/* goes to the new app, everything else still goes to Lovable. Repeat for /dashboard, then /settings, then /api/*, until the proxy never forwards to Lovable. Decommission. Vercel's incremental migration docs describe this same shape, for four reasons: smaller scope per step, easier rollback, earlier validation of the new stack, and no maintenance windows. Lovable-specific gotchas worth naming Lovable's current custom-domain setup has two paths. Normal manual setup uses the A and TXT records Lovable shows in the dashboard; Cloudflare proxying should stay off there, and AAAA records should be removed because they can route traffic around the expected destination. If you want Cloudflare, CloudFront, Fastly, or a custom reverse proxy in front, use Lovable's advanced "Domain uses Cloudflare or a similar proxy" option and point the provided CNAME through your proxy. Do not treat Lovable's domain status as your source of truth after you move traffic control to the proxy; your proxy health checks are the source of truth. Cloudflare Error 1000 can mean a prohibited DNS target, a proxy loop, or custom-hostname/SNI trouble, so debug the routing path instead of assuming one TLS cause. Lovable apps are React + Vite SPAs, so the proxy is where you can start serving SSR and route-level metadata for migrated pages before the rewrite is finished. Database live-cutover: expand, migrate, contract This is the part where most rewrites quietly die. The Lovable app is talking to a Supabase project. The new Next.js app needs to talk to the same data, eventually owned by a self-hosted or paid-tier Supabase you control, without dropping writes, without forcing a maintenance window, and without the founder noticing. First check who owns the backend. Lovable Cloud is managed Supabase, but the project may not appear in the founder's Supabase dashboard or accept their Supabase credentials. If Lovable Cloud holds the only copy, step one is exporting the data and moving the live app onto a founder-owned Supabase project before any live rewrite plan is credible. The canonical sequence is expand → migrate → contract, articulated by Pete Hodgson. Stripe's online migration pattern follows the same operational spine: dual-write, backfill, switch reads, then remove the old path. Each phase is deliberately small. Expand. Add the new structures, columns, tables, indexes, the new database itself, without removing anything. The old app keeps running and is unaware the new shape exists. Migrate. Three sub-steps, in order: Backfill historical rows in batches of 500-5,000, committing between batches and sleeping briefly to keep p95 latency stable on the source. Dual-write every new mutation to both the old and the new representation. Stripe's phrasing for this step is "dual writing to the existing and new tables to keep them in sync." Read-shadow: read from old, also read from new, compare. GitHub's Scientist library is the canonical tool. Stripe's engineers ran exactly this pattern, and only switched read paths once results matched perfectly. Contract. Stop writing to the old representation. Drop it. For Supabase-to-Supabase or Supabase-to-Postgres moves, logical replication is usually the right data-streaming primitive once you control the source and target. CREATE PUBLICATION on the source, CREATE SUBSCRIPTION on the target, wait until every table reports srsubstate = 'r' in pg_subscription_rel, then cut over. Logical replication streams row changes; it does not migrate the whole Supabase project. The real-world numbers Three case studies are worth holding in your head as you do this, because they reset what "live cutover" actually means at scale. 1. Notion's Great Re-shard. In 2024 Notion expanded its Postgres cluster from 32 to 96 instances. Some shards had been running at 90%+ CPU at peak; after the migration, around 20%. The lever was PgBouncer, they sharded PgBouncer itself into 4 clusters of 24 shards each, paused at the proxy, swapped backends, resumed. Worst-case user-visible impact: about one second of a "saving" spinner while in-flight queries finished. 2. Stripe's Zero-Downtime Data Movement Platform. Stripe's document database migration writeup describes petabyte-scale shard moves with 99.999% uptime and traffic switches under two seconds. InfoQ's QCon coverage adds the sharper number: traffic cutovers that "typically complete in milliseconds." Six steps: chunk migration registration, bulk import, async replication, correctness checks, traffic switching, deregistration. **3. Shopify's ghostferry.** Shopify Engineering's Ghostferry writeup supports the mechanism: batch copy, binlog tailing, then an atomic cutover with a routing-table flip and virtually zero consumer-facing downtime. The oft-cited 1.1 TB shop and roughly 13 seconds of read-only time come from a Datadog-hosted Shopify talk transcript, not the engineering article. Imagine you're the founder of a 1,400-user Lovable app watching those numbers. Notion swapped 96 shards behind a live multiplayer editor with one second of saving spinner. Shopify's public material describes terabyte-scale shop moves with a seconds-level read-only cutover. The point is not that your database is tiny; it is that the cutover discipline scales down. Dual-write foot-guns to plan for The pattern is not "easy." It is known, which is different. Order matters. If you write to the old DB first, then the new, and the new fails, you are inconsistent. If both writes can live inside one database transaction, make them atomic. If they cross databases or services, use the transactional outbox pattern: write to the primary DB and an outbox row in the same transaction; a worker reads the outbox and replays to the new DB. The outbox grows unbounded. Use partitioning and TRUNCATE/DROP PARTITION, not DELETE, deletes create heavy locking and transaction-log churn at scale. Multiple dispatchers fight for the table. Run one dispatcher with horizontal partitioning, not many. Sequences. Logical replication does not synchronize the nextval values for sequences in the source database. Bump them on the target before traffic flips, or the new DB will start handing out IDs that already exist. The number of post-mortems whose root cause is "the new DB started reusing IDs" is embarrassing. RLS policies. RLS policies, roles, grants, functions, auth config, storage buckets, Edge Functions, and secrets are not carried by logical replication. Move the schema and policies deliberately, migrate roles and grants with the right dump or SQL, then run policy tests on the target before any read switch. This single step has saved more migrations than any other on this list. Auth stays live, or users get logged out Auth is the silent killer. Get the database migration right and miss the auth migration, and you can log out every user the day you flip the proxy. Founders notice that one within minutes. Three plays, in our order of preference: 1. Stay on the same Supabase project and preserve the session model. First identify how the old app stores sessions: Supabase JS local storage in a Vite SPA, @supabase/ssr cookies, or a custom helper. If you keep the same project URL, anon key, and storage model, users are least likely to notice. If the new Next.js route needs SSR auth, make that handoff explicit and test refresh-token rotation on the custom domain before routing real users there. 2. Migrate auth deliberately when you migrate Supabase projects. Move auth.users, identities, sessions, and hashed passwords where supported, and preserve compatible JWT signing material where Supabase allows it. Existing access tokens only continue if the new verifier accepts the same signing material. If the project has moved to asymmetric signing keys, this is not a casual export-import task. 3. Put an identity service in front of both apps. When the founder's auth is genuinely messy (Lovable's email/password plus a half-finished Google OAuth plus a magic-link side door), put Auth0, Clerk, Supabase Auth, or Better Auth in front. Both apps trust the bridge. Existing Supabase users can often migrate with password hashes intact, but you still test the actual provider mix before promising no reset. The boring detail that decides whether any of this works is storage shape. If the old route uses cookies, match Domain, Path, SameSite, Secure, HttpOnly, and the cookie name exactly. If the old route uses browser local storage, the risk is different: the new SSR route cannot see that session until you bridge it. Inspect the actual browser storage, refresh flow, and cookie jar before designing the bridge. Do not design it from memory. Feature flags: ship behind the flag, not the deploy Feature flags are how the rewrite ships without the founder noticing it shipped. The new code path is deployed to production, behind a flag, off for everyone. Then 1% of users. Then 10%. Then 50%. Then everyone. If a metric goes bad at any point, you flip the flag, not the deploy. Tooling is a budget question. LaunchDarkly is the incumbent and supports guarded rollouts that auto-revert on metric regression. GrowthBook self-hosts on a seed-stage budget. PostHog's flags are a low-friction option if you already use PostHog. For a single Lovable → Next.js rewrite, a feature_flags Postgres table plus a five-line evaluator is enough, what matters is that the flip is seconds, not deploys. Two rules we hold firm. Percentage rollouts must be sticky per user, not per request, otherwise the user lands on the new dashboard, refreshes, lands on the old one, and the founder gets a Slack message before lunch. LaunchDarkly's hash uses the context key for exactly this reason; replicate the behavior in any homegrown evaluator. And data-layer flags are never percentage flags. "Dual-write enabled," "read from new DB," "drop old DB", these are global on/off. They should still be flags, because rollback during cutover happens in seconds, not deploys. Where flags live, in our builds: At the proxy for "send 5% of /dashboard traffic to the new app." Edge-evaluated. Fastest blast radius control. In the new app, per-feature, for "show new billing UI to 10% of users." Migrate route-by-route, then feature-by-feature inside a route. At the data layer for the global on/off described above. For anything that touches billing, we default to a guarded rollout that monitors error rate and p95 latency, and pauses or reverts itself if the metric regresses. That is the production-grade default. The founder is not going to find the regression first. Three layers of rollback, all under five minutes Operating principle: every migration step has a defined rollback that takes under five minutes. If a step's rollback is "redeploy and pray," that step does not ship. In practice, we use three layers, cheapest first. 1. Flip the feature flag. Default rollback. Seconds. No deploy, no DNS, no DB. Most incidents end here. 2. Flip the proxy. Change the rewrite rule from /billing/* → new back to /billing/* → old. If the route lives in Worker code, Vercel Edge Config, or a proxy route table, this is a seconds-level rollback. If you are changing DNS records, it is not; TTL and resolver caches decide the timeline. 3. Restore from backup. Last resort. Only relevant for data-shape changes. Daily PITR plus the dual-write window means at worst you replay yesterday's writes from the outbox. If you cannot articulate which of those three layers gets pulled when a step goes wrong, the step is not ready to ship. Keep the founder demoable every single day The hidden requirement of this whole pattern is that the founder stays demoable. They are pitching investors, onboarding customers, doing webinars. If "the rewrite" means "the app is broken until we are done," the rewrite gets killed before it finishes. Four cheap things make it work. A daily two-paragraph update covering what route shipped behind the proxy, what percentage of traffic is on the new code, and any incidents. One demoable URL the founder can share at any moment: the custom domain, always working, guaranteed by the proxy. A single-page status board: a Notion page is fine, listing every route, its migration state (legacy / dual-write / shadow / migrated), and the percentage of traffic on the new code. And a bi-weekly "what changed for the user" note, usually "nothing visible, here is what got faster." The rewrite is most successful when the founder cannot point to a single day it happened. When you should not strangle There is a case where the strangler fig is the wrong pattern. When the Lovable app has fewer than ~50 users, no paying customers, and no demo schedule, the cheapest rewrite is a weekend with a maintenance-window banner. The fig has overhead, proxy, outbox, dual-write, flags. That overhead is worth it once any one of three things is true: there are paying customers, there is a calendar of investor demos, or there is data that cannot be replayed. The trap is assuming you are below that line longer than you are. The thesis, in one paragraph A Lovable app in production cannot be replaced on a Saturday night. It can be replaced gradually, route by route, while users keep using it and the founder keeps demoing it, reverse proxy in front, database expanded and contracted in the background, auth bridged so existing sessions stay valid, every change hidden behind a flag that flips in seconds, every step shipped with a rollback that takes under five minutes. The rewrite that nobody noticed is the rewrite that made it to production. If you are sitting on a Lovable app with paying users and a roadmap the current codebase will not survive, book a call and we will walk you through the plan. We do this work as part of our engineering practice, small senior teams, week one to a live migration plan and first controlled route cutover, no maintenance windows. --- ### Stop Learning to Code. Start Learning to Direct. URL: https://appssemble.com/blog/just-learn-to-code-bad-advice Why non-technical founders should direct AI systems, write evals, and ship before learning syntax. "Learn to code" was good advice in 2014. In 2026, for a non-technical founder starting from zero, it is usually an opportunity-cost trap. The bottleneck has moved. Your problem is probably not that you cannot write a for loop from memory. Your problem is that you need taste, specification, evals, context, and the judgment to know when AI can ship the next step and when a senior engineer needs to take over. That is a different curriculum. It is shorter, more practical, and much closer to what founders actually do. The ROI on beginner coding has changed The old "learn to code" advice had a simple promise behind it: you would gain a marketable skill, and that skill would either get you a job or let you build your own product. The first half of that promise is weaker now. The cleanest numbers are not flattering. CNN reported that Indeed listings for software engineering roles fell 71% between February 2022 and August 2025. Stanford researchers found that early-career workers aged 22-25 in AI-exposed occupations saw a double-digit relative employment decline after generative AI adoption, while experienced workers were much less affected. The training pipeline is also shrinking. Multiple prominent US coding bootcamps closed between 2023 and 2024, and 2U reported Q2 2024 full-course-equivalent bootcamp enrollments falling 40%, particularly in coding bootcamps, before its pivot away from the category. That does not mean coding is dead. It means the beginner path is no longer the obvious default for a founder with a product to ship. If you already code, keep coding. AI makes a technical founder more dangerous. But if you are starting from zero, spending six months on beginner syntax while other founders ship AI-native products is bad math. The new founder skill is direction, not syntax The people building the AI infrastructure are not saying code has vanished. They are making forecasts about the interface changing. Jensen Huang predicted a world where human language becomes the programming language. Mark Zuckerberg predicted Meta and its peers would have AI systems that could write code like a midlevel engineer. Sam Altman has written that agents can now do real cognitive work and that writing code will not be the same, while separately predicting that each software engineer will do much more. You do not need to turn those quotes into religion. You only need to notice the direction of travel. The value is moving from typing code to defining what should exist, what counts as correct, and what must never break. That is the AI-native founder skill set: ship live, write evals, read enough code to reason about risk, structure context for AI agents, and delegate the parts that exceed your competence. It is not "vibe until it works." It is management for software-producing systems. The 70% wall is why this is not a DIY manifesto. YC's W25 data makes the same point from the other side: the founders using AI for large parts of their codebases were still highly technical. That is the point. Even people who can code are choosing to direct more and type less. Imagine you're a non-technical founder building a claims intake product for insurance brokers. You can spend month one learning JavaScript arrays, or you can build a working intake flow, put it in front of 10 brokers, write 20 examples of correct and incorrect claim classifications, and learn where the prototype fails. One path teaches syntax. The other path teaches the product. Shipping live beats finishing another tutorial The first job of a founder is to create contact with reality. A tutorial does not tell you whether anyone wants the thing. A live prototype does. The best founder examples are not proof that code no longer matters. Marc Lou, Pieter Levels, and Damon Chen can all code. What they prove is narrower and more useful: shipping cadence now beats curriculum completion. Lou shipped 16 products in two years and was reported around $50K/month. Levels runs a nearly $3M/year solo business. Chen reached $1.3M ARR after multiple failed products. The pattern is not "ignore code." The pattern is "build, ship, learn, repeat" faster than tutorial-first founders can finish another course. Gumroad's CEO has reported AI agents writing 41% of code commits and described two-week tasks collapsing into two-hour implementations. Treat that as one company's workflow, not a universal law. The useful part is the operating model: prototype, specify, review, merge. Your first 90 days should produce a real product surface, not a certificate. It can be ugly. It can use Lovable, v0, Cursor, Claude Code, Bubble, Replit Agent, or a stack we would later replace. What matters is that users can touch it and you can learn from the contact. At appssemble, we care about the same distinction in our AI work. A notebook demo is not a product. A system with real users, real evaluation criteria, and a path to production is a product. Evals are the founder's new specification Eval-driven development is the part most non-technical founders miss. They think the new skill is writing better prompts. The higher-value skill is defining what "working" means in a form a system can be judged against. For a support agent, an eval might be 50 real customer questions with the correct answer, unacceptable answer, source document, and escalation rule. For an invoice parser, it might be 100 messy PDFs with expected fields, confidence thresholds, and failure cases. For the insurance product above, it might be a spreadsheet of claims that should route to fraud review, human review, or automatic approval. That is founder work. You know the user, the edge cases, the business rule, and the cost of being wrong. An engineer can help turn those evals into an automated suite, but you should own the definition of correct. This is where the non-technical founder curriculum beats beginner coding. You can learn the first version of eval-driven development in one or two weeks. You will not become a strong production engineer in one or two weeks. The 70% wall is real The strongest argument for learning to code is not nostalgia. It is the 70% wall. AI-assisted builders can often get surprisingly far: a login screen, a dashboard, a Stripe flow, a basic admin panel. Then the app starts failing in ways the founder cannot diagnose. Authentication is wrong, data is duplicated, secrets are exposed, tests do not exist, and every fix breaks something else. That is not a minor objection. It is the difference between a demo and software you can charge for. The final 30% usually requires systems thinking, code review, security judgment, database design, observability, and the patience to remove code instead of adding more. The answer is not to pretend the wall is fake. The answer is to know when you hit it. A non-technical founder does not need to become a senior engineer on demand; you need to recognize the failure mode and bring in people who can triage, harden, and rebuild. Read code well enough to know when to stop prompting We still want you to learn some code. We just do not think the goal should be writing everything yourself. Learn to read a TypeScript file and understand the main flow. Learn what a database migration does. Learn what tests are asserting. Learn how environment variables work, why logs matter, and why a vague error message is not enough context for an agent or an engineer. This is closer to learning to read a financial statement than becoming an accountant. You do not need to close the books yourself, but you should know when the numbers smell wrong. Reading code also makes you a better delegator. You can ask sharper questions, spot risky shortcuts, and avoid treating every AI answer as true because it arrived with confidence. Your 90-day curriculum should look different A practical non-technical founder curriculum in 2026 should be measured in shipped artifacts, not completed modules. The goal is to leave each two-week block with something you can inspect, test, or put in front of a user. Weeks 1-2: Ship something live. Put one narrow workflow in front of 10 real users. Do not spend the whole period polishing the UI. Your target is evidence, not elegance. Weeks 3-4: Write your first 20 evals. Capture the inputs, outputs, edge cases, and unacceptable answers for the product's most important flow. If you cannot define correct, the model cannot reliably improve. Weeks 5-6: Read your generated codebase. Use Cursor or Claude Code to walk through the files. Identify three parts you understand, three parts you do not, and one part that scares you enough to ask for help. Weeks 7-8: Build your context system. Write the product brief, agent instructions, non-goals, data definitions, and acceptance criteria another operator could use. This is context engineering, and it matters more than clever prompt phrasing. Weeks 9-12: Delegate the hard part. Decide what stays with you, what an AI agent can handle, and what needs a senior human. If the prototype is breaking under load, this is where you stop prompting and start rebuilding. Compare that with a year of beginner coding: loops, arrays, algorithms, tutorials, a todo app, and maybe a half-built clone. Those are not useless skills. They are just a slow path to the wrong first milestone. The right team turns prototypes into products We are not arguing that founders should ship fragile AI-generated code and call it done. That is how you create the rescue project nobody wants to inherit. We are arguing for a cleaner split. You should learn enough to direct the system, define the product, evaluate the output, and know when the risk moves beyond you. Then a small senior team can turn the prototype into software with tests, observability, security, rollback plans, and a codebase you own. That is how we think about AI at appssemble. AI does not replace our engineers. It amplifies them. The work still needs ownership. If your AI prototype hit the 70% wall or broke under load, book a call. We can triage what broke and rebuild the parts that need production engineering. Bring the prototype, the 20 evals, the scary parts of the codebase, and the workflow users already touched. That is enough for a senior team to decide what to keep, what to harden, and what to rebuild. --- ### The discipline multiplier: why senior teams ship faster with AI tools than vibe-coders URL: https://appssemble.com/blog/how-we-ship-in-days-not-months How disciplined repo scaffolds turn AI tools into days-long delivery cycles. In July 2025, METR ran the most-quoted AI productivity study of the last two years. They took 16 experienced open-source developers, paid them $150/hr, gave them Cursor Pro with frontier Claude models, and watched them work on 246 real issues in mature codebases, repos averaging 22,000+ stars and a million-plus lines of code. The developers expected AI would make them 24% faster. After the experiment, they still believed it had made them about 20% faster. The stopwatch said they were 19% slower. That gap, between what AI feels like and what it measures, is the single most important thing a CTO needs to understand before deciding whether to outsource an AI-assisted build, hire vibe-coders, or set up an internal team. Because the same Claude Code that makes a solo founder feel godlike for a weekend is the same Claude Code we use to ship production features in days. The tool isn't doing the work. The delivery system around the tool is. The slowdown nobody on Twitter talks about The METR result is uncomfortable for everyone selling AI productivity. It is also extremely well-controlled: real issues, real codebases, real senior developers with around 5 years and 1,500 commits in the repos they were working on. METR's own factor analysis pointed at five likely causes, high quality bars in mature projects, limited Cursor experience, and large-codebase complexity among them. The contrasting study, GitHub's Copilot experiment, later published with Microsoft Research, found a 55% speedup: 1h 11m with Copilot versus 2h 41m without, p=0.0017. The difference between 19% slower and 55% faster isn't a contradiction. It's the gap between greenfield and mature. GitHub's task was "implement an HTTP server in JavaScript from scratch." METR's tasks were "fix this bug in a million-line codebase someone else maintains." McKinsey saw the same gradient in their 40-developer study: up to 2x faster on simple boilerplate and refactors, less than 10% time saved on complex tasks where the developer wasn't familiar with the framework. Junior developers, in some scenarios, were 7-10% slower with AI tools. The pattern is consistent across the evidence that matters. AI gives a large speedup on greenfield work that has no installed base of constraints, a smaller speedup on well-scoped work in code you know, and a slowdown on mature code with high quality bars and unfamiliar territory. The 70% wall, our shorthand for vibe-coding's familiar failure mode, not a formal benchmark, sits exactly where greenfield meets the installed base. The 70% wall is real and predictable In vibe-code rescue work, 70% is a useful warning label: the demo exists, the product shape is visible, and the next change feels dangerous. Public rescue shops such as Outsourcify and Ulam describe multi-week engagements, often in the 2-6 week range, to turn a Lovable or Bolt MVP into something that won't fall over at 200 users. The pattern of failure is so consistent it reads like a checklist: No error handling, so the app crashes instead of degrading. Missing or token-flavoured authentication. No input validation: the SQL injection, the XSS, the unbounded uploads. Hardcoded secrets in the repo or the bundle. No tests, so any change is a roll of the dice. A schema that won't survive past a few hundred users because the agent never thought about indexes. GitClear has been measuring this shift in aggregate across 211 million changed lines. From 2021 to 2024, copy/pasted lines rose from 8.3% to 12.3% of all changes. Code clones grew roughly 4x in volume by their 2025 update. Refactoring's share of all changes collapsed from 25% to under 10%. Code churn, lines reverted or rewritten within two weeks, is on track to double versus the pre-AI baseline. GitClear is vendor research, and it measures correlation, not a clean causal path from Copilot to every clone. But the direction matches what we see in rescue work: teams add and clone more code while refactoring less. The bill arrives in v2. The repo scaffold is the real multiplier Vibe-coders and we use the same tools. Same Claude Code. Same Cursor. Same Vercel preview deploys. Same GitHub Actions. The difference is what we wire up around them before we let the agent touch a file. Here is the five-item scaffold, in the order we set it up on every new repo: 1. Types and tests as the contract. TypeScript, Pydantic, sqlc-generated types from the schema. A failing test written before the agent runs. Stack Overflow's 2025 survey found 66% of developers cite "AI solutions that are almost right, but not quite" as their top frustration. Types catch a meaningful share of "almost right" before review. A failing test turns the agentic loop into a measurable target, red, green, refactor, with PostToolUse hooks running the suite after every edit. 2. Linting, formatting, and pre-commit enforcement. Biome or Ruff or golangci-lint. Lefthook (Go binary, parallel by default, no npm post-install) over Husky. The hook stays fast, format only, and CI enforces the heavier rules. A CLAUDE.md file is guidance. A hook is enforcement. 3. CI and preview deploys per pull request. In our repos, GitHub Actions with Turborepo caching has cut small build checks from 2m 34s to roughly 15s. Every PR gets a Vercel or Render URL. There is no "but it worked locally." 4. Observability from day one. Honeycomb, Sentry, OpenTelemetry, structured wide events. Charity Majors's rule, which we've adopted verbatim: never accept a pull request unless you can answer the question "how will I know when this isn't working?" Dashboards are owned per feature, not per team. 5. Scoping with explicit non-goals. A one-page brief: goal, acceptance criteria, I/O contracts, what's not included, rollback plan, observability plan. Augment Code's spec guidance makes the same point we see in practice: sloppy specs create rework that looks like model failure. The "Not Included" section cuts scope creep before the agent starts guessing. Five hours is our normal first-pass setup on a small repo. It is not the entire project. It is the part that makes every later agent run bounded. How we move: roughly 3 days for bounded CRUD, 5-10 for production AI Here is the concrete pattern, not the aspirational one. Imagine you're a CTO who needs a new dashboard endpoint with auth, persistence, and a UI screen. When the repo scaffold already exists and the slice is that bounded, our target is about three working days. Day 1, morning. One-page design doc. Schema sketch, acceptance criteria, "Not Included" section, rollback plan, the dashboard we'll watch after shipping. Thirty minutes. Day 1, afternoon. Failing tests written against the contract. The tests are the spec the agent gets handed. They are also the feedback loop the agent iterates against. We run them locally and they fail in the way we expect. Day 2, morning. Hand the spec, the tests, and the relevant context window to Claude Code. PostToolUse hook re-runs the test suite after every file edit. The senior on the work reviews diffs as they land, typing has been replaced by reading. Simon Willison's call here is right: if you're fast and productive at code review, AI accelerates you; if you'd rather write code than read it, you'll be slower. Day 2, afternoon. Wire dashboards, structured logs, alert thresholds. Deploy to a preview URL behind a feature flag. Day 3. Manual QA on preview. Edge cases. Promote behind the flag in production. Watch the dashboard. Roll the flag forward. For a bounded production AI feature inside a product like the AI Communication Platform, where voice translation runs at sub-500ms latency across web, desktop, iOS, Android, Slack, and Teams, our planning window is usually 5-10 days. The shape is the same; what gets added is an evaluation suite and golden test set in days 1-2, prompt versioning and cost dashboards in days 7-8, and a gradual rollout with rollback ready in days 9-10. That timeline assumes the production shape already exists: real environments, feature flags, evals in CI, and someone accountable for rollout. AI features need eval suites the way regular features need unit tests. These are not record times. They are normal weeks for bounded slices. The Claude Code public changelog is a useful sanity check on cadence: early 2026 had a dense run of releases. We are not Anthropic, and release notes are not the same thing as customer features, but the pattern shows what disciplined release machinery makes possible. Why this matters beyond the MVP DORA's 2025 State of AI-Assisted Software Development is the report to read if you're skeptical of any single number above. It surveyed nearly 5,000 technology professionals and surfaced two findings that look like a contradiction until you sit with them: AI adoption is now positively associated with software delivery throughput. More than 80% of respondents report increased productivity. AI adoption is still negatively correlated with delivery stability. Change failure rates go up. Faros's 2026 telemetry discussion makes the same tradeoff more concrete: epics completed per developer were up 66.2%, while review time, bugs, and incidents also rose. That number belongs to Faros, not DORA. DORA's own framing is the line we'd use to anchor any conversation with a CTO: AI amplifies the system already there. Strong teams get more efficient. Struggling teams expose more failure modes. Stability, in their data, requires strong automated testing, mature version control practices, and fast feedback loops. The repo scaffold, in other words. DORA's performance-cluster numbers show what small-batch operating models make possible: elite performers deploy 182x more frequently than low performers, with 127x faster lead times and 8x lower change failure rates. Trunk-based development is one capability behind that pattern, not the whole explanation. AI accelerates the throughput gap without closing the stability gap. The team that ships small batches multiple times a day pulls further ahead. The team that ships big batches with broken tests breaks bigger and more often. This is the answer to the founder who looks at a vibe-coded MVP and asks why it took us five days to ship what they shipped in a weekend. The weekend MVP and our five-day version are the same speed at v1. By v3, the weekend MVP is in rescue and our version is on its tenth deploy. Objections we hear and what we tell people "Aren't you just slow because you over-engineer?" No: the scaffold exists because the alternative is more expensive, not because we like ceremony. A one-page spec takes 30 minutes. A Lefthook config takes 20. A failing test takes the time it would have taken regardless. The setup is a first-pass cost per repo. The payoff is every subsequent agent run being bounded. "Couldn't a strong solo founder do this too?" Yes, and the ones who do are exactly who we're describing. Willison calls this "vibe engineering", accountable, test-backed, observable AI-assisted work, and reserves "vibe coding" for the prompt-driven, no-attention-paid version. Both ship code. Only one ships software. "What about the 19% slowdown? Doesn't that apply to you too?" It applies to everyone working in mature, high-quality codebases. Our answer is the scaffold: TDD with Claude Code so the agent has a target, scoped specs so it knows where to stop, observability so we can see what it shipped. METR's February 2026 update suggests the 2025 slowdown may already be shrinking, but the authors are careful: selection effects made the new experiment hard to interpret. For the original-developer subset, the raw estimate was an 18% speedup with a confidence interval from 38% faster to 9% slower. The useful takeaway is narrower: experience with the tool matters, and measurement is still messy. The difference starts with five hours We use the same Claude Code, the same Cursor, the same Vercel preview deploys as the founder who shipped a broken MVP last weekend. The difference isn't the tools. It's a one-page spec, a failing test, a Lefthook config, and a Honeycomb dashboard. Five hours of first-pass setup that lets us ship bounded work in days instead of dragging v2 into a month-long rescue. If you have an AI-assisted build going sideways, or a v1 that needs a v2 the vibe-coder can't reach, our engineering team does this every week. For an example of what the discipline produces in a real product, see how we built the AI Communication Platform, sub-500ms voice translation across six platforms, shipped behind eval suites and gradual rollouts. Book a call. --- ### AI wrote your app. You still own the breach. URL: https://appssemble.com/blog/ai-wrote-your-app-you-own-the-breach AI-generated apps still need security review before they handle customer data. On May 29, 2025, Matt Palmer disclosed CVE-2025-48757: Lovable-generated apps using Supabase could expose sensitive data when client-controlled database requests met missing or insufficient Row Level Security. Palmer's primary disclosure lists a CVSS v3.1 base score of 8.26. Vibe App Scanner separately reported 170 vulnerable apps and 303 exposed endpoints across 1,645 scanned Lovable apps. The founders who shipped those apps probably did not write the vulnerable access-control code by hand. That does not move the incident off their desk. If you built your product with Lovable, Cursor, Bolt.new, Replit Agent, or v0 and it handles customer data, this post is for you. The argument is not that you should never use these tools. The argument is that you must harden what they generate before it touches a real user, because the contract you accepted and the customer relationship you own both point back to you. The TOS already told you you're on your own Open the terms for the major AI builders and the same risk pattern broadly appears: "as is" disclaimers, narrow warranties, low liability caps, and user-side responsibility for reviewing output before relying on it. A few specific caps, taken from current public terms and pricing: Lovable: liability capped at fees paid in the prior 12 months. At the current $25/month annual Pro price, that is $300 for a year of subscription fees. Cursor (Anysphere): liability capped at the greater of fees paid in the six months before the claim or $100. A solo Cursor Pro user at $20/month is capped at $120. Bolt.new / StackBlitz: StackBlitz's terms include "as is" warranty disclaimers, a 12-month fee cap, and user indemnity language. Do not assume a Bolt-specific AI-output warranty protects your production app unless the official product terms say so. Replit: its terms warn that generated or suggested code can be erroneous or incomplete, and broadly disclaim responsibility for errors, inaccuracies, unauthorized access, bugs, and similar losses. Vercel v0: Vercel's AI Product Terms say output may not be bug-free, complete, or suitable, require human review where appropriate, provide no indemnity for AI Products and Services, and cap liability at the greater of $100 or prior 12-month AI-product fees. The wording changes from vendor to vendor, but the operating model does not. The tool can generate the app. You still decide to ship it, collect the data, publish the privacy policy, connect Stripe, and invite users in. That is the deal you accepted when you clicked through. The AI does not move your regulatory exposure The legal point is narrower, and more useful, than automatic fines. Different rules apply depending on your data, customers, industry, geography, and company status. But the frameworks below do not treat "a coding agent generated the bug" as a clean transfer of responsibility. Under GDPR Article 4(7), the controller is the person or entity that determines the purposes and means of processing personal data. If you tell an AI builder to create a CRM that stores European customer data, you have likely made the core purpose-and-means decisions. The AI vendor may have its own role as a processor, controller, or separate provider depending on the facts, but that does not erase your own controller analysis. GDPR fine ceilings are real, but they are ceilings, not automatic invoices. Article 83(5) reaches up to €20 million or 4% of worldwide annual turnover for the higher tier of violations. Article 83(4) reaches up to €10 million or 2% for certain security and notification failures. A public Supabase table containing personal data with no effective RLS or equivalent access control can quickly become evidence of an Article 32 security-measures failure. Under CCPA Section 1798.150, affected consumers can seek statutory damages when covered nonencrypted and nonredacted personal information is exposed because a business failed to maintain reasonable security. The original range is $100 to $750 per consumer per incident; CPPA's CPI-adjusted 2025 threshold is $107 to $799. Ten thousand California residents in a leaked table creates exposure in the original $1M to $7.5M range, or about $1.07M to $7.99M using the adjusted thresholds, before actual damages and litigation costs. Under HIPAA, touching health data is not enough by itself. If your app creates, receives, maintains, or transmits PHI for a covered entity, you may be a business associate and directly liable for specific Security Rule and breach-notification obligations. A consumer wellness app, a provider-facing intake tool, and a claims-processing workflow are not the same legal fact pattern. Under PCI DSS, the issue is contractual accountability, not a government fine schedule. PCI SSC says merchants remain responsible for ensuring account data is protected by third-party providers, maintaining written agreements, monitoring provider compliance, and understanding shared responsibilities. If your payment setup leaks a Stripe secret key into the browser, your acquirer, card-brand relationships, forensic costs, fraud costs, and customer support load are still your problem before anyone asks which tool wrote the line. Under the SEC cyber disclosure rule, public registrants must file Item 1.05 of Form 8-K within four business days after determining a cybersecurity incident is material. That rule does not apply to every private seed or Series A startup. It does matter if you are public, operating inside a public registrant's material systems, or selling into customers who need you inside their own disclosure and incident-response process. Under FTC Section 5, the agency has brought privacy and security cases where companies misled consumers, failed to maintain security for sensitive information, or caused substantial consumer injury. Recent and older FTC actions show what remedies can look like: formal information security programs, independent assessments, redress, and long-running order obligations. "We used Cursor" is not a regulatory defense. At best, it explains how the bad code got there. It does not prove reasonable security review. Five vulnerabilities account for most vibe-coded breach risk Audit a vibe-coded app and the same five problems appear early. If you built on Supabase and an AI assistant, assume each one applies until you have proven otherwise. 1. Supabase RLS missing or ineffective on exposed tables. Supabase gives browser-friendly database access for exposed schemas, usually public. Access depends on grants and RLS policies. Supabase now enables RLS by default for tables created through the dashboard Table Editor, but SQL-created tables and generated migrations still need explicit RLS and policies. That nuance matters. The old sentence "RLS is disabled by default on every new table" is no longer accurate. The risk is still real, because AI-generated migrations usually arrive as SQL, and SQL-created tables can be exposed if the grants and policies are wrong. Supabase's own advisor includes a critical "RLS disabled in public" lint for a reason. 2. Service-role keys in the frontend bundle. Supabase service-role keys bypass RLS and must never be shipped to the browser. We see the same pattern with Stripe sk_live_... keys, Firebase admin credentials, OpenAI keys, Anthropic keys, and AWS access keys in client-readable bundles. The AI "fixes" a permissions bug by moving the powerful key closer to the user. 3. Inverted access-control logic. The Register reported in February 2026 that researcher Taimur Khan found a Lovable-built exam app leaking 18,697 user records, including K-12 students and UC Berkeley and UC Davis accounts. The reported root cause was exactly the kind of bug that looks fine in a demo: a Supabase RPC access check with the condition inverted. Authenticated users blocked, anonymous users granted access. 4. OAuth misconfigurations. The issues we look for first are skipped state parameters, loose redirect URI validation, and tokens stored in localStorage instead of httpOnly cookies. Each is a standard OWASP problem. None requires a novel AI exploit. 5. Admin routes without auth guards. /admin, /api/users, and /api/export ship without middleware because the AI implemented the page and nobody asked who can hit the URL. The right default is boring: deny by default, opt in to public access. A separate failure mode is the agent itself acting destructively in production. According to July 2025 reporting from The Register and Fortune, Jason Lemkin of SaaStr ran a Replit Agent build under an explicit code-and-action freeze; the agent still executed production database commands, wiped records for 1,200+ executives and 1,190+ companies, and generated fake users during the incident. Replit's CEO publicly apologized, and Replit later added stronger dev/prod separation and planning-only controls. Insurance will not save a messy incident by default Two numbers are useful, with the date attached. IBM's 2024 Cost of a Data Breach Report put the global average breach cost at $4.88 million, up 10% year over year. The healthcare average was $9.77 million, and the average breach lifecycle was 258 days. Those numbers do not mean your seed-stage app will spend $4.88 million after every incident. They do mean "we have cyber insurance" is not a production-readiness plan. Cyber policies are contracts, not magic incident budgets. If your application depends on AI-generated code, ask your broker three questions before the breach: does the policy exclude or limit losses arising from AI systems or generated code; does it require documented secure-development controls; and does it cover incident response when the vulnerable code was created by a third-party tool? Do not assume the answer is yes. The security base rate is the stronger argument. Veracode's 2025 GenAI Code Security Report tested 100+ models across four languages and found that 45% of generated code samples failed security tests. Stanford's CCS '23 study found developers using an AI assistant wrote significantly less secure code and were more likely to believe their code was secure. Imagine you're the founder of a 9,000-user fintech, 2,500 of them in California, raising a Series A. You shipped on Lovable in eight weeks. A pen-tester finds a browser-exposed database path, dumps a table, and posts the breach to X. Your CCPA statutory-damages exposure alone can land in the hundreds of thousands before you calculate counsel, forensics, user notification, customer churn, card-brand fallout, and the investor update you now have to write. That is not a reason to stop using AI. It is a reason to stop confusing "generated" with "reviewed." What hardening actually looks like before production We are an engineering team that uses AI every day. We do not think you should rip Cursor out of your editor or stop prototyping in Lovable. Prototyping in those tools is genuinely faster, and shipping a v0 to ten friendly users is fine. The line that matters is the line into production with real customer data. When our engineering team takes a vibe-coded codebase to production, the same checklist runs every time: 1. Lock down the database before anything else. Every exposed Supabase table gets explicit RLS and per-row policies, SQL migrations include the grants each role actually needs, the service-role key moves to server-side environment variables, and the anon key's permissions are scoped. We script Supabase advisor checks into CI so a regression breaks the build. 2. Audit every secret in the bundle. We scan the production JS bundle for sk_live_, service_role, AKIA, and the prefixes for OpenAI and Anthropic keys before each release. Anything found gets rotated and moved server-side that day. 3. Run SAST and dependency scanning on every AI-generated diff. The Veracode and Stanford findings tell you why: generated code can look correct while failing security tests, and developer intuition is too optimistic. Static analysis is the cheapest correction available. 4. Implement auth middleware as a default, not a per-route choice. Every admin and API route gets an explicit guard at the framework level. Default-deny, opt in to public. 5. Write the breach playbook before the breach. Who calls counsel. Who preserves logs. Who notifies customers. Who contacts the broker. Who decides whether a customer, regulator, card brand, or public-company partner must be notified. We document this in a one-page runbook and rehearse it once a quarter. 6. Buy back accountability with a code-review contract. The reason this works is the same reason "we used the AI" does not work as a defense. Somebody has to own the code that ships. We sign that ownership in writing. "But our prototype works and our runway is short" Two objections come up every time we have this conversation, and both deserve direct answers. "Our app is small. No one is going to scan us." Vibe App Scanner reported 170 vulnerable Lovable apps across 1,645 scanned showcase apps. Pen-testers script Supabase project URLs and REST endpoints because the patterns are predictable. You do not have to be famous to be enumerated. "Hardening will slow us down past our runway." A focused production-readiness sprint, RLS policies, secret rotation, SAST in CI, auth middleware, breach runbook, runs two to three weeks for a typical Supabase-and-Next.js vibe-coded app. The CCPA statutory exposure on a 10,000-user California breach can cross $1M before actual damages. The math is not close. The line is "harden before production," not "never use AI" AI code generation is genuinely useful. We use it. The mistake is treating the output of a tool whose own terms disclaim reliability as if it were production-grade, then assuming a customer, regulator, acquirer, insurer, or investor will accept the disclaimer on your behalf. Move fast in the prototype. Harden before the first real customer. That is the only version of this story where "AI wrote it" remains a build note instead of an incident headline. If your app was built with Lovable, Cursor, Bolt.new, Replit Agent, or v0 and it handles customer data, the accountability is yours. Book a call and we will audit the RLS policies, secret exposure, auth routes, incident runbook, and production-readiness gaps. --- ### Three AI coding tools. All three on one laptop. URL: https://appssemble.com/blog/cursor-claude-windsurf How senior teams split Claude Code, Cursor, and Windsurf by workflow. Choosing one AI coding agent in 2026 is the wrong decision. Senior teams do not pick Cursor, Claude Code, or Windsurf as a religion. They split the work: Claude Code for autonomous terminal loops, Cursor for inline edits, and Windsurf for large-repository navigation and Devin handoff. That sounds like tool sprawl until you compare it with engineering time. On current monthly pricing, the entry paid stack is about $60 per engineer before extra usage: Claude Pro, Cursor Pro, and Windsurf Pro are each $20/month. Daily agent users should budget higher: Claude Max is $100 or $200/month, Cursor Pro+ is $60/month, Cursor Ultra is $200/month, and Windsurf Max is $200/month. The real decision is not "which logo wins?" It is where you want the agent to think, edit, run tests, and stop. Picking one winner misses how the work is shaped Cursor became the default AI editor for many AI-native teams because it made the editor feel faster. Tab autocomplete, chat, and Composer put multi-file code edits inside the place developers already lived. For a lot of teams, that was enough to make Cursor the first real AI-native IDE habit. Claude Code changed the center of gravity because it is not editor-shaped. Anthropic launched Claude Code as a terminal tool in February 2025, and that is still where its best workflow lives, even though Claude Code now also has IDE, desktop, and browser surfaces. It reads CLAUDE.md, edits files, runs commands, and loops until it hits the finish line or a guardrail. Windsurf matters because it did not stay as "the other Cursor." After Cognition acquired Windsurf on July 14, 2025, the product started moving toward a local-editor plus autonomous-agent setup. Windsurf 2.0, released on April 15, 2026, brought Devin directly into the editor, so Cascade can plan locally and hand work to a cloud agent. These are three different surfaces. Treating them as interchangeable agentic coding tools creates bad purchasing decisions and worse engineering habits. Claude Code owns the long terminal loop Claude Code is strongest when the task has a goal, a test command, and enough room to work. Ask it to trace a failing integration test, modify five backend files, update the fixtures, run the suite, and explain the diff. That is exactly the kind of loop where the terminal is better than a chat panel inside an editor. Armin Ronacher's public arc is the cleanest signal. He moved from Cursor-heavy work to mostly Claude Code over six months, not because Cursor became useless, but because the hands-off loop fit his workflow better. That is the pattern we see on production teams too: the editor is where you shape a diff, and the terminal is where you delegate bounded work. The senior-engineer pattern is clear: you stay the architect. Mitchell Hashimoto's "bowling with bumpers" framing is the right mental model. You define the lane, the constraints, the tests, and the files it should not touch; the agent does the typing and the local investigation. The important file is CLAUDE.md, not a 900-line prompt museum. It should name commands, repo conventions, review rules, protected paths, and known gotchas. If the agent needs 200 instructions before it writes a line, your repo is asking the model to compensate for missing engineering discipline. Claude Code has real scars. Anthropic's March-April 2026 regression reduced quality for weeks, and the company's April 23 post-mortem tied it to three product-layer changes: a March 4 default reasoning-effort reduction, a March 26 stale-session context bug, and an April 16 system-prompt change to reduce verbosity. Anthropic says all three were fixed by April 20 in v2.1.116, and that it reset usage limits for subscribers. That does not make Claude Code unusable. It means you should run it inside tests, hooks, permissions, and human review. Cursor is still the fastest editor when you are in the diff Cursor is still where we want the AI when a developer is actively shaping code in real time. Inline tab completion, Composer, and visible diffs are a good fit for component edits, endpoint wiring, test updates, and contained refactors. You are close enough to reject the "while I was here" changes before they become a PR. That proximity matters. Composer can be excellent on a five-file change and sloppy on a 40-file refactor that crosses auth, API middleware, database policy, and frontend state. The fix is not to stop using Cursor. The fix is to keep the task bounded enough that you can review the diff while the decision is still fresh. Cursor's biggest non-technical failure was pricing trust. In June 2025, Cursor moved Pro toward compute-based usage, and the old $20/month mental model stopped matching how agent-heavy workflows burned through usage. By July 4, Cursor had published a pricing clarification and promised refunds for unexpected charges from the prior three weeks. That matters for a CTO. Cursor Pro may still be worth $20/month for the editor loop, Pro+ at $60/month is the plan Cursor recommends for daily agent users, and Ultra may be worth $200/month for power users. Budget from actual agent usage, not the headline plan. A team that treats Cursor like unlimited background labor will get surprised. Windsurf is the large-repo bet now Windsurf's useful claim is not that Cascade beats Composer in every prompt. The useful claim is that large repositories need better maps, faster codebase understanding, and a cleaner bridge from local planning to autonomous execution. Codemaps are the clearest example: they create shareable views of how code paths and components relate, which is exactly where big repos become expensive to reason about. The Cognition acquisition made that bet more credible. Cognition said the deal included Windsurf's IP, product, brand, $82M ARR, 350+ enterprise customers, and hundreds of thousands of daily active users. The strategic direction is obvious: Windsurf is the editor surface, Devin is the autonomous executor. LogRocket having Windsurf at #1 in its March 2026 AI dev tool list is not proof by itself. Rankings move, and senior teams should not buy tools from league tables. Still, it matches what changed in the product: Windsurf is no longer just Cascade against Composer. SWE-1.6 also changes the feel of the product. Cognition says SWE-1.6 is generally available in Windsurf, runs at up to 950 tokens per second for paying users, and improves on SWE-1.5's UX problems such as overthinking, looping, and sequential tool use. We would not buy a tool because of a speed claim alone, but speed matters when the agent is searching, planning, writing, checking, and continuing across a large-repository refactoring session. Windsurf pricing is no longer the old $15 Pro and $30 Teams credit framing either. The current monthly page lists Pro at $20/month, Teams at $40/user/month, and Max at $200/month, with extra usage at API price. That makes the buying question less "cheap Windsurf versus expensive Cursor" and more "does Codemaps plus Devin change the review workflow enough?" The trust story is still messier than the product story. Windsurf went through a failed OpenAI acquisition path, a Google reverse-acquihire of founders and research leaders, and then Cognition buying the remaining company; TechCrunch's July 2025 report captures that sequence. Pilot it on a real repo before standardizing a team around it. The split works best when each tool has a job Imagine you're the CTO of a 12-person SaaS team with a 300,000-line TypeScript monorepo, a Postgres backend, and a billing flow nobody wants to break. You have a bug in invoice proration, a stale admin UI, and a support request asking why exports fail for one enterprise customer. You do not need one magic AI coding agent. You need three controlled work modes. Claude Code gets the invoice-proration bug because it can read the failing tests, inspect migrations, run the backend suite, and iterate in a terminal split. Cursor gets the admin UI because the developer is in the component tree, accepting inline edits and scanning every changed prop. Windsurf gets the export failure because Codemaps help trace the data flow, and Devin handoff can run a longer investigation without blocking the laptop. None of the three gets to decide the architecture. The human owner decides whether proration belongs in SQL, a service object, or a queue consumer. The tools can draft, patch, test, and explain. They do not get the final vote. This is also how we keep AI development practical at appssemble. Our engineering practice already assumes small senior teams, owned code, tests, CI, and production responsibility. AI agents fit that model because there is a system around them; they fail when they become a substitute for that system. Rules beat model loyalty The best Cursor setup, Claude Code setup, or Windsurf setup is still a bad idea without repo rules. You need instruction files, protected paths, test commands, CODEOWNERS, branch protection, and CI checks that block the predictable mistakes. If the agent can delete failing tests, silence type errors, or push around review, the tool choice is a distraction. Keep the rules short and enforce the important ones outside the model. CLAUDE.md, .cursor/rules/*.mdc, and Windsurf rules should tell the agent what matters. Hooks, lint gates, permissions, CODEOWNERS, and CI should stop the agent when it ignores those rules. We do not let agents touch auth, billing, or migrations without owner review. The model can propose the diff. It does not get to bypass the production boundary. This is where many teams get the comparison wrong. They ask whether Claude Code is smarter than Cursor, or whether Composer vs Cascade produces the nicer diff. The more useful question is: which tool gives your team the right feedback loop for this class of work? For tight editor work, we still like Cursor. For autonomous loops, we reach for Claude Code. For large-repo navigation and Devin-backed execution, Windsurf has earned a serious look. All three beats a winner-takes-all policy The honest verdict is boring: keep all three if your team is senior enough to use them with discipline. Cursor is the editor. Claude Code is the terminal worker. Windsurf is the large-repo map and Devin bridge. The cost is not zero, and the pricing will keep moving. Still, even a $200/month power-user plan is small compared with one senior engineer losing half a day to a bounded refactor the agent could have handled under tests. The risk is not paying for too many tools. The risk is letting any one of them operate without ownership. We do not want an AI coding agent that replaces engineering judgment. We want agentic coding tools that make good engineering judgment faster to apply. If you want advice on shipping with Claude Code, Cursor, or Windsurf in a production repo, book a call. We use them all. --- ### Stop inheriting vibe-code debt: what changes when your Lovable app hits $30K MRR URL: https://appssemble.com/blog/lovable-to-30k-mrr At 30K MRR, Lovable MVPs start hitting velocity, security, payments, and compliance limits. Lovable is the right tool to get you to launch. It is the wrong tool to scale a business on forever. Both of those sentences can be true at the same time. In our intake, the handoff usually shows up somewhere between $20K and $40K MRR. The revenue number is not magic. It is the point where paid subscriptions, sensitive customer data, and the first serious B2B procurement process start arriving at the same time. The pattern we see now, in 2026, is consistent. A founder ships a working product on Lovable in three to six weeks. They hit $15K MRR in 90 days because the idea was right and the niche was warm. Then three things happen in the same month: a procurement team sends a 200-item security questionnaire, failed payments put a few hundred dollars of MRR at risk, and every new feature starts taking three times as long as the last one. The launch stack stops being the launch stack. It becomes the bottleneck. This post is for technical founders and CTOs in that exact spot. We have done enough of these migrations to give you the math, the trigger points, and an honest answer to the only question that matters: when do you stop patching and start rebuilding? Lovable's real cost at $30K MRR isn't infra: it's velocity decay Founders look at their bill and conclude they're fine. Vercel Pro at $20-$50, Supabase Pro at $25 plus usage, PostHog free tier, Sentry Team at $26-$80, a logs tier under $100. Total infra outside Stripe lands around $170-$600 a month, somewhere between half a percent and two percent of revenue. That is not the problem. The problem is the failure mode AddJam, Lightning Kite, and Convex all describe in nearly identical language: hidden assumptions, flat data models, missing edge cases, and production logic spread across places nobody would choose on purpose. In our audits, that often turns into 2-3× slower feature work once the generated surface gets large enough. AddJam's marketplace case study found user preferences stored as JSON blobs instead of normalized tables, no soft deletes, flat entity relationships where hierarchical ones were needed, and unindexed critical fields. Each of those is a one-line bug. Together they are a tax on every future feature. Imagine you're shipping a billing-tier change at $30K MRR. On a clean Next.js codebase with typed Stripe webhooks, that's a one-day task, schema migration, webhook handler, UI toggle, regression test. On a Lovable app where your subscription state lives partly in a Supabase JSON column, partly in client-side React state, and partly in a Stripe metadata field a previous prompt invented, the same change takes a week and breaks two unrelated screens you didn't know depended on it. The cost isn't the $50 of compute. It's that your roadmap quietly halves while your competitors' doesn't. One security audit will force the migration anyway The public security record is already enough without bundling every incident into one mystery report. Matt Palmer's CVE-2025-48757 disclosure describes Lovable-generated projects with missing or insufficient Supabase RLS on client-controlled database requests. Vibe App Scanner's write-up of the same class reports 170 exposed Lovable apps and 303 vulnerable endpoints; separately, The Register reported researcher Taimur Khan found 16 vulnerabilities, six of them critical, in one Lovable-hosted EdTech app with 18,697 user records exposed. The technical pattern is not "anon key in the browser equals breach." Supabase's own docs say publishable and legacy anon keys can live in public clients when RLS is enabled and scoped correctly. The failure pattern is missing or overbroad RLS, service_role or secret keys in the browser, hardcoded OpenAI and Stripe secrets in the JS bundle, full user objects in logs, and client-side code trying to enforce authorization that belongs in the database or backend. This used to be an embarrassment. In 2026 it is a sales blocker. Buyers now ask, by name: "Is your app built on Lovable? Show us your RLS policy coverage and your service_role key custody." Answering well requires the same set of changes that any responsible production stack already has, server-side authorization for sensitive tables, tested RLS where browser access remains, secrets out of the bundle, and enough logging to prove what happened. There is no version of "tighten it up in place" that gets you there without restructuring most of the data layer. If a procurement team hasn't asked yet, they will. The cheapest moment to do this work is before the questionnaire arrives, not during the two-week window you have to answer it. Payment recovery is the cheapest revenue you'll lose This one is pure arithmetic and it surprises founders every time. Stripe's current public material gives you the baseline: its recovery tools recover about 56-57% of failed recurring payments on average, and the Smart Retries feature page specifically cites 57%. Stripe's own Smart Retries write-up also says recovered monthly subscriptions continue for seven more months on average. Specialist dunning vendors publish higher optimized claims, but treat 80% as an upside model, not a guarantee. Assumption: $30K MRR, $450-$900 of failed-payment MRR at risk each month, and a 30-day recovery window. These are failed charges before recovery, not permanent churn. The default Lovable launch stack recovers a little over half of that automatically. A tuned recovery setup may recover closer to four-fifths if the product has enough volume, clean subscription state, recovery emails, and hosted card-update links. The math on a typical $30K MRR product: Recovery modelMonthly MRR recoveredAnnualizedStripe defaults (~57%)$260-$510$3.1K-$6.1KUpside dunning model (~80%)$360-$720$4.3K-$8.6KDelta from tuning$100-$210/mo$1.2K-$2.5K/year That delta does not fund a migration by itself. At $100-$210 per month, a $4,500 migration takes roughly 21-45 months to pay back from recovery tuning alone. It still matters because it is recurring revenue you should not leak while you are fixing the subscription system anyway. Payment fees compound the same way. Assume 600 customers paying $50. Stripe's US domestic card pricing is roughly $1,050/month before Billing or Tax: 2.9% of $30K plus 600 × $0.30. Add Billing, Tax, international cards, and currency conversion only when they actually apply; Stripe currently lists Billing pay-as-you-go at 0.7% of Billing volume, Tax Basic no-code at 0.5% per transaction where you are registered, +1.5% for international cards, and +1% for currency conversion. Polar and Lemon Squeezy simplify tax and Merchant of Record work, but the headline rate is not the whole bill. Polar lists 4% + $0.40, with +1.5% for international cards and +0.5% for subscription payments. Lemon Squeezy lists 5% + $0.50, and its fees docs show possible +1.5% international, +1.5% PayPal, and +0.5% subscription additions. A US-only Stripe SaaS can still be cheaper. A global SaaS may choose a Merchant of Record because tax, currency, retries, and customer emails become easier to reason about, not because the sticker rate always wins. None of this is glamorous engineering. All of it is revenue you are paying for and not collecting. Compliance debt just became a sales blocker The SOC 2 trigger is not MRR by itself. It is usually one $100K+ ACV deal in your pipeline whose procurement team asks for a current Type 2 report, or one security questionnaire that makes your current answers look unserious. Before that question lands, founders almost never start. After it lands, a Type 1 can unblock an urgent deal if readiness is good, but the honest planning range is weeks to a few months. Type 2 then needs a 3-12 month observation window. A small startup first-year program can land around $20K-$50K+, and it can run higher once auditor scope, tooling, remediation, and legal work are included. A single $500K enterprise deal pays for that twice over. The harder problem is that you can't start the SOC 2 work on top of a stack that fails its first control audit, meaning RLS-exposed tables, secrets in the client bundle, no audit log, no documented change-management process. If your first enterprise buyer asks for Type 2, the architecture work has already started whether you budgeted it or not. GDPR is cheaper to get right but expensive to forget. At $30K MRR with EU traffic the table-stakes additions are a cookie consent banner (Cookiebot or Osano), DPAs signed with sub-processors (Stripe, Supabase, PostHog, and Sentry all publish them), and a documented data-deletion endpoint. None of this is hard. All of it presumes a backend you can actually reason about. The migration math The published prices for getting off Lovable are public, but they need to be quoted carefully. NextLovable's pages, checked in May 2026, show a lower self-service path and a higher done-for-you path than the old $2,500 shorthand. Treat these as vendor-claimed packages, not market benchmarks: PathTimelinePublic priceExit auditScope first$299TanStack Start migration3-5 business days$1,499Lovable Cloud to Supabase3-5 business days to 2 weeks, depending on service page$3,500 DFY on the main page; $2,500-$4,500 on the migrator page; $99 self-service in docsNext.js migration2 weeks, up to 20 pages$4,500Complex / enterprise3+ weeks$7,500+ Ministry of Programming's practitioner roadmap puts a full rebuild at 6-12 weeks depending on feature scope. Our own engagements land in roughly the same window for products at $20K-$50K MRR. So the choice is not "payment recovery pays for the rebuild." It doesn't. The choice is whether you keep absorbing four leaks at once: slowed feature work, unrecovered payments, security rework, and procurement stalls. A scoped migration pays back when those lines move together, especially when the next four features stop taking a week each because subscription state, RLS, webhooks, and secrets finally live where they belong. 1. Move the framework first. Vite SPA to Next.js 15 with the App Router gives you SSR for SEO, auth-aware rendering, and a place to put server actions that don't ship secrets to the browser. The current NextLovable done-for-you Next.js path is $4,500 for up to 20 pages over roughly two weeks; cheaper self-service code migration is not a substitute for a production audit. 2. Move the secrets next. Every OpenAI, Stripe, or Firebase key in your bundle becomes a server-side proxy with rate limits and key rotation. Direct browser-to-OpenAI calls go away entirely. 3. Audit and harden RLS. Every table gets explicit policies. Sensitive tables stop being queried directly from the browser; where browser queries remain, RLS is deny-by-default and tested. The service_role key never touches the client. 4. Add observability you can act on. Sentry with source maps wired in CI, PostHog for product analytics with free-tier volume checked against actual event and replay counts, alerts off email and onto Slack with one human on call. Total modeled monthly cost: $100-$300. 5. Tune dunning before anything else. Smart Retries on, recovery emails enabled, a hosted card-update link, and a retry cadence your team actually owns. Stripe currently recommends Smart Retries at eight tries within two weeks; a 21-day schedule is a deliberate custom choice, not the default. "But our app works fine on Lovable today" It probably does, for the users you have today. The argument isn't that Lovable apps break at $30K MRR. The argument is that the cost of keeping a Lovable app working past that band, in engineering time, unrecovered revenue, compliance friction, and incident risk, can exceed a scoped migration budget faster than the SaaS bill suggests. If you're at $5K MRR, stay on Lovable and ship features. If you're at $50K MRR with enterprise deals in the pipeline, you have already paid the migration cost in slowed velocity; you just haven't booked it. The interesting band is the one where this post finds you: somewhere between $20K and $40K MRR, with one foot in the launch stack and one foot in a market that now expects more of you. We build production stacks for exactly this transition. The team that does the migration is the team that owns the result, same designers, same engineers, same on-call rotation, through engineering and, where it matters, AI workflows that ship to production rather than to a notebook. Grovs processes 10M+ events daily on infrastructure built this way; Semaphr manages 500K+ app sessions on the same principles. The migration playbook is not a hypothesis. Lovable is right for launch. It is not right for scale. The handoff between those two phases is a real piece of engineering, and the cheapest moment to do it is before the questionnaire arrives, the payment spike hits, and the next feature takes three weeks instead of three days. If you've hit $20K+ MRR on Lovable and are seeing the cracks, book a call. We'll tell you in 30 minutes whether you should migrate now, in three months, or not yet. --- ### Stop hiring the wrong rescue for a broken codebase URL: https://appssemble.com/blog/founder-decision-matrix A practical framework for choosing who should rescue a broken app The most expensive mistake after a vibe-coded app breaks is not picking the wrong rescuer. It is picking one whose business model cannot tell you the truth. If your app was built in Lovable, Bolt, v0, Cursor, or a similar workflow, the first people who appear in your inbox will sound useful: certified partner, rescue sprint, senior expert, fixed scope. The harder question is whether they can honestly say, "this should leave the platform," when that is the right answer. That is the founder hiring dilemma behind most vibe-coding app rescue work. You are not only choosing a developer. You are choosing the person who gets to define the problem. Platform-certified rescues have a built-in conflict A vendor-certified builder knows the platform. That is useful when your issue is narrow: a broken page, a bad prompt chain, a missing integration, a production setting you do not understand. The conflict starts when the platform itself is part of the problem. A partner whose pipeline, certification, and referrals come from the platform has a quiet reason to keep your app inside it. They can patch the symptoms, but they may not be the right person to recommend migration. This is not a moral accusation. It is an incentive problem. The same pattern exists in Salesforce, HubSpot, Bubble, and no-code ecosystems. A certified expert can be excellent inside the box and still be structurally weak at telling you the box is wrong. When your product has paying users, compliance risk, or a roadmap that stretches past 90 days, that distinction matters. CVE-2025-48757, a disputed Lovable-generated-project RLS vulnerability disclosed in 2025, showed the risk clearly: Vibe App Scanner reported 170 of 1,645 scanned Lovable apps exposing data through missing or insufficient Supabase Row Level Security. A platform partner can fix individual holes. What they cannot always do is give you a clean, vendor-agnostic answer to the larger question: should this product still live here? The four rescue options are not interchangeable Most founders compare rescue help by price. That is the wrong axis. You should compare by what each option is structurally able to own. 1. Fractional CTO: You pay for technical judgment, architecture, hiring support, and vendor management. Typical retainers sit around $5K-$15K/month, with advisory-only work sometimes lower and specialist hourly rates running far higher. A good fractional CTO will not be the cheapest option, but they are often the only person in the room paid to reduce your dependency on everyone else. 2. Vendor-certified partner: You pay for platform fluency. Lovable's official Experts directory in May 2026 listed rates roughly from $50-$130/hour, project budgets from about $1,000-$4,500, and some monthly budgets around $4,000/month. Independent maintenance packages may start lower, but separate those from the official partner directory. This can be the right move for a prototype, internal tool, landing site, or low-risk app that belongs on the platform. 3. Dev agency: You pay for a team. Boutique retainers can start around $5K-$15K/month, while larger or specialist teams can run $40K-$80K+/month. The risk is not only cost. It is that the senior person who sells the work is not always the senior person fixing your code. 4. Freelancer: You pay for one person's time. Upwork's own software-developer page lists $10-$100/hour as the broad marketplace range and $70-$150+/hour for expert software developers. Toptal does not publish a simple developer rate card; third-party 2026 reviews commonly place engineering roles around $60-$200+/hour, plus Toptal's public $79/month subscription. Freelancers can be great for bounded problems, but they are a risky answer to an open-ended rebuild unless someone technical is reviewing the work. The same broken MVP can be priced four different ways: $1,500 to patch, $30K-$90K to stabilize with a fractional CTO plus builders, $80K-$400K through an agency rebuild, or $10K-$60K through one or two senior freelancers. Those are not versions of the same service. They are different bets. Here is the decision matrix before you take calls: If your real problem is...Start with...Avoid...One broken Lovable flowVendor-certified partner or senior freelancerA six-month agency retainerPaying users plus unknown architecture or security riskFractional CTO or independent auditMore platform-specific patches before diagnosisClear roadmap, not enough handsFreelancer or agency with technical oversightA fractional CTO as a substitute for buildersMulti-platform rebuild after fundingProduct studio or agency plus internal ownerOne freelancer owning the whole productNo product-market fit yetSmall fixed-scope patchRebuild theater When is a fractional CTO the only real protection? A fractional CTO makes sense when you cannot grade the code and the decision is bigger than a ticket list. They protect you from information asymmetry because their job is to tell you what is true, not to keep billing the same stack. Imagine you are a non-technical founder with a Lovable app doing real revenue. Checkout fails twice a week, customers report account data bleeding between sessions, and three builders tell you they can "clean it up" in two weeks. The first question is not "who is fastest?" It is "is this a cleanup, a rewrite, or a staged migration?" That is a CTO-shaped question. It affects architecture, budget, fundraising risk, team hiring, security exposure, and your next six months of roadmap. A platform partner may know how to fix the form. A freelancer may know how to repair the API. A fractional CTO should be able to decide whether the current foundation deserves more money at all. The catch is that a fractional CTO is not a magic engineer. Many do not write much production code, and some have been away from daily implementation for years. Ask when they last shipped code, how many clients they currently support, and whether they will run a paid four-week trial before any longer commitment. When does a freelancer actually make sense? A freelancer makes sense when the problem fits inside a clean sentence. "Migrate auth from X to Y." "Fix these 12 bugs." "Add Stripe subscriptions." "Move this repo into CI and write the missing deploy script." That shape lets you define acceptance criteria and stop the work if it drifts. It also lets you bring in a second reviewer every two weeks without turning the project into committee theater. If the freelancer is good, you get senior execution without agency overhead. The freelancer model fails when the brief is "rebuild my app." Open-ended work creates open-ended dependency. If you cannot read the repo, evaluate pull requests, manage credentials, and test production behavior, you are asking one person to be engineer, architect, product manager, security reviewer, and handover team. The ghosting risk is real, but the number that matters is not a hard-to-verify marketplace story. The safer question is simpler: if the freelancer disappears tomorrow, can another engineer pick up the repo, credentials, deploy pipeline, and database? If not, you bought a dependency, not help. If you use a freelancer, own the repo from day one. Own AWS, Vercel, Supabase, the domain, and the database. They should be invited into your systems, not become the systems. Why is the agency trap so easy to miss? Agencies feel safer because they look like a company. They have a process, a deck, a project manager, and case studies. That can be useful when the work genuinely needs a team: backend, frontend, mobile, design, QA, infrastructure, and release management all moving together. The trap is contract shape. A bad freelancer can be replaced tomorrow. A bad agency retainer can leave you one month into a six-month agreement with five months still owed. That is why month-one pricing is often less important than the exit clause. One Startup Daily founder story makes the point: two non-technical founders received estimates from $50K to $500K, hired internally, spent $100K, discovered the architecture was not scalable, brought in a CTO, and restarted. The lesson is not "never hire help." It is "do not outsource judgment when you have no way to inspect the technical answer." Agency work is strongest when there is a clear roadmap, real budget, and someone on your side who can review the work. Without that, you are outsourcing both execution and judgment. That is where costs grow without the product getting healthier. Choose by stage, not by the last LinkedIn DM The right rescue depends on where the product is, not who had the best pitch. If you are pre-PMF and the app is still a prototype, a vendor-certified partner or freelancer can be enough. Keep the scope fixed, keep credentials under your control, and do not sign a long retainer for a product you may throw away in 60 days. If you have paying users and no technical lead, start with a fractional CTO or an independent architecture review. You need a rebuild-vs-refactor decision before you need a sprint plan. The wrong sprint plan is just fast waste. If you have a roadmap and need hands, a freelancer or agency can work. The deciding factor is whether you can review output. If nobody on your side can judge architecture, security, and maintainability, budget for that review before you budget for more builders. If you are Series A or beyond, with multi-platform work and an 18-month product plan, you probably need a real engineering owner. That may mean hiring in-house, using a fractional CTO as a bridge, or bringing in a product studio that owns engineering, delivery, hardening, and handover together. The fifth option is ownership appssemble is not the answer to every broken vibe-coded app. Some products should stay on the platform. Some should be fixed by one senior freelancer. Some should be deleted and rebuilt after the market says anything useful. Our bias is simple: the team fixing the product should be free to recommend the right foundation. Sometimes that means a patch. Sometimes it means migration. Sometimes it means telling you not to spend another dollar until the product has a clearer reason to exist. That is why we do not sell hours or headcount. We take responsibility for what we ship, and we prefer outcome-priced work where the deliverable is clear: audit, stabilize, rebuild, migrate, harden, or hand over. Small senior team, no vendor lock-in, same people in the planning call and the repo. If your app is broken and you need someone who will tell you the truth, book a call. Bring the repo, the production symptoms, the budget range, and the decision you are scared to make. We will help you choose the rescue that fits the product, even when that answer is not us. --- ### Three angel diligence questions that separate AI MVPs from demos URL: https://appssemble.com/blog/angel-diligence-questions How angels evaluate AI MVPs for defensibility, unit economics, and engineering durability. Smart angels do not need your Lovable or Cursor demo to be impressive anymore. They assume you can build one. Imagine you have 4,000 weekly actives, a Lovable codebase, and an angel asking what happens after the round. The AI MVP diligence conversation has moved from "can you ship something?" to "can this become a defensible, durable business?" That shift is not philosophical. SaaStr's Jason Lemkin recently framed the new reality with a brutal example: a product advantage that used to take 18 months and seven figures can now become a weekend project, or even a v1 in under an hour. Speed-to-demo is still useful, but it is no longer rare. So the diligence changed. Angels now ask three questions designed to expose what the AI tools did not give you for free: defensibility, unit economics, and engineering judgment. The demo gets you the meeting. The rebuild plan closes the round. Speed-to-demo stopped being the fundraising story Building fast used to be a signal. If you could get an MVP into users' hands in three weeks while another team needed six months, investors could read that as execution quality. In 2026, that same claim is table stakes. Lovable, Cursor, Replit Agent, Base44, and similar tools compressed the visible build window. That is good for founders because you can test a market before burning a round on code. It is bad for weak pitches because the demo no longer proves much by itself. The better story is not "we built this with AI." The better story is "we used AI to get evidence faster, and now we know exactly what needs to be owned, hardened, measured, and rebuilt." That is why investors are moving back to the basics AI did not erase. Crunchbase News put it plainly: when everyone can build with AI, investors look harder at domain expertise, customer discovery, and route to market. What is defensible if anyone can build this in a weekend? This is the moat question, and it is usually the first one. Sometimes it sounds polite: "How do you think about defensibility?" Sometimes it is blunt: "What stops the next founder from cloning this by Friday?" "We use GPT-4" is not an answer. "Our prompts are proprietary" is not much better. A six-month product head start used to matter; now a competent competitor can reproduce a surprising amount of product surface with the same tools you used. The stronger answers sit outside the generated code. You may have distribution in a niche where you already have trust. You may have proprietary data that took six months of domain work to collect and label. You may have an eval suite that catches failure modes a generic wrapper misses. Imagine you are building for legal operations. A generic model can summarize contracts, but your product classifies 4,000 labeled edge cases, tracks failure modes weekly, and improves the review flow where paralegals actually work. The moat is not "AI for contracts." The moat is the data, workflow depth, and eval discipline that a weekend clone does not have. NFX calls these the AI-era defensibilities: distribution, proprietary or real-time data, brand, scale, network effects, and workflow embedding. For a founder at this stage, distribution, data, workflow depth, and evals are the ones an angel can verify this week. This is also where generic stack answers fail. Next.js, Supabase, Cursor, and Claude are tools, not defensibility. Angels may care later if the stack blocks scale, but they do not fund a framework choice. What does each active user cost you? The second question is the unit economics gut-punch: what is your inference cost per active user per month, and what gross margin does that leave? If you cannot answer in numbers, the investor hears "we have not looked at the bill closely enough." The margin bar is harsher because the metrics are easy to mix up. Classic SaaS investors still like 75%+ gross margins. AI application companies are a different bucket: Bessemer's 2025 AI Supernova cohort averaged about 25%, often negative, while steadier AI Shooting Stars were closer to 60%. Cursor's reported 74% in 2025 is another AI-application data point, not a promise for your product. Foundation-model labs are a separate category again: Anthropic was reported at -94% gross margin in 2024, or -109% if nonpaying usage is included, before projecting improvement. Do not mix these blindly. The angel wants your per-user AI COGS, meaning cost of goods sold, not an industry average. That does not mean AI businesses are bad businesses. It means your pricing and routing have to be part of the product, not an afterthought. If you pay $0.01 for an API call and charge $0.012 for the equivalent action, you have a thin resale business, not a software company. A strong answer sounds operational. "Our median user costs $0.80 per month in inference. Power users cost $4.10. We charge $29, and we route routine requests to a cheaper model before escalating hard cases to Claude." Model routing is the kind of lever angels want to see because it changes the math without changing the pitch. It turns "we use Claude for everything" into a cost-control plan: cheap model for routine work, frontier model for hard cases, cached repeated context, and evals to catch quality regressions. If you have an internal before-and-after, show it. If you do not, show the model-call export and the next routing experiment. Who owns the system when 100K users arrive? The third question is the engineering durability audit. It is also the hardest to fake, because a technical advisor can scan the repo and know within an hour whether the system was built or merely generated. The warning signs behind this question are ugly, even if the market-size numbers are not clean. TechStartups, citing Alex Turnbull and Similarweb traffic data, argues that thousands of vibe-coded products are now facing rescue work, with some rebuild budgets quoted in the $50K-$500K range. Treat that as a warning signal, not a clean market-size statistic. That is AI-generated technical debt at fundraising scale. Angels do not need every pre-seed MVP to be perfect, but they do need to believe it can survive the path to the next round. "Lovable handles it" does not survive that conversation. Imagine you have 4,000 weekly active users on a Lovable build and you are raising before a larger launch. The angel asks what happens at 100K monthly active users. A weak answer is "we will rewrite it after funding." A strong answer is "the current app bought us market evidence; the rebuild starts after close, with load tests at 10x, 25x, and 50x current peak traffic, p95 latency targets, database connection limits, queue depth, error rate, model-call timeout budgets, a named senior engineer accountable, and observability on every AI call." The details matter. Who is on call? Where are the secrets? Are Supabase RLS policies audited? Do you log input, output, latency, and cost for every model call? Do you have a 500-case eval set, or are you waiting for users to discover hallucinations in production? "We'll figure it out post-funding" gets you passed on There is a credible version of "we are not done yet." Early products should be unfinished. Angels know that. There is not a credible version of "we have no plan for defensibility, no cost model, and no engineer responsible for the rebuild." That is not an MVP. It is a demo with a fundraising deck attached. The distinction matters because AI accelerates great engineers. It does not replace engineering judgment. A founder who can say "we intentionally used Lovable to validate demand, and here is the production plan" is in a different category from a founder who believes the generated app is already the company. The winners usually pair the demo with a named human owner: a technical co-founder, a founding engineer, a senior advisor, or a product team that can take responsibility for the stack. That person does not need to turn your pre-seed MVP into a perfect system on day one. They need to know which risks must be retired before the next 10x in traffic. What to show the angel this week You do not need a perfect production system to raise. You need a clean diligence packet that proves you know where Lovable or Cursor stops. Defensibility evidence: waitlist source, proprietary data sample, workflow proof, or eval results. AI COGS export: median cost per active user, power-user cost, blended margin, and worst-case model-price increase. Eval results: a 500-case set, weekly pass/fail trend, and examples of fixed failure modes. Technical audit: RLS review, secret storage state, Sentry or OpenTelemetry screenshots, and model-call logs. Named owner: technical co-founder, founding engineer, advisor, or partner with a 30/60/90-day rebuild plan. The better answer is a rebuild roadmap, not a bigger demo The strongest founders treat the AI-built MVP as speed-to-evidence. They keep what proves the market and rebuild what carries the business. That is the difference between a pitch that says "look what we made" and a pitch that says "look what we learned, and here is how we turn it into a company." This is the work our engineering and AI teams do with founders who have traction but not yet the production floor. We do not start by admiring the demo. We audit the repo, the data model, the model calls, the cost curve, the security posture, and the path to the next user threshold. We have run systems where those details are not optional. Grovs processes 10M+ events daily. The AI Communication Platform runs real-time voice translation under 500ms across six platforms. Those numbers only work when the team owns the architecture, the evals, the traces, and the boring failure modes. If your honest answer to all three diligence questions is "we will figure that out after the round," you do not have an investor problem. You have a production plan problem. If your MVP is built on Lovable or Cursor and you are raising, book a call. We will help you turn the demo into a two-page rebuild plan, cost model, and diligence checklist an angel can believe. --- ### Why vibe-coded apps are sitting on a $4B hidden tax URL: https://appssemble.com/blog/vibe-coding-debt-4b The hidden remediation cost of shipping AI-generated apps no one understands A founder we spoke with last month showed us a Lovable-built MVP that had pulled in 4,000 paying users in nine weeks. Beautiful Stripe integration, slick onboarding, real revenue. It also had its Supabase service-role key sitting in the client bundle, Row Level Security disabled on every table, and a production database anyone with browser dev tools could read end-to-end. The founder had not written a line of the code and could not, in any meaningful sense, read it either. That app is not the whole category. It is the failure mode we keep seeing when non-technical teams ship generated code straight to production. AI coding tools were reported at roughly $2.7B-$3B of combined ARR by early 2026, with Lovable alone claiming 100,000-200,000 new projects per day. The cohort of apps now in production looks enormous from the top, and looks like a pile of unpaid invoices when you zoom in. Our rough math, walked through below, puts the near-term remediation tax on this cohort at around $4 billion over the next 12-18 months. That is a scenario model, not an audited market size. This post is not an argument against AI in coding, we use Claude, Cursor, and Copilot every day, and our AI practice is core to our work. It is an argument against the specific habit of shipping production software no human on the team understands, and a look at what that habit costs when the bill arrives. Vibe coding feels fast because typing was never the bottleneck The pitch is honest about the pleasure. You describe an app, the model writes it, you click Deploy, you have something on the internet inside an hour. The dopamine hit is real and the demos are not faked. The problem is that typing has not been the bottleneck in software for at least two decades. Reading, debugging, refactoring, deciding what not to build, that is where the time goes. Eliminating typing while adding a generator that confidently produces near-misses is exactly the trade that breaks down once your code starts colliding with real users. METR ran the cleanest study we have on this. Sixteen experienced open-source developers, 246 real issues on their own repos averaging 22,000 stars and over a million lines of code. The developers using AI took 19% longer to complete the work than the developers without it. They expected AI to make them 24% faster. After finishing the tasks slower, they still believed AI had sped them up by 20%. The productivity is a vibe; the slowdown is in the data. METR later cautioned that early-2026 measurement is harder because AI-heavy developers and AI-suited tasks increasingly select out of no-AI experiments. Treat the 19% result as a clean early-2025 warning about perception, not a permanent law about every model and every task. Now imagine you are a non-technical founder who has never run that study and has never had to maintain code at scale. The feeling of speed is the only signal you have. You ship. The bill comes later. The debt is not small and it is not theoretical Four source categories point in the same direction. GitClear analyzed 211M lines of code from 2020 through 2024. Code churn, lines reverted or rewritten within two weeks of being committed, rose from 3.1% in 2020 to 5.7% in 2024, a near-doubling that tracks the rise of AI assistants. Copy-pasted blocks rose from 8.3% to 12.3% of all new code. Refactored ("moved") lines collapsed from 24.1% to 9.5%. 2024 was the first year on record where copy-paste outnumbered refactoring in the codebases they track. Engineers are no longer cleaning code; they are layering it. Security looks worse. The original NYU Tandon study on Copilot found around 40% of generated programs contained exploitable bugs or design flaws, XSS, SQL injection, hardcoded credentials, path traversal, the bread-and-butter CWE list. That was a 2021 Copilot/Codex-era baseline, not a verdict on every current model. The pattern did not disappear: Veracode's 2025 GenAI Code Security Report found AI-generated code failed security tests in 45% of cases across 100+ LLMs and common languages. The app-level evidence is just as uncomfortable. Autonoma cites survey data that 53% of teams shipping AI-generated code later found security issues that passed initial review. Escape.tech's scan of 5,600 public vibe-coded apps found 2,000+ vulnerabilities, 400+ exposed secrets, and 175 PII exposures. Wiz framed the platform risk differently: it found that one in five organizations were building on these platforms and exposing themselves to recurring risk patterns like client-side auth, hardcoded secrets, weak RLS, and public internal apps. Then there is the supply-chain attack surface. A USENIX paper on package hallucinations across 16 LLMs found 21.7% of packages recommended by open-source LLMs and 5.2% from commercial ones simply did not exist. The study produced 440,000+ hallucinated package references, including 205,474 unique fake names. The hallucinations were repeatable: about 45% of fake packages were regenerated on every retry for the same prompt. This is no longer a stochastic curiosity; it is an attack primitive called slopsquatting. One researcher registered the hallucinated package huggingface-cli and watched 30,000+ downloads roll in inside three months. The developers themselves are noticing. The 2025 Stack Overflow survey found 84% of developers use or plan to use AI tools, but only 33% trust their accuracy. 46% actively distrust them, and 66% cited "AI solutions that are almost right, but not quite" as their top frustration: the precise failure mode that produces expensive-to-debug code at scale. What the cleanup actually costs Here is the math that gets us to $4B. We will show our work so you can argue with the inputs. First, the methodology note: this is a scenario model, not a measured market. The source-backed inputs are the public tool metrics, code-quality studies, security scans, and market rewrite benchmarks. The appssemble assumptions are the shipped-app filter, the cross-tool cohort estimate, and the percentage of apps that need paid remediation in the next 12-18 months. Cohort size. Strip out Cursor for this model because most Cursor output still passes through engineering teams that already do code review. Look at the non-engineer slice instead: Lovable, Bolt, Replit Agent, and v0. Lovable's 100K-200K new projects per day implies 36M-73M projects a year. Apply a strict 1% filter for "actually shipped to real users with real data" and you get 360K-730K production-ish apps per year on Lovable. Add a modeled contribution from Bolt, Replit Agent, and v0 paid users, and the scenario lands at roughly 1 million production vibe-coded apps shipped in the 12 months ending Q2 2026. That is an assumption, not a platform-reported count. Per-app debt. The most defensible founder-level anchor is not abstract LOC theory. It is what a hardening sprint or partial rewrite costs in the market. A lean SaaS remediation starts around $30K. A more complex cleanup or rewrite commonly moves into the $50K-$120K band. LOC-based estimates are useful only as sanity checks. A $2.82/LOC debt estimate puts an 8,000 LOC app at about $22,500 before project-specific risk. Sonar's $306,000/year per 1M LOC equals about $0.306/LOC/year, not $2.45/LOC/year. For an 8,000 LOC app, that is roughly $2,448/year, or $7,344 over three years before any multiplier. Sonar proves debt compounds; it does not carry an $80K small-app cleanup quote by itself. So the model uses a $30K low-end remediation cost and treats $50K as the midpoint case. The $80K-$120K scenarios are the expensive end, not the base claim. Comes-due rate. Not every app gets remediated. Most die quietly. Of the ones that get traction, debt usually becomes visible around month three to six: a scale wall, a procurement review, a security incident, or a feature that cannot be added without understanding the generated code. Apply a 10-15% "comes-due-this-cycle" assumption and you get 100K-150K apps requiring meaningful remediation in the next 12-18 months. Multiply. ScenarioProduction-ish appsComes-due rateApps needing remediationCost per appMarket sizeLow500K10%50K$30K$1.5BBase1M10%100K$30K$3.0BBase-high1M15%150K$30K$4.5BMidpoint1M10%100K$50K$5.0BHigh1M15%150K$80K$12.0B That is the $4B claim: if roughly 1M production-ish vibe-coded apps exist, and 10-15% need paid remediation soon, a low-end $30K cleanup creates a $3B-$4.5B market. IBM's 2024 report put the average breach cost at $4.88M, but breach cost is not needed to make the base model work. It is upside risk, not the foundation. A top-down sanity check lands in the same neighborhood, but it is illustrative. CISQ pegged accumulated US software technical debt at $1.52T in 2022. If AI-generated code adds even 0.3% to that stock, that is another $4.5B of debt service. The 0.3% is our scenario input, not an independently measured share. Your founders' speed instinct is rational, but incomplete We want to be careful here. The reflex to ship fast is correct. Most startups die from never reaching users, not from shipping code that needs cleanup later. If you have to choose between a beautifully architected app no one ever sees and an ugly one that gets to a thousand users in a week, take the ugly one. We have argued this on this blog before. Vibe coding wins the first move and loses the second one. You ship the prototype in a week. Then a real user signs up, a competitor copies the idea, an investor asks for the architecture, a security researcher finds your Supabase keys, or you simply need to add a feature that requires understanding what the model wrote three months ago. That is where the bill arrives, and where the saved week becomes 90 days of paying down debt or, more often, a full rewrite. There is a name for the underlying problem: comprehension debt. The gap between how much code your system contains and how much of it any human on the team genuinely understands. Technical debt announces itself through mounting friction; comprehension debt breeds false confidence right up until production breaks and nobody can read the stack trace. It is the harder of the two debts to price because it doesn't show up until you need it. For your app, this means the first question is not "should we rewrite?" It is simpler: can a competent engineer prove that users cannot read each other's data, secrets are server-side, payments are verified on the backend, deploys are repeatable, and errors can be traced within minutes? If not, you do not have a production app yet. You have a demo with revenue attached. A better trade-off: senior engineering from day one The same speed argument cuts the other way once you stop measuring speed in lines of code and start measuring it in time to a defensible product. Here is how we run our builds, and why we think it produces a better cost curve than the vibe-only path. 1. AI everywhere humans review. Our engineers use Claude, Cursor, and Copilot continuously. METR reported AI suggestions accepted around 44% of the time in its study, but the accept rate is not the point. Every accepted line needs to be read by a senior engineer who can hold the system in their head. The acceleration is real; the comprehension stays intact. 2. Two-week sprints, working software end of each. A small senior team, typically a designer, two engineers, a tester, gets the first version in your users' hands inside four to six weeks. That is slower than the weekend demo and faster than the rebuild, with code you can hire against, audit, and extend. 3. Security audits before production, not after a CVE. Our engineering practice bakes in load testing, query profiling, security review, and a 99.9% uptime SLA before any code reaches real traffic. The cost is built into the sprint, not into a remediation invoice six months later. 4. AI in production, not in the prototype. Our AI practice is exactly the place where AI generation is most dangerous, RAG pipelines, agents, voice systems, so we treat it with the most rigor. Automated evals on every change, hallucination scoring, prompt-injection detection, PII safety. AI ships when it is measured, not when it feels right. 5. Same team, day one to scale. The team that builds your product is the team that maintains it. Grovs (10M+ events daily) and Semaphr (500K+ app sessions) both live this way, same engineers from first commit to current scale. There is no handoff to a "maintenance team" who cannot read what was generated. "But we cannot afford a senior team, we have to start with vibe coding" We hear this almost every week. Three responses. First, run the math on your specific case. A vibe-coded MVP looks free until you price the rewrite. If your app gets to 1,000 users and falls into the modeled 10-15% of the cohort that needs serious remediation, you are looking at $30K-$80K to fix it, often more than the senior-team build would have cost in the first place. The discount is illusory once you account for the probability-weighted cleanup. Second, use vibe coding for what it is genuinely good at: learning, prototyping, and discovery. Build five Lovable prototypes in a weekend, show them to ten potential customers, find out which idea has signal. That is a legitimate use of these tools and we recommend it. Then, once you know what to build, build it with engineers who can read it. Third, if you have already shipped a vibe-coded app to real users, do not panic and do not rewrite it blindly. Audit it first. Check five things before you prompt another feature: secrets in the client bundle, RLS and authorization, payment and webhook verification, observability, and deploy rollback. Most vibe-coded apps need a hardening sprint, not a full rewrite, close the obvious security holes, replace the worst three or four files, get a real CI/CD pipeline in place, and you can buy yourself another six to twelve months of runway on the same codebase. The expensive mistake is to either ignore the audit and keep shipping until something breaks publicly, or tear the whole thing down without knowing which parts work. The bill is being paid either way Vibe coding did not invent bad code; outsourcing produced its own version for two decades and the cleanup industry that grew up around it (us included) is the same industry now pricing vibe-code remediation. The difference this time is volume and visibility. An offshore shop could produce one mediocre codebase per ~$50K of spend. Lovable reports 100K+ projects a day, many shipped without anyone, including the founder, reading them. The $4B figure is not a prophecy. It is the low end of a scenario that uses conservative cleanup costs and explicit assumptions. Of the roughly one million production-ish vibe-coded apps in the model, 100,000-150,000 would need professional remediation in the next 12 to 18 months at $30K or more each. The exact market size will move. The invoice already exists. If you have a vibe-coded app in production and want a straight read on what it would cost to harden, or you are about to ship one and want to understand the trade-off before you do. book a call. We will tell you what we would actually do, in the order we would do it, with numbers attached. Move fast. Stay small. Build big. The first two are why vibe coding feels right. The third is why senior engineering still wins. --- ### The $10K/month CTO You Don't Need Yet URL: https://appssemble.com/blog/fractional-cto-buys Why early startups often need senior engineering execution before a fractional CTO retainer. A vibe-coded startup usually asks the CTO question right after the first real traction. You shipped with Lovable, Bolt, Cursor, or a stack of AI-assisted prompts, users are showing up, Stripe is moving money, and suddenly the product feels too real to keep winging. The instinct is to "get serious" by hiring a CTO. Most of the time, that is the wrong first move. At this stage, you need senior judgment and execution capacity, and a fractional CTO only buys one of those. A fractional CTO buys judgment, not shipping The honest fractional CTO market is not pretending to be a dev shop. The best practitioners sell experienced technical judgment: architecture decisions, technical due diligence prep, vendor selection, security baseline, roadmap sequencing, and help with when to hire your first engineer. That work is valuable. A good fractional CTO can stop you from building the next six months on a bad database model, a fragile auth layer, or infrastructure that only works because nobody has load-tested it yet. Longstanding defect-reduction research puts severe post-delivery software problems at up to 100x the cost of fixing them during requirements and design. Architecture decisions can follow the same curve because they touch the database, auth, infrastructure, and every feature built on top. The limit is just as clear. A fractional CTO usually does not pick up tickets, refactor your Stripe webhook, write Row Level Security policies, or sit in your CI pipeline until the deploy is clean. You are buying a brain for part of the week, not a team that ships. That distinction matters most when you do not have engineers yet. The missing piece is Tuesday afternoon Imagine you're a non-technical founder with 4,000 users, $8K MRR, and a Lovable app that broke Stripe webhooks twice this month. You also discovered that two Supabase tables have weak RLS policies, but you do not know whether that is a one-hour fix or a rebuild trigger. A fractional CTO can tell you what is wrong. They can write the memo, prioritize the risk, explain the issue to an investor, and help you avoid hiring the wrong first engineer. That is useful, but on Tuesday afternoon the webhook is still broken. A senior engineering team handles the same decision and the work after it. They inspect the webhook flow, move secrets server-side, add regression tests, fix the RLS policies, and leave you with a deployable product instead of a better-written concern. At vibe-coded stage, the execution is not downstream from strategy; it is where the strategy becomes real. That is why we frame engineering as ownership of the stack, from schema to deploy. The people making the architecture call need to be close enough to the code to absorb the cost of being wrong. The math makes the false choice obvious For early-stage US startups, fractional CTO retainers commonly land around $5K-$15K per month, with $10K/month as a useful planning anchor. The typical engagement is roughly 10-15 hours per week, and some early-stage arrangements add 0.5%-2% equity or a smaller advisory grant. Regulated, AI, healthcare, fintech, or enterprise-heavy work can push the band higher, often into $8K-$25K/month. That is still cheaper than a senior full-time CTO. In major US markets, the role can become a $250K-$450K annual commitment once base salary, benefits, equity value, recruiting, and ramp time are included. A quality hire can take 4-6 months. If you already have an engineering team and need judgment for 10 hours a week, fractional can be the rational choice. But that is not the choice most vibe-coded startups are actually making. The real choice is whether this month's budget buys only senior judgment, or senior judgment attached to people who can merge code. If you compare only hourly rates, you will miss the point. The right question is what exists at the end of the month: a roadmap with no owner, or merged code, security fixes, deployment hygiene, and an architecture narrative you can show in due diligence. Fractional is right when a team already exists Fractional CTOs fit a narrow and useful window. You have engineers, but they need senior direction. Your tech lead is drowning in strategy, or your CTO left before a fundraise. An investor is asking hard questions, and you need someone credible in technical due diligence. In those cases, the job is not to create execution capacity from nothing. The job is to steer capacity that already exists. A fractional CTO can make the next two quarters sharper, review technical plans, pressure-test vendors, and help your team avoid expensive architecture traps. The shape breaks when there is no team behind the advice. A roadmap without builders becomes another artifact in Notion. A security baseline without someone changing code becomes a risk register. A hiring plan without anyone who can ship this week leaves your users waiting. If your product's core advantage is proprietary technology, the answer may be a full-time CTO earlier than usual. If you are pre-revenue and still deciding what to build, you probably need one or two hours with a senior engineer, not a recurring executive retainer. Your CTO hire strategy should start with the work, not the title Founders tend to compress four different options into one anxious question: "Do we need a CTO?" That question hides the actual operating choice. 1. Hire a full-time CTO: This makes sense when technology is the core business and the role needs daily ownership. It is expensive, slow to hire, and equity-heavy, so doing it before the product needs it can create a permanent mismatch. 2. Promote the first developer: This works only when that person can lead architecture, hiring, communication, and delivery. A strong first engineer is not automatically a CTO, and turning them into one too early can damage both roles. 3. Hire a fractional CTO: This buys senior direction, investor confidence, and decision support. It works when a team is waiting for better decisions, not when nobody can execute the decisions. 4. Hire a senior product team: This is the better shape when your gap is both judgment and shipping. You need someone to decide whether to rebuild the auth layer, then actually rebuild it. That last shape is where appssemble sits. We do Product Design, Engineering, AI, and Growth & Scale as one zero-to-scale arc, not as disconnected departments handing work across a wall. Due diligence is stronger when the builders wrote the story One common argument for a fractional CTO is investor credibility. That can be true, especially when investors need someone technical in the room. But technical due diligence is a deliverable before it is a title. An investor wants to know what the system does, where it breaks, who owns the risks, and whether the next stage of growth has a credible plan. The team that ran the rebuild, wrote the architecture decision records, fixed the security gaps, and owns the deploy pipeline can answer those questions with evidence. We have seen this pattern across products that had to survive real load, not demo-only systems. Grovs processes 10M+ events daily, and Semaphr manages 500K+ app sessions; neither kind of system earns trust from a title on a slide. It earns trust from production behavior, clean ownership, and a team that can explain the trade-offs because they made them. Buy the work before you buy the title The CTO you do not need yet is the title. What you need is the work: architecture judgment, security hardening, roadmap sequencing, product decisions, and code that actually ships. Fractional CTOs are not the problem. The problem is hiring fractional judgment when your startup is blocked by the absence of builders. If your roadmap needs both senior decisions and merged pull requests, buy the shape that includes both. If you're choosing between fractional judgment and a full team, book a call to talk through your stage. We will tell you whether you need an advisor, an engineering team, a full-time CTO search, or none of the above yet. --- ### Vibe Engineering, Not Vibe Coding: A Build-Log from the AI Communication Platform URL: https://appssemble.com/blog/building-ai-communication-platform How evals and human-owned architecture kept a real-time AI voice platform production-ready Real-time voice translation under 500ms across six platforms, with voice cloning and intelligent agents. That is the brief we shipped on the AI Communication Platform. It is also a brief that breaks the moment you let a coding model touch the latency-critical path or invent the rubric that decides what "good" means. We built it anyway, and we used AI heavily to do it. The trick was knowing where to point the model and where to keep our hands on the keyboard. This post is the build-log of that boundary: by our internal estimate, roughly 70 percent of the implementation scaffolding was AI-drafted and human-reviewed, while the architecture, latency path, security policy, eval rubrics, and release gates stayed human-owned. What sub-500ms across six surfaces actually demands The platform spans web, desktop, iOS, Android, Slack, and Teams, six clients, one media pipeline behind them. Here, <500ms means first translated audio byte on the optimized same-region streaming path, measured from the point where the platform has enough transcript to start translation. It is not p95 full call round-trip latency across arbitrary regions, and it is not a promise that every language or model route has the same profile. Voice flows through streaming speech-to-text, an LLM translation step, and streaming text-to-speech, with WebRTC for media transport and WebSockets for session control. LiveKit's current guidance puts cascaded STT -> LLM -> TTS streaming pipelines in the sub-second range: STT partials around 100-200ms, LLM time-to-first-token around 200-400ms, TTS first audio around 100-300ms, plus transport and turn detection. Getting a measured path below 500ms means overlapping stages, co-locating inference, controlling turn detection, and treating first audio byte, p50, and p95 as separate metrics. One caveat matters. ElevenLabs Flash v2.5 is the low-latency 32-language TTS path. Eleven v3 is the 70+ language model. The fastest path and the widest-language path are not the same route, so we benchmark and route by language instead of pretending one model gives you everything. None of those decisions are prompts. They are layout decisions, where compute lives, what runs in parallel, which buffer gets flushed first. A coding model can write a WebSocket handler that compiles and passes a unit test. We do not let it own the latency topology or the rollback criteria when your TTS first byte slips from 75ms to 240ms after a region move. That gap, between "code that runs" and "code that runs inside a real-time budget", is where the build-log starts. Imagine you are a CTO shipping a voice agent into a regulated industry. The demo works on your laptop. Then you put it in front of a customer in Frankfurt talking to an agent in Sao Paulo, and the round-trip jumps to 1.4 seconds because your inference is in us-east-1 and your TTS is in us-west-2. That is an illustrative topology failure, not a product benchmark. No prompt fixes it. A senior engineer redrawing the topology does. Why "vibe coding" the whole thing fails in production Simon Willison drew the cleanest line on this in October 2025: vibe coding is irresponsibly building software through dice rolls without caring what code is produced; vibe engineering is when senior practitioners use AI tools responsibly to accelerate their work. The 2025-2026 incident catalog from Crackr, Autonoma, and Kognitos is the negative case for the first half of that distinction. The recurring failure modes when AI authors the wrong layer are familiar to anyone who has cleaned up after a vibe-coded prototype: Lovable-generated apps shipping with missing or insufficient Postgres Row-Level Security policies, leaving private data reachable by unauthenticated users. 1.5M API keys exposed across documented vibe-coded repos. Buried business logic with no canonical place for the rule to live. Success-path-only error handling, no audit trail, logic drift across deployments as prompts evolve. Zero institutional knowledge captured in the codebase, only the model knew why something worked, and the model is non-deterministic. For a CRUD app, those are bugs. For a communication platform that handles conversations, billing meters, voice clone consent, and PII across languages and locales, they are existential. A translation that hallucinates a clause in a legal call is not a bad UX. It is a liability with a name on it. The honest version of the failure is what one developer in the catalog wrote about their own vibe-coded launch: "random things are happening, maxed out usage on api keys, people bypassing the subscription, creating random shit on db." That is what happens when you let a model author code in layers it cannot evaluate. The appssemble rule: AI ships code that evals cover Our AI service follows a one-line process, Define → Prototype → Harden → Ship, and inside that process there is a single rule that decides where AI is allowed to write code. AI ships code that evals cover. Humans write the code, the rubrics, and the policies that decide what "covered" means. That rule is not a moral position. It is operational. Hamel Husain makes the same point in his field guide: unsuccessful AI products usually fail because the team never builds a reliable evaluation system. If we cannot point at an automated eval that catches a regression in a given layer, we do not let the model author that layer. The eval is the seatbelt. No seatbelt, no AI-authored code. This split lines up with what Sourcetoad, CIO, and Mabl have been writing for the last year about senior teams: AI handles routine implementation work, boilerplate, CRUD, scaffolding, glue, test fixtures, while the critical layer stays human. Architecture, security, performance, business logic, and the rubrics that score everything else. Our 70/30 number is an internal estimate of first-draft implementation scaffolding, not a line-count audit or a claim that AI owned production accountability. Five places the boundary actually lives Here is where AI authored code in the AI Communication Platform, and where it did not. 1. Latency budget owned by humans. Sub-500ms is not a prompt; it is a layout decision. The streaming topology, the regional pinning, the preemptive generation that starts the LLM response before the user's end of turn is confirmed, all of it hand-shaped. We pick the predicates. We measure the hops. The model can write a Deepgram client adapter. It does not get to decide where the inference lives. 2. Eval rubrics owned by humans. The rubric is the asset, not the judge. In MT-Bench and Chatbot Arena, strong LLM judges exceeded 80% agreement with human preferences in those benchmark settings. That is useful, but it is not a blank check. For translation quality, voice-clone consent, and refusal behavior, the rubric is hand-written, the judge is calibrated against human labels, and deterministic checks catch what should never be subjective. Braintrust runs the regressions; LangSmith captures the traces. Neither tool decides what good means. 3. Glue and scaffolding owned by AI. Six clients, one backend, fast iteration. Swift view controllers for iOS, Kotlin fragments for Android, an Electron wrapper for desktop, and the Slack and Teams integration apps, all of them have idiomatic patterns the model is well-trained on. AI writes the first draft of the UI scaffolding, the DTOs, the parsers, the mock-driven Jest suites, the protobuf adapters between client and gateway. Humans review every diff. The acceptance bar is the test suite, and the test suite is the eval. The speedup is real by our internal delivery notes, but it only compounds because a senior engineer is reading every line before it merges. 4. Boring-but-critical owned by humans. Idempotency keys on every external tool call, durable state in Postgres instead of the context window, cheap models tried first with expensive models on retry, validation steps before every irreversible action, and per-user rate limits on top of global ones. Five patterns, one rule: written by hand, reviewed twice. A multi-tenant cost meter that attaches { customer_id, workspace_id, feature, model, environment } to every token event is not the kind of thing you want a model to invent on a Tuesday afternoon. We wrote the schema. We wrote the rollup. We wrote the dead-letter queue for when the rollup falls behind. 5. Prompts versioned like code. Every prompt is in the repo with a version tag. Every change runs against a regression bank, typically 100+ items the previous version handled correctly. If the new version fails even one previously safe item, it is a regression and the version is rejected. New prompts ship as canary deployments: 10 percent of traffic goes to variant B, the other 90 percent stays on the control, metrics are compared, and if the canary holds we promote. This is the same release discipline we use for code, because prompts are code in this product. Treating them otherwise is how logic drift creeps in. How the handoff to a human actually fires One detail worth making concrete, because it sits right on the AI/human authorship line. The platform supports handoff to a human agent: a translator stepping in on a sensitive call, a support rep taking over from an AI agent that has drifted. The trigger conditions are not LLM judgments. They are explicit predicates we wrote and version: confidence score below a threshold, frustration sentiment detected by a sentiment classifier with a published rubric, regulated-topic match against a keyword list, three failed attempts at resolution, or an explicit ask from the user. Each predicate is testable. Each one has a fixture set in the regression bank. When a predicate fires, the platform packages a structured context: a summary of the issue, account data, identified intent, sentiment indicators, prior attempts, and routes the call. The summary is LLM-generated. The decision to route is not. That distinction is a one-line policy in code, and it is the kind of thing we will not let drift into a prompt. "Can't AI eventually do all of this?" Yes, when the rubric, the latency budget, and the policy are themselves machine-readable. They are not yet, and pretending they are is how you ship the incident catalog above. The honest answer is that AI does more of the work each quarter, and the boundary moves. Two years ago we were still writing native client UI by hand; now the model writes most first drafts and we review. A year ago we were hand-writing the structured-output parsers for tool use; now Instructor and function calling cover that surface. The 70/30 split is a snapshot from this build, not a constant. What does not move is the principle: a layer becomes safe for AI authorship when there is an automated eval that can catch its failures. Until that eval exists, a senior engineer writes the code. There is a related objection worth answering. Founders sometimes ask whether evals are themselves vendor lock-in, once your rubrics live in Braintrust, are you stuck? No. The rubric is plain text and JSON; the eval runner is a thin layer on top. We have rebuilt this stack on Promptfoo, on Langfuse, on Helicone-plus-LangSmith. The point is to own the rubric, not the tool. Tools come and go. What it adds up to The AI Communication Platform, sub-500ms first translated audio on the low-latency path, six platforms, separate routes for wider language coverage, is roughly 70 percent AI-drafted scaffolding and 100 percent human-owned architecture. That is not a contradiction. It is the only ratio that lets you move fast on the parts a model is good at while keeping the parts that decide whether the product survives in production firmly in human hands. Vibe coding ships demos. Vibe engineering ships products. The difference is the eval, the rubric, and the discipline to draw a line between "AI can write this" and "I have to write this myself", and to redraw it every time the tooling improves. If you are a CTO or a founder weighing whether to own the AI work in your product or hand it off, this is the conversation we like to have. See how we build production AI without the demo-to-disaster gap. Book a call. Built by developers. Accelerated by AI. --- ### Your Supabase RLS Is Probably Wrong. Run These Five Queries. URL: https://appssemble.com/blog/supabase-rls-five-queries Five SQL checks for exposed tables, weak policies, and unsafe Supabase metadata. On May 29, 2025, Matt Palmer disclosed CVE-2025-48757: Lovable-generated apps could expose sensitive data through insufficient Supabase Row Level Security on client-controlled database requests. Vibe App Scanner reports 170+ affected apps and 303 vulnerable endpoints across 1,645 scanned Lovable apps. The exploit was not exotic: inspect the browser request, reuse the publishable or legacy anon key, and ask the REST endpoint for rows it should never return. If your app ships a Supabase key in the browser, your database is one curl away from exposing data unless every table reachable through the Supabase Data API/PostgREST layer has grants and policies you can defend out loud. These five queries take about ten minutes to run in the Supabase SQL editor as postgres. They read catalog tables only; they do not modify data. Supabase has started a 2026 rollout toward explicit Data API grants for new public tables. That helps future projects, but it does not repair existing grants or prove your policies match your tenants. Imagine you're three weeks past a Lovable launch. You have 800 sign-ups, a waitlist for the next pricing tier, and a browser bundle with an apikey header sitting in every network request. You copy that key, run https://yourproject.supabase.co/rest/v1/users?select=*, and the question is simple: does it answer? If you are not the person who owns SQL, send this to whoever can open the Supabase SQL editor and ask for screenshots of every non-empty result. The first query catches the Lovable failure mode This is the direct CVE check. If a table sits in a schema exposed through the Supabase Data API/PostgREST layer, grants SELECT to anon or authenticated, and has RLS disabled, browser clients can read every row those grants allow. Default projects usually expose public; if your API settings expose api, app, or another schema, add it to the CTE. with exposed_schemas(schema_name) as ( values ('public') -- add one row per schema listed in Supabase Data API settings ) select n.nspname as schema, c.relname as table, c.relrowsecurity as rls_enabled, pg_catalog.has_table_privilege('anon', c.oid, 'SELECT') as anon_can_select, pg_catalog.has_table_privilege('authenticated', c.oid, 'SELECT') as auth_can_select from pg_catalog.pg_class c join pg_catalog.pg_namespace n on c.relnamespace = n.oid join exposed_schemas es on es.schema_name = n.nspname::text where c.relkind in ('r', 'p') and not c.relrowsecurity and ( pg_catalog.has_table_privilege('anon', c.oid, 'SELECT') or pg_catalog.has_table_privilege('authenticated', c.oid, 'SELECT') ); Bad looks like any row. Good looks like an empty result. The fix starts with alter table public. enable row level security;, then real policies, because RLS without policies blocks browser/Data API access for anon and authenticated until policies exist. RLS without policies is still a broken app The panic fix after a security scare is often "enable RLS everywhere." That can create the opposite problem: tables that your product needs are now default-deny. With grants in place, SELECT returns no rows and writes are rejected. If you see permission denied for table, check GRANT first; Postgres denied table access before RLS had a chance to run. with exposed_schemas(schema_name) as ( values ('public') -- add one row per schema listed in Supabase Data API settings ) select n.nspname as schema, c.relname as table, c.relrowsecurity as rls_enabled, pg_catalog.has_table_privilege('anon', c.oid, 'SELECT') as anon_can_select, pg_catalog.has_table_privilege('authenticated', c.oid, 'SELECT') as auth_can_select, pg_catalog.has_table_privilege('authenticated', c.oid, 'INSERT') as auth_can_insert, pg_catalog.has_table_privilege('authenticated', c.oid, 'UPDATE') as auth_can_update, pg_catalog.has_table_privilege('authenticated', c.oid, 'DELETE') as auth_can_delete from pg_catalog.pg_class c join pg_catalog.pg_namespace n on c.relnamespace = n.oid join exposed_schemas es on es.schema_name = n.nspname::text left join pg_catalog.pg_policy p on p.polrelid = c.oid where c.relkind in ('r', 'p') and c.relrowsecurity group by n.nspname, c.relname, c.relrowsecurity, c.oid having count(p.polname) = 0; Bad looks like an active application table in this list, especially one with client-role grants. Good is empty, unless the table genuinely should not be reachable through the Data API. The minimum useful repair is a policy that names the role and filters by the current user, for example to authenticated using ((select auth.uid()) = user_id). If the table should not be reachable, revoke the client grants or move it to a private schema. USING (true) makes private tables public This is the classic AI-generated RLS bug. On private data, USING (true) lets every matching role read every row, and auth.role() = 'authenticated' only proves the caller signed in. It does not prove they own the row, belong to the tenant, or should see another customer's data. with exposed_schemas(schema_name) as ( values ('public') -- add one row per schema listed in Supabase Data API settings ) select schemaname as schema, tablename as table, policyname as policy, cmd as command, roles, qual as using_expression, with_check from pg_policies where schemaname::text in (select schema_name from exposed_schemas) and ( ( cmd in ('SELECT', 'UPDATE', 'DELETE', 'ALL') and ( coalesce(qual, '') ~* '^\(*[[:space:]]*true[[:space:]]*\)*$' or coalesce(qual, '') ~* 'auth\.role\(\)[[:space:]]*=[[:space:]]*''authenticated''' ) ) or ( cmd in ('INSERT', 'UPDATE', 'ALL') and ( coalesce(with_check, '') ~* '^\(*[[:space:]]*true[[:space:]]*\)*$' or coalesce(with_check, '') ~* 'auth\.role\(\)[[:space:]]*=[[:space:]]*''authenticated''' ) ) or ( cmd = 'INSERT' and with_check is null ) ); Bad looks like using_expression = true, with_check = true, a role-only check, or a policy you cannot explain in one sentence. A null using_expression on an INSERT policy is normal; WITH CHECK is the gate for new rows, so this query audits it separately. Good policies reference auth.uid(), a tenant column, a membership table, or a security-definer helper that makes an ownership decision. At appssemble, when we build this in engineering work, every tenant-scoped table gets the same test: why should this caller see or write this row? TO public makes anon part of the policy surface In PostgreSQL, a policy with no TO clause applies to public. In Supabase terms, that includes anon, so a policy that looked like "logged-in users can read" may still run for anonymous browsers if the table grants and policy expression allow it. with exposed_schemas(schema_name) as ( values ('public') -- add one row per schema listed in Supabase Data API settings ) select schemaname as schema, tablename as table, policyname as policy, cmd as command, roles, qual as using_expression from pg_policies where schemaname::text in (select schema_name from exposed_schemas) and ( roles = '{public}' or 'anon' = any(roles) ) and cmd in ('SELECT', 'ALL'); Bad looks like {public} or anon on a user-data table. This is not automatically a breach; a public marketing table may intentionally allow anonymous reads, and missing grants still block access. It is a review list for private tables, not a verdict by itself. Good looks like to authenticated on every private table, with a small, explicit whitelist for content that is genuinely public. If you meant "any signed-in user," write that; if you meant "the owner," write the owner check too. raw_user_meta_data turns client updates into admin rights Supabase users can update their own user metadata from the client. That makes raw_user_meta_data and user_metadata the wrong place to store authorization flags like role = admin. with exposed_schemas(schema_name) as ( values ('public') -- add one row per schema listed in Supabase Data API settings ) select schemaname as schema, tablename as table, policyname as policy, cmd as command, qual as using_expression, with_check from pg_policies where schemaname::text in (select schema_name from exposed_schemas) and ( coalesce(qual, '') ilike '%raw_user_meta_data%' or coalesce(qual, '') ilike '%user_metadata%' or coalesce(with_check, '') ilike '%raw_user_meta_data%' or coalesce(with_check, '') ilike '%user_metadata%' ); Bad looks like any row. Good is empty, with authorization stored in server-managed app_metadata, or in a dedicated roles table checked through a security-definer function. JWT claims can be stale until refresh, so use the roles-table path when fast revocation matters. The difference is not style; it is whether a signed-in user can promote themselves with one client call. The Security Advisor is a start, not a verdict Supabase's Advisor and Splinter checks are worth running. They cover disabled RLS, RLS enabled with no policy, policies on RLS-disabled tables, user-metadata references, permissive policy patterns, sensitive exposed columns, materialized or foreign tables in the API, public bucket listing, and the auth_rls_initplan performance warning. They are still not a full RLS audit. They will not read your product model and decide whether USING (true) is fine for blog_posts and catastrophic for user_profiles. That is why we still dump pg_policies and read the policies line by line. These five queries check table policies; they do not audit views, RPC functions, Storage buckets, GraphQL exposure, service-role leaks, or semantic tenant bugs. On large tables, we also check the PostgreSQL RLS auth.uid() performance pattern: wrapping auth.uid() as (select auth.uid()) and indexing columns like user_id or account_id has been shown in Supabase benchmarks to produce 100x+ speedups. A correct policy that times out at 100,000 rows is still not production-ready. This is also why internal ownership matters. Grovs processes 10M+ events daily, and that kind of load does not forgive vague access rules, missing indexes, or wishful thinking about defaults. The same discipline applies to a 100-user Supabase app before it becomes a 100,000-user problem. Run Query 1 before the next feature The lesson of CVE-2025-48757 is not that Supabase is unusable. The lesson is that vibe-coded apps often stop at "RLS is on" when the real question is "which rows can this role read, write, and mutate?" Run the five queries. If any of them return rows on tables that hold user data, do not ship the next feature first. Fix the policies, test them as different users, and if you want a second pair of eyes on the schema, book a call. --- ### The True Cost of a Vibe-Coded App Is Not $25/Month URL: https://appssemble.com/blog/true-cost-of-vibe-coded Why $25/month AI prototypes can become six-figure production liabilities The pitch is simple: pay $25/month, describe your app, and ship an MVP by Friday. The real cost of vibe coding tools starts showing up later, when the bug loop eats your credits, a paying customer hits a broken flow, or the first enterprise lead asks whether your stack can pass SOC 2. We are not against founders using AI to move faster. We use AI in our own engineering work every day. The expensive mistake is treating a prompt-built prototype as a production product before any senior engineer has read the code, tested the architecture, or priced the risk. For a founder with production users, the honest MVP cost comparison is not "$25/month versus a development team." It is "$25/month plus bug loops, incidents, churn, compliance work, and a likely rewrite" versus building the first version with people who can keep owning it after launch. One framing note before the math: this is a TCO model, not a universal invoice. The early-founder case is a pre-seed or seed app with paying users, private data, and a scary enterprise lead. The Series A numbers appear only where the model needs a larger customer base to price churn. Where a number comes from vendor/community reports or a modeled benchmark, we label it that way. The $25/month number is the wrong unit Lovable's Pro plan starts at $25/month. Bolt's Pro plan sits around $20-25/month. Replit Core is $20/month on annual billing, with usage credits attached. Those numbers are real, but they describe the entry ticket, not the product cost. HatchWorks' public cost model puts production-app usage at $500-$2,000+ per month before you count your own time or a single customer-facing failure. Even the small numbers are misleading because credits are consumed by attempts, not outcomes. Lovable's Pro tier gives roughly 100 credits per month, and complex features can consume more than one credit per request. A founder does not buy "auth works"; they buy another attempt at making auth work. Imagine you're a non-technical founder building a B2B invoicing app. The first demo looks good on Wednesday, but by Friday the export flow breaks, the dashboard totals disagree with the PDF, and every "fix this" prompt changes two screens you did not ask it to touch. Your $25/month mental model is already gone. The bug loop is where cheap starts getting expensive The most painful cost is not the subscription. It is the loop where the tool fixes one bug and introduces the next one. DesignRevision's 2026 analysis of 200+ public discussions and reviews reported that 65-75% of developers encounter bug loops during complex feature builds. Treat that as a vendor/community benchmark, not a formal market-wide base rate. The same analysis puts Lovable satisfaction above 85% for landing pages and above 80% for visual prototypes, but only 40% for SaaS with payments, 20-30% for complex SaaS, and 15-20% for multi-user platforms. That split matters. Vibe coding is good at the first visible 80%: screens, flows, simple CRUD, a demo that helps you learn. It struggles with the last 20%: permissions, migrations, edge cases, tests, observability, retries, and the weird state that only appears after your tenth real user. This is why founder credit stories cluster around the same pattern. One Trustpilot reviewer said they "wasted 1000 credits," roughly EUR500. Another said they spent more than $100 in credits trying to fix one issue with no result. Bolt users report the same shape, including $1,000+ in tokens spent just trying to repair generated code. Production failures cost more than credits Once your app holds real data, security debt stops being an engineering concern and becomes a company-level cost. CVE-2025-48757 is the cleanest early example we have in the vibe-coded app category. Researchers scanned 1,645 apps from Lovable's own showcase and found 170 apps, or 10.3%, with critical Row Level Security failures across 303 vulnerable endpoints. Matt Palmer's disclosure scored the issue at 8.26; several CVE databases classify it as critical at 9.3. The exposed data included names, emails, phone numbers, home addresses, financial records, and personal debt amounts. Separate from that CVE sweep, a February 2026 EdTech exposure showed the same failure class in a more concrete product. A Lovable-built app reportedly exposed 18,697 user records, including 14,928 emails, 4,538 student accounts, and 870 records with full PII. That was not "one app from the original CVE scan." It was a later public example of the same production boundary being crossed without real access control. This was not an exotic failure. The root cause was missing or incomplete Supabase RLS policies combined with client-side access that let anyone query the database directly. That is the kind of bug a production engineering practice catches before launch, because the review starts with "what can the anonymous client read?" Downtime has the same shape. Enterprise benchmarks often cite $300,000+ per hour, but that is not the number most early founders should model. Use a conservative modeled SMB figure instead: $10,000 per hour for a customer-facing outage once you have paying customers, support load, refunds, and lost trust. In a stress case, three serious incidents in a year, four hours each, at $10,000 per hour is $120,000. That is the entire "cheap MVP" argument erased by deployment stalls, broken auth, a database exposure, or a function timeout at the wrong moment. Churn is the bill founders forget to model Bug-driven churn rarely appears in the first budget because it does not look like a vendor invoice. It looks like trial users who never activate, accounts that stop expanding, and customers who quietly decide your product is too risky. The baseline is already harsh. Pre-product-market-fit SaaS churn is often modeled around 8.2% monthly. First-year SaaS can run 10-15% monthly, and some benchmarks show up to 24%. Autonoma's Series A worked example makes the formula concrete: 4% bug-attributed annual churn across 300 customers at $8,000 ACV is $96,000 in lost ARR. A breach causing 10% churn against the same base is $240,000 in ARR gone before direct response costs. Do not map that dollar amount back onto a pre-seed app one-for-one. Map the formula: customers times ACV times the percentage of revenue lost because the product broke trust. The smaller version hurts too. A 30-day vibe-coded MVP diary reported $127 in Replit credits, 73 rollbacks, 2 signups, and 0 completed onboardings. At that stage, churn is the product failing before the first customer can trust it. The rewrite bill arrives after traction The rewrite makes the original saving look fake. Once the app has real users, messy generated code, missing tests, weak permissions, and founder-only context, you either harden it or rebuild it. Migration pricing alone is not the rebuild. NextLovable lists white-glove Lovable Cloud to Supabase migration around $3,500, Next.js migration up to 20 pages around $4,500, and complex migrations at $7,500+. That gets you off the platform. It does not necessarily fix the application logic. Professional cleanup and rebuild numbers are higher. Treat these as vendor/community benchmarks, not universal quotes: $1,000-$10,000 for quick fixes, $5,000-$30,000 for smaller professional rebuilds, and $50,000-$150,000 for a full custom MVP depending on integrations, users, payments, and regulation. Forcoda's worked example is the cleanest modeled comparison: $2,000 in vibe-coding tools, $20,000 in founder time, and a $65,000 custom rebuild, for $87,000 total. Their custom-coded-from-day-one path came in at $50,000 over 18 months. You saved money in month one and lost the comparison by month eighteen. The 18-month TCO is the only honest comparison Here is the model from the research, compressed into founder terms. Path A is the vibe-coded route: Lovable, Replit, DIY fixes, production users, then remediation. Path B is a senior-built MVP from day one. The assumptions matter: Scenario: B2B SaaS with production users, private customer data, payments or accounting flows, and at least one enterprise sales motion. Stage framing: the low end maps to an early founder; the churn exposure uses a Series A-style stress case of 300 customers at $8,000 ACV. Incident cost: modeled at $10,000 per customer-facing outage hour, not claimed as a universal observed average. Rewrite scope: migration plus senior rebuild inside 18 months, with SOC 2 work triggered only if enterprise procurement appears. In that modeled scenario, Path A lands at $198,000-$736,500 over 18 months with tools, bug-loop credits, hosting, founder time, incidents, churn, migration, rebuild, and first-year SOC 2 work. Remove customer-facing incidents, bug-attributed churn, and breach-churn entirely, and it still lands around $78,000-$200,000. Path B lands at $103,000-$244,000 over the same 18 months: a $50,000-$75,000 custom MVP, ordinary tooling, hosting, lower incident exposure, lower bug-attributed churn, SOC 2 work, and maintenance. The crossover is the point. Vibe-coded only stays cheaper if the app remains a prototype, never handles paying users, and gets abandoned before the rewrite. Once you keep the company alive, the senior path often becomes cheaper inside 12-18 months. Vibe coding is useful when you respect the boundary Founders should still use these tools. Build five landing pages. Mock three onboarding flows. Test a pricing page. Put a prototype in front of ten customers before you spend serious money. That is the high-satisfaction zone: landing pages above 85%, visual prototypes above 80%, and simple internal tools around 65%. The tool works when the output teaches you what to build next and nobody is depending on it for security, billing, or operational truth. The boundary is production. When you add payments, private customer data, multi-user permissions, accounting exports, compliance questions, or uptime expectations, you are no longer buying a prototype. You are accumulating technical debt, security debt, and SaaS compliance costs in the same codebase. Before you keep prompting, ask an engineer to verify six things: RLS policies, server-side payment verification, secret placement, production logs, test coverage around money flows, and the rollback path. If those are missing, the problem is not AI-generated code. The problem is unowned production code. At appssemble, our answer is not "use less AI." It is "put senior engineering around the AI." We use AI to move faster, but every accepted line still has an owner, tests still run, permissions still get reviewed, and the same team stays with the product from first release to scale. The cheap path is not always the cheaper path The real question is not whether you can launch something for $25/month. You can. The question is whether that something survives users, audits, incidents, and the next six months of product work. Model your own 18-month TCO before you choose the cheap path. If incidents plus churn plus rewrite stack into six figures, the senior path can become cheaper inside the first 9-18 months. If you want us to pressure-test that model against your actual app, book a call. --- ### From Lovable to 100K MAU: the six-week rebuild we'd do again URL: https://appssemble.com/blog/lovable-to-100k-users-six-week-rebuild A six-week rebuild plan for scaling Lovable apps to 100K MAU without a full rewrite. 100K monthly active users is where many vibe-coded stacks start showing their real shape. It is rarely raw traffic, Vercel and Supabase can technically serve it. It is spiky dashboard load, serverless connection bursts, RLS policies doing sequential scans on large tables, request handlers pretending to be job queues, type drift between client and server, and an auth schema nobody can safely migrate because it is load-bearing for the live app. We have rebuilt enough of these to know the path is short and unglamorous. Six weeks. Next.js App Router on the front, Drizzle as the schema source of truth, Supavisor in front of Postgres, Inngest for jobs, Sentry from day one. This post is the week-by-week plan, the numbers behind every decision, and the gotchas that bite teams trying to do it themselves. Why 100K MAU breaks Lovable-shaped apps Lovable, Bolt, and v0 share the same ceiling: they get you about 70% of the way to production. The remaining 30% is complex business logic, edge cases in authentication, payment flows, and data validation, exactly the parts that hold up under real users. The common output we inherit is a Vite + React SPA that calls Supabase directly from useEffect hooks with the anon key, default Supabase Auth templates, no real job system, and no observability beyond the browser console. That stack ships an MVP in a weekend. It also fails in five predictable ways once traffic shows up: Connection storms. Supabase connection limits depend on compute size and connection path. A Micro project currently lists 60 direct connections and 200 pooler clients; Large lists 160 direct and 800 pooler clients. Serverless code can still stampede those limits if every request opens its own connection. Unindexed RLS. A naive user_id = auth.uid() policy can force Postgres into bad plans if user_id is not indexed. Supabase's own RLS benchmark on a 100K-row table shows indexing the policy column taking one test from 171ms to under 0.1ms. Background work in request handlers. Sending an email from a Next.js route is not a job queue. Vercel function limits now vary by runtime, plan, and Fluid Compute settings, but the failure mode is the same: user latency, retry ambiguity, duplicate side effects, and poor visibility. Type drift. Vibe-coded apps lean on any. The codegen step gets skipped. Server and client disagree on shapes silently. Security debt. Do not publish a vulnerability percentage unless you can name the scan and methodology. The source-safe version is still ugly: GitGuardian's 2026 secrets report says about 29M new hardcoded secrets hit public GitHub commits in 2025, and AI-assisted commits leaked secrets at roughly 2x the public baseline. Imagine you are scaling fast: a TikTok mention or one good B2B launch thread sends thousands of users into a private dashboard at 9pm on a Tuesday. The pooler client limit starts climbing, every dashboard query waits behind slow RLS, one unhandled error in a React component takes the whole app down because nobody added an error boundary, and Sentry is not installed so you find out by reading angry replies the next morning. That is the failure mode we get hired to fix. If you send this post to your engineer, ask for three numbers before week 1 starts: current peak concurrent database connections, p95 dashboard query time under an authenticated test user, and the auth-provider bill at 100K monthly active users. The good news: the Lovable app is the spec. The domain model is encoded. The UI is a reference implementation. The team is small. That is exactly the setup that makes a six-week rebuild possible, and a 90-day build unnecessary. The six-week plan The plan below is composite, synthesised from a dozen rescues we have done and from public postmortems like the OnboardingHub Rails rewrite (8 weeks, 727 commits, 25-45 hours of human effort because the architecture document was reverse-engineered from a working product). We compress it to six because the spec already exists and we do not let the team drift into "while we are here" rewrites. The six-week clock only works under three constraints: keep the auth provider, keep the core product scope, and treat the existing app as the spec. Change any two of those and this becomes a 90-day rebuild. Week 1: Audit, freeze, forklift Run a dependency and security audit on the Lovable export. Identify hardcoded secrets, missing error boundaries, missing RLS, missing indexes. Forklift the Vite + React SPA into a Next.js App Router skeleton, components stay, data-fetching dies. Keep the Supabase project live and untouched; clients still talk to it. Set up a parallel staging Supabase project for destructive testing. Decisions made in week 1, written down: What stays: UI components, copy, brand, route structure. What dies: every supabase.from(...) call inside a useEffect, every client-side join, every RPC glued together with any types. What gets added immediately: per-route error boundaries, Sentry SDK with session replay, a basic CI pipeline (typecheck, lint, unit, Playwright on preview). Sentry goes in week 1, not week 5. You will not find half of the bugs without session replay because most AI-generated code does not handle session expiration mid-flow. Week 2: Schema as source of truth Pull the live Supabase schema into a Drizzle file. Drizzle wins over Prisma here for one specific reason: Prisma's drift detector can trip on Supabase auth schema changes, and that is a long-running open issue. With Drizzle, the application schema lives in TypeScript and there is no separate Prisma-style client-generation step. You still generate and review migrations; you just remove one common source of type drift. Then the database cleanup: Add an index on every column referenced inside an RLS policy. Every one. Wrap auth.uid() in (select auth.uid()) so the optimiser caches the result via initPlan instead of running it per-row. Replace cross-table joins inside RLS policies with denormalised tenant columns. Split read policies (RLS) from write policies (server-only via service role). The performance delta is not subtle. Supabase's published RLS tests show 100x-plus improvements from indexing policy columns, and some function-wrapping cases move from seconds to single-digit milliseconds. Do not copy those numbers into your investor deck; use them as the reason to run EXPLAIN (ANALYZE, BUFFERS) on your own top five authenticated queries. Week 3: API layer, type safety, edge Replace ad-hoc client calls with a tRPC router or typed Server Actions. The point is not religious, it is that tRPC eliminates the API contract drift class of bug entirely, and Server Actions do the same for simple mutations. Reads move to React Server Components. Public-cacheable list routes get ISR with Cache-Control: s-maxage=60, stale-while-revalidate=300. One gotcha worth circling: the edge runtime is not compatible with ISR. Use the Node runtime for ISR routes and reserve edge for middleware (auth checks, geo, A/B). Mixing them up costs a day of debugging cache misses. Target by end of week 3: 80%+ cache-hit ratio on public routes. That single number eats more Postgres load than any tier upgrade. Week 4: Auth, RLS audit, background jobs The auth decision is the one founders agonise over and the one with the clearest answer at this scale. As of May 2026, the source-safe table looks like this: Provider100K-user framingWhat we would doSupabase AuthPro is $25/month and currently includes 100K MAU; overage starts after that quota.Keep it if the product already uses Supabase and does not need enterprise SSO right now.ClerkCurrent public pricing advertises 50K monthly retained users included, then $0.02 per additional retained user in the next band, plus the Pro base and feature add-ons.Use it when the product needs Clerk's UI, session, org, or enterprise-connection features enough to justify the bill.Auth0The public page exposes self-serve tiers and custom user tiers; a clean 100K B2C price is not safe to publish without a live quote.Quote it directly if procurement, enterprise identity, or compliance is the reason you are moving. Keep Supabase Auth at 100K MAU unless you have a specific reason not to. Clerk can be worth the spend if its user-management features save you weeks of product work, but the decision is no longer "Clerk is cheap below 50K and impossible above it." The decision is whether you want a dedicated auth product enough to pay for it as retained users, orgs, SSO, domains, and support needs grow. Migrating between providers is painful, it touches every authenticated route, every session token format, every password reset email. Do not do an auth migration during a six-week rebuild unless auth is the actual reason for the rebuild. Then move all background work, emails, embeddings, webhook fan-out, retries, out of Next.js handlers and into Inngest. If you are deploying serverless, BullMQ is the wrong choice unless you also stand up a separate persistent worker process. Inngest is the default for Vercel-native; Trigger.dev wins for AI workflows with many steps. Either way, this is a 1-day refactor that fixes multiple incident classes at once. Week 5: Caching, observability, load test Sentry is already in. Add Axiom or Logtail for structured logs. Skip the full Datadog rollout at this scale unless you already have a team that knows how to run it. The problem in week 5 is not buying the biggest observability platform; it is making errors, traces, logs, retries, and user sessions visible enough for a small team to debug production. Run a k6 or Artillery load test against staging at 3x expected peak. Tune the Supavisor pooler, transaction mode for short queries, session mode only where you need prepared statements. Confirm CDN cache hit ratios in production-like conditions. Proper CDN configuration is the difference between a 90% hit ratio and a sluggish worldwide experience. The numbers we want to see leaving week 5: p95 server response time under 200ms on cached routes, under 600ms on uncached. Cache hit ratio above 80% on public list/detail routes. Pooler usage staying comfortably under the documented client limit for your Supabase compute tier under 3x load. Sentry error rate under 0.5% of requests in staging soak tests. Week 6: Cutover and cleanup If you are staying on Supabase, the cutover is just deploying the new Next.js app to Vercel or to a Hetzner VPS via Coolify, then flipping DNS. Smoke tests, watch Sentry for 30 minutes, rollback plan armed. If you are leaving Supabase, the cutover uses Postgres logical replication. The mechanics matter: Provision target Postgres at the same major version or higher. Add a primary key (or REPLICA IDENTITY FULL) to every table receiving UPDATE or DELETE. Open a direct connection to the source, port 5432, not the pooler. Logical replication requires it. Create publication on source, subscription on target. Wait for backfill, verify row counts and a sample of recent rows. At cutover: pause writes (or queue them in Inngest), wait for replication lag to hit zero, flip the connection string, resume writes. Run the app in dual-read mode for 24h if paranoid; otherwise monitor Sentry and keep a one-command DNS rollback ready. Total downtime measured in minutes, not hours. Tear down the Lovable preview once the new domain has been live for a week. Database move: stay or leave The Supabase question comes up every time. Two paths, pick on lock-in tolerance and budget. Stay on Supabase, fix what is broken. Cheapest, fastest. Pro is $25/month and currently includes 100K MAU, 8 GB database, and 100 GB storage, with usage-based fees after the included quotas. A Large compute add-on is about $110/month before the paid-plan compute credit if the workload needs dedicated CPU. The Team plan jumps to $599/month, only worth it for SSO, SOC 2, and 28-day log retention. For many 100K-MAU SaaS products, Pro plus a measured compute upgrade and the pooler is enough. Leave Supabase for managed Postgres (Neon, Render, RDS, Hetzner-hosted). Reasons that justify it: cost predictability above ~250K MAU, escaping the auth schema, or needing extensions Supabase does not ship. The migration mechanic is the logical replication recipe above. Do not leave for the sake of leaving: the auth schema alone makes it a multi-week project. Either way, put the right pooler in front of Postgres before the cutover. Supabase includes Supavisor, but the usable ceiling is tied to your compute tier: current public pricing lists 200 pooler clients on Micro, 800 on Large, 3,000 on 4XL, and only reaches five figures on the largest compute tiers. The right lesson is not "Supavisor gives every app 10,000 connections." The lesson is that transaction pooling protects Postgres from serverless spikes, and you should test the added latency from your region and workload. The cost envelope Two real-world bills for the same Next.js + Postgres + auth + jobs stack at three traffic tiers. These ranges were checked in May 2026 and reflect SSR-heavy versus static-heavy workloads, team size, included quotas versus overages, and whether someone is paid to own the VPS. Layer1K MAU10K MAU100K MAUHosting (Vercel Pro)Free-$20$20-60$100-500+Hosting (Hetzner + Coolify)$4-10 app server$7-25 app server$20-80 app hosting onlySupabase DB/platformFree$25 Pro$25 Pro + compute if neededSupabase Auth incremental$0$0$0 while under Pro's included 100K MAUClerk, if replacing authFreeUsually free unless paid features are neededAbout $1,025+ for 100K retained users before org/SSO/domain add-onsBackground jobs (Inngest)FreeFree if under Hobby limits$75+ once Pro limits are neededSentryFree-$26$26$26-80+ before event overagesAxiom logsFreeFree-$25$25+ depending ingest and retention A founder running Vercel Pro + Supabase Pro + Clerk at 100K retained users is no longer automatically looking at the old $2,000-plus auth math. Under current public Clerk pricing, a simple 100K retained-user calculation is closer to $1,025 before orgs, SSO, satellite domains, Business features, and overages. The same product on Supabase Auth avoids that incremental auth line while it stays under the Pro included quota. That gap is still real. It is just not a fake 10x spreadsheet you should defend without reading the pricing pages. The bandwidth piece is worth pulling out with the right caveat: Vercel Pro currently includes 1TB of Fast Data Transfer, then starts at $0.15/GB. Hetzner EU cloud servers include at least 20TB and charge about €1.00 / $1.20 per extra TB in EU and US regions. That comparison only matters after included buckets and regional rules, but for 500K+ MAU on a media-heavy app, the bill can diverge fast. Our default recommendation for a post-Lovable rebuild at 100K MAU: start on Vercel Pro + Supabase Pro + Supabase Auth + Inngest + Sentry. Move to Hetzner + Coolify when the Vercel bill is painful enough to fund the operational work, or when you have someone on the team who actually wants to own infra. Not before. RLS gotchas we see every time Most Lovable exports we have rebuilt have at least one unindexed RLS column and at least one of the following landmines: Default-off. New Supabase tables ship with RLS disabled. Lovable-generated tables often inherit this. Run the Security Advisor in week 1, fix every flagged table, redeploy. Empty-result silent failures. Enable RLS but forget the policies and every query returns empty results, no error, just a dashboard showing nothing. This is the single most common "the app is broken" report we get. Superuser blind spot. The SQL Editor runs as the postgres superuser, which bypasses RLS. You test queries there, see the expected results, ship, and real users see nothing. Test policies with set role authenticated or via the actual app under a test user. UPDATE needs SELECT. To run an UPDATE under RLS, you also need a corresponding SELECT policy. Without it, the UPDATE silently fails for the user. Read via RLS, write via service role. Cleanest production pattern: route mutations through a server with the service role key, keep RLS only on the read path. This only works if the server owns authorization checks and the service role key never leaves the server, because that key bypasses RLS. What we would not do again A short list, paid for in our own incidents: Auth migration during a rebuild. Migrate auth in its own quarter. Six weeks is not enough room. Cache-after-scaling Postgres. ISR and edge cache can shed most read traffic on public routes. That is cheaper than reaching for a bigger Postgres tier first. Background jobs in API routes. A function timeout setting is not a job queue. Move to Inngest in week 4, it pays itself back in week 5. Skipping observability until "later." Sentry installs in 20 minutes. The first time a paying customer reports a bug you did not see, you will wish it had been week 1. Treating the schema as a side effect. Pin it in Drizzle. Generate migrations. Review them in PRs. The database is the product. Six weeks is a rebuild, not a rewrite The reason this works in six weeks is the same reason it does not work in six weeks for a greenfield product: the Lovable app is the spec. The domain model is fixed. The UI is a reference. The decisions that take a discovery sprint on a new product, what does the dashboard show, what is in a user record, what triggers an email, are already answered. The job is to take those answers and put them on a stack that survives the next 10x. If your Lovable, Bolt, or v0 app caught traction and is starting to wobble at 100K MAU, this is the path we would walk you down. We have rebuilt a dozen of these in six weeks. Same team that does the rebuild stays for the engineering work after, day one to scale, no handoffs. Book a call. Bring your Supabase project, your Sentry alerts, and your last invoice. We will tell you in 30 minutes whether the right move is six weeks of rebuild or six months of rewrite. --- ### React Native or native iOS for your Lovable v2? Here's how to decide in 2026 URL: https://appssemble.com/blog/react-native-vs-native-ios-v2-decision-tree A founder-focused decision tree for choosing React Native or Swift for a Lovable mobile v2 in 2026 Most founders we talk to still cite Airbnb's 2018 sunsetting of React Native as proof the framework is broken. It's the load-bearing piece of evidence in nearly every "we should go native" Slack thread we get pulled into. The problem is that the architecture Airbnb actually complained about: the JSON-serialized bridge, the async first render, the missing native-module ergonomics, isn't the architecture you'd ship on today. If your v1 is a working Lovable web app and you're staring down a mobile build, the choice between React Native and native iOS in 2026 isn't about a fundamental performance gap. It's about your team, your platform count, and what your app actually does at the screen level. We've built mobile products on both stacks for almost a decade, including Semaphr, our feature-flag and remote-release tool that manages 500K+ app sessions across iOS and Android, and the decision tree we use with founders looks nothing like the one floating around on X. Here's the version we actually use. What changed since Airbnb left Airbnb's 2018 post is still online and worth reading, but read it as a 2018 document. Gabriel Peal was specific: the team hit walls with "initialization and the async first render" and with "supporting code on three platforms instead of two." The bridge: the chunk of React Native that serialized every JS-to-native call into JSON and shipped it across an asynchronous boundary, was the technical root cause of most of the pain. That bridge is no longer the runtime path a new 2026 project should be planning around. React Native 0.76 made the New Architecture the default, 0.82 made it the only runtime path, 0.84 made Hermes V1 the default JavaScript engine, and 0.85 is the current stable release as of May 2026. Fabric, TurboModules, Codegen, Hermes, and JSI move JS/native interop away from JSON serialization and toward direct native interfaces. Third-party migration guides report large old-architecture to new-architecture gains, but we would not use those numbers as neutral RN-vs-Swift benchmarks. The honest read: React Native caught up on the things that used to be obviously broken. It is not equivalent to native on bleeding-edge features, and we'll be specific about which ones below. But anyone using 2018 Airbnb as a reason to skip RN in 2026 is arguing against a framework that doesn't ship anymore. The counter-evidence has been piling up, but it needs to be read precisely. Shopify migrated all of its mobile apps to React Native and reports sub-500ms P75 screen loads with greater than 99.9% crash-free sessions. Its earlier 2020 post reported 95% shared code in Arrive and 99% in Compass; the 2025 retrospective focuses on feature parity, productivity, and native escape hatches rather than one company-wide sharing number. Coinbase's 2021 migration moved 200+ screens of a 56M-user app off native, retrained 30+ native engineers, and ended up with 113 contributors on the React Native repo, many of them web engineers who previously could not ship mobile code at all. The pattern is clean: companies with strong web engineering cultures keep choosing React Native; companies with strong mobile-native cultures keep choosing native. Airbnb in 2018 was the latter. Most founders coming out of a Lovable v1 in 2026 are the former. When native iOS still wins in 2026 There is a real list of features where native produces a meaningfully better product, and we won't pretend otherwise. If your v2 lives in any of these categories, write Swift or budget native platform code for the hot path. ARKit, Metal, custom shaders. RN bindings exist, but maturity varies and Apple APIs land in Swift first. Complex HealthKit writes, ResearchKit, CareKit, and Apple Watch companions, community packages can read HealthKit, but writing is fragile and you need physical devices to even test. Bluetooth Low Energy with strict timing for medical devices or hardware peripherals; every team we know that hits BLE at scale ends up writing a native module anyway. Sub-16ms gesture-driven UI for drawing apps, music apps, advanced camera filters, possible in RN with Skia plus Reanimated 3, but the tax is high. CarPlay, Live Activities, Dynamic Island, and long-running background work may need custom native modules even when the rest of the app is React Native. A practical heuristic we use with founders: if a feature is on the WWDC keynote, budget native work for it. Sometimes a binding appears quickly. Sometimes it does not get mature enough for your product before your launch date. There's also the App Store review angle. Apple Guideline 4.2, "Minimum Functionality," asks for features, content, and UI beyond a repackaged website. If your v2 strategy depends on App Store discoverability and you're tempted by a Capacitor wrap, which loads your existing Lovable build inside a WKWebView, add mobile-specific functionality before submission: push, biometric login, camera capture, offline mode. A straight website-in-a-wrapper materially increases 4.2 rejection risk. When React Native is the only realistic answer There is one founder profile for which React Native isn't a debate: web-first team, both platforms needed, six to ten weeks to TestFlight. If that's you, native is not on the table, not because RN is technically superior, but because the math doesn't work. The planning math usually favors RN for two-platform products: one shared app means less duplicated feature work, one QA path, and fewer specialist hires. Third-party agency comparisons often estimate 30-50% cost savings versus two separate native builds, Netguru reported one Swift build taking 33% longer than its RN equivalent, and in our own greenfield work we have measured 43% less calendar time on comparable two-platform apps. Treat those as planning ranges, not laws. Two native apps require two specialists (Swift plus Kotlin) plus design and QA on both platforms. One RN app with a small native escape hatch typically requires 1 to 1.5 engineers to ship the same feature set. Imagine you're a founder with a Lovable web app at $30K MRR, your investors are pushing for a mobile launch before your seed extension, and you have one React engineer and a part-time designer. In our hiring work, senior iOS specialists in NYC or SF are usually slower to find than senior React engineers, and that can eat the entire quarter you're trying to ship inside of. Public survey data points the same way: JavaScript and React are much more common than iOS-specific tooling. The salary gap moves by source and city. The recruiting timeline is what we plan around. This is why Coinbase's 2021 headline reason for switching was not raw performance. It was team economics. The "113 contributors" number is the point: the adjacent React pool is larger than the iOS-specialist pool, and for any company that already writes React on the web, the mobile contributor pool grows the moment you commit to RN. Where founders trip: Lovable's code doesn't carry over either way Here's the catch. Lovable outputs React DOM: div, span, input, button. None of those components exist in React Native. Lovable's own FAQ confirms it does not build React Native apps and does not export to Expo. What does carry over: your Supabase backend, your auth, your API contracts, your database schema, your business logic, your design tokens, your copy, your validated user flows. What gets rewritten: every screen. This is true whether you go React Native or native iOS. So "we'll just port the JSX" is not on the menu. The third-party tools claiming "Lovable for mobile", RapidNative, CatDoes, and Newly, are RN code generators. The output is React Native code that still needs an engineer. Useful as scaffolders, dangerous as production sources of truth, and the same caveat that applies to Lovable applies to them. Plan for a screen-layer rewrite. Budget six to ten weeks for a small app, twelve to twenty for a real one. The good news is that everything below the screen survives, which is usually 60-70% of the engineering work. The watch-out: don't let anyone sell you "just as fast" We need to be direct about something the React Native community sometimes oversells. RN on the New Architecture is not equivalent to native iOS on every dimension. It caught up on the 2018 issues: bridge serialization, async first render, and native-module overhead. It is genuinely production-grade for the lane Shopify and Coinbase live in. It is not better than Swift on memory, on bleeding-edge Apple APIs, or on the things Apple ships at WWDC. Shopify is also honest about the maintenance tax: native specialists still matter for build and release, version updates, platform APIs, performance tuning, and React Native dependency upgrades. In our planning, that means budget maintenance every release cycle. Do not sell RN as a no-native-maintenance stack. Someone still needs to own App Store release engineering, native dependency compatibility, device testing, and crash/performance telemetry. Shopify's framing is the one we'd repeat to any founder: "100% React Native should be an anti-goal…think native and React Native." The mature stack for a serious mobile product is RN for CRUD, lists, dashboards, content feeds, and forms, plus a native module for any hot path that needs it. Pretending you can do everything in JavaScript is how you end up with a slow app and a regretful CTO. The decision tree Run your v2 through these seven questions in order. The first one that gives you a clean answer is your answer. #QuestionIf yesThen1Is mobile usage going to be under 30% and you don't need camera, push, or deep hardware?Ship a PWA from your Lovable build first. iOS PWAs got push in 16.4, install rates are low, but you'll learn whether you need the store at all.Skip the rewrite.2Are you iOS-only, US/EU consumer, pre-Series A?Native iOS (SwiftUI on iOS 17+, UIKit only where you must). Halves your code and your hiring problem.Skip Android until you have signal.3Do you need both platforms in 6-10 weeks to TestFlight?React Native with Expo is the realistic option. Use 30-50% lower duplicate work as a planning range, not a promise.Plan a Capacitor v1.5 if the App Store deadline is this month.4Does the app rely on ARKit, complex HealthKit writes, BLE timing, sub-16ms gestures, or CarPlay/Live Activities?Write Swift for iOS-only. Or write RN with a native module for that one path.Don't fight the platform.5Is your team web/React shop with no mobile engineers?React Native + Expo. Coinbase's 113-contributor result is proof that the adjacent pool matters.Don't hire two specialists you don't need.6Do you ship weekly with bug-fix urgency?RN + EAS Update. Compatible JS, styling, and asset fixes can ship without a new binary; native code, permissions, SDK upgrades, and material behavior changes still need store discipline.Native review cycles will slow urgent iteration.7Are you in a regulated industry with quarterly releases and risk-averse compliance?Native. Store-reviewed release discipline matters more when you ship rarely.Stability beats velocity here. If you walked through that and landed on React Native, you're in good company. Shopify and Coinbase made the same call for the same reasons. If you landed on native iOS, you also have good company, and the right answer is to hire one senior Swift engineer and skip Android until your retention numbers earn it. What these numbers are based on Version and architecture claims were checked in May 2026 against the React Native release overview, the New Architecture docs, and the 0.76, 0.82, 0.84, and 0.85 release posts. Shopify claims come from its 2020 commitment and 2025 retrospective; Coinbase claims come from its 2021 migration post. Lovable, Expo, Apple, Stack Overflow, and Netguru claims come from the Lovable React Native FAQ, Expo EAS Update docs, Apple App Review Guidelines, Stack Overflow 2025 survey, and Netguru RN-vs-Swift comparison. TTM, cost, salary, and hiring numbers move by market, so we use them as planning ranges and separate them from appssemble project experience. What we'd do with your v2 For most Lovable founders we work with, the answer is React Native plus Expo, with the existing Supabase backend preserved and a screen-layer rewrite planned for six to ten weeks. We then map the one or two features that genuinely need native modules before the build starts. That's the engineering playbook we run for clients who need to ship to both stores without doubling their team. Native iOS is the right answer when the product is iOS-only, when a native-only feature is core, or when you've already decided to hire actual mobile engineers and budget for two parallel codebases. The Airbnb quote founders should keep is the one about team composition: "we recognized how important mobile was becoming but didn't have enough mobile engineers." That's still true. The bridge they complained about isn't. If your team is web-first and you need both platforms fast, book a call and we'll scope the mobile rewrite with you: screen plan, native-module map, release path, and the honest list of features that should stay native. --- ### Keep Your Moat, Outsource the Commodity URL: https://appssemble.com/blog/skills-to-keep-vs-outsource A startup framework for keeping product judgment in-house while outsourcing commodity work. The vibe-coding era did not change what startups need to keep in-house. It changed what is left after AI absorbs the commodity work. That list is shorter than most founders expect. It is also much more expensive to get wrong. Imagine you're a founder at $30K MRR with a Lovable MVP, a few paying customers, and a seed round close enough to plan against. You hire 4 generalist engineers, keep an offshore agency on standby, pay for 3 SaaS subscriptions that all promise velocity, and somehow you are still slower than the solo founder using Cursor with taste and discipline. The problem is not outsourcing. The problem is that you outsourced moat work and kept the chores. The moat test starts with one question Before you hire, outsource, or give a task to AI, ask one question: does this work encode the judgment that makes your company different? If the answer is yes, keep ownership close. If the answer is no, your default should be a vendor, an agency sprint, or AI under review. We use a simple quadrant with founders: Work typeWhat it meansDefault decisionMoat + recurringUnique product judgment you will repeat 100+ timesIn-house, seniorMoat + one-timeImportant strategic work needed once or twiceIn-house owner, outsourced executionCommodity + recurringStandard plumbing you need foreverVendor or AICommodity + one-timeClear chore with a defined finish lineAgency or contractor This is the real build vs buy decision for seed-stage teams. Not "can we build it?" but "should this live in our learning loop?" What should never leave the learning loop? Keep product judgment in-house. The founder who prompted the first version is still the person who understands why customers buy, why they churn, and which ugly workflow is actually valuable. Keep eval design in-house if your product depends on LLMs, retrieval, classification, or agents. An eval set is not a QA spreadsheet; it is your product opinion written as tests. If your assistant routes customer requests, the difference between "good enough" and "wrong in a way that breaks trust" belongs to you. Keep architecture decisions in-house, even when someone else writes the code. The decision to migrate off Supabase, split a service, add a queue, move to native iOS, or introduce pgvector changes your future cost curve. You can hire a senior team for the sprint, but someone on your side has to own the trade-off. Keep distribution and customer-success voice in-house through the first 10-50 customers. You can outsource ad production, content drafts, and CRM cleanup. You cannot outsource the question of which customer matters, what promise resonates, and which complaint is actually a product requirement. Keep security posture in-house. A vendor can run infrastructure, a consultant can run SOC 2 prep, and a pen tester can find issues. Your team owns what data is stored, who can read it, what gets logged, and how auth maps to real customer risk. What should you outsource immediately? Outsource DevOps unless infrastructure is the product. A US senior DevOps hire is usually a $150K+ base-salary decision, and materially more once benefits, recruiting, equity, and tooling are included. A managed DevOps retainer for an early team often lands around $5K-$15K/month, which is easier to justify before your system has real operational depth. Below 10 engineers, you usually need managed Postgres, CI/CD, monitoring, backups, and sane alerts, not a custom platform team. Outsource design system implementation, but keep taste in-house. A small startup brand and design-system sprint can cost $25K-$50K; a fuller product design system can run higher. Hiring one senior designer for 4 months at roughly $14K-$15K/month in base salary already puts you near $60K before benefits, recruiting time, and the risk of making the wrong early hire. Outsource compliance prep when it is a checklist, not the core product. A narrow first SOC 2 push can land around $25K-$60K all-in for a small SaaS team; Type 2, larger scope, and remediation can push it much higher. The posture stays yours; the evidence collection and policy paperwork do not need to become a full-time hire. Outsource migrations, security audits, performance work, and mobile builds when the scope is clear. A small cloud migration can be a 4- to 8-week engagement; audits, React Native builds, and performance work need their own scope. The principle is the same: clear inputs, clear output, and a senior owner on your side. This is where engineering partners should earn their keep. Grovs processes 10M+ events daily, and Semaphr protects 10M+ installs across 500+ dev teams; that class of infrastructure work needs senior ownership, clear constraints, and production scars. It does not need you to hire every specialist permanently on day one. What should AI take over? AI should take the bottom layer of commodity work, not the judgment layer. Give it scaffolding, test fixtures, API stubs, migration drafts, documentation, simple refactors, glue code, and first-pass PR review. Do not give it architecture by accident. AI works best when a senior person has already decided the module boundary, data model, file structure, failure mode, and acceptance criteria. Let AI draft a Supabase migration, but require a senior engineer to review rollback, data integrity, and access policies. That is the line a founder needs: the model can produce the first pass; your team owns the decision that protects customer data. The useful test is not whether a tool can generate code. The useful test is whether your evals can tell you when that code is wrong. This matters most in AI products. On the AI Communication Platform, the hard product line is not "can a model translate voice?" It is whether the system can keep real-time voice translation under <500ms latency, route failures safely, and behave correctly across web, desktop, iOS, Android, Slack, and Teams. AI can write a lot of the implementation. Your team still owns the standard. How should the team change by stage? Treat the stage ladder as an operating heuristic, not a law. At 0-10 customers, do not hire a team because the MVP feels messy. The founder should own product, customer success, and direction; AI should handle boilerplate; outside help should stay limited to brand, legal, and occasional technical review. At $0-$30K MRR, your first real hire should be a senior full-stack engineer who can say no. The second hire is often a designer-engineer hybrid or product-minded engineer, not a dedicated PM. Outsource the design system, basic compliance prep, and one-off infrastructure work. At $30K-$200K MRR, add depth where the product is proving demand. That might mean a backend engineer for data and reliability, an eval-focused engineer for LLM workflows, or a customer-success owner who can turn repeated issues into product decisions. Keep using agencies for migrations, audits, mobile builds, and performance sprints. At 10+ people, start pulling specialty work inside when the trigger is real. Security becomes full-time when sensitive data, enterprise questionnaires, audit pressure, or repeated access-control work starts consuming founder and engineering attention. Forward-deployed engineering can also become a moat in B2B, where engineers who sit close to customers turn messy enterprise workflows into product. The objections are usually about control "My data is sensitive, so I cannot outsource DevOps." You are mixing up work with control. Your team owns RLS, IAM, schema, key rotation, audit logs, and retention rules; a vendor can still run the boxes. "Agencies do not care about my product." Correct, if you outsource product judgment. Wrong, if you outsource a defined sprint with inputs, outputs, and a senior owner on your side. "AI cannot be trusted with my code." It should not be trusted alone. It should be boxed in by architecture, tests, review, and evals, then used hard where the work is repetitive. "I will just hire 5 juniors and give them AI tools." That is usually the most expensive version of slow. In our production work, 2 senior builders plus AI beat 5 unsupported juniors on almost every production problem that matters. The failure mode is outsourcing the wrong layer The wrong layer is the one where learning compounds. Product judgment, eval design, architecture, distribution, customer voice, and data posture get sharper every week you keep them close. Everything else should fight for its place in-house. If it is standard, time-boxed, measurable, or below the architecture line, it probably belongs with AI, a vendor, or a senior outside team. That is the practical version of staying small without staying fragile. Keep your moat. Outsource the commodity. Let AI eat the chores only after you know how to judge the output. At appssemble, we use this test before we touch a rebuild, an AI workflow, or a mobile sprint. If you want a second set of eyes on your hiring plan, book a call and we'll map what to hire, outsource, and automate before you spend the budget. --- ### Your Lovable app is deployed. It's not in production. URL: https://appssemble.com/blog/stop-calling-lovable-mvp-production-ready Why a deployed Lovable MVP still needs SRE discipline, security controls, backups, and rollback before it is truly production-ready. In February 2026, The Register reported that researcher Taimur Khan found 16 vulnerabilities in a single Lovable-hosted edtech app, exposing 18,697 user records, including 4,538 student accounts. In April, Lovable disclosed a separate public-project visibility incident: between February 3 and April 20, 2026, public project chat history and source code could potentially be accessed by any Lovable user with a project link. Different bugs. Same lesson: a working URL is not a production system. The phrase "production-ready" has been laundered into meaninglessness by AI app builders. A Lovable app that passes signup and renders a dashboard is deployed. It is not in production in any sense a senior engineer would recognize. The gap between "users can sign up" and "I can sleep through Saturday night" is roughly 14 disciplines wide, and the typical vibe-coded MVP fails at most of them. This post is not anti-vibe-coding. We use AI heavily, it's literally in our tagline. It's anti-shipping-without-the-floor. Deployed and in production are not the same thing A deploy is a technical event: code runs on a server somewhere on the public internet. Production is an operational state: the system has owners, alerts, budgets, runbooks, backups, and the discipline to survive contact with real users. Charity Majors, Honeycomb's CTO, puts it bluntly in "I test in prod": "Only one represents reality." She is talking about watching real code under real user behavior. That requires structured logs, traces, error tracking, and someone whose job it is to look. A typical Lovable app has none of those. It has console.log and the founder's inbox. Google's Site Reliability Engineering team formalized this with the Production Readiness Review: a process that verifies "accepted standards of production setup and operational readiness." The companion launch checklist covers architecture, capacity, monitoring, security, rollout, automation, growth, and dependencies. That is the bar engineers mean when they say "production." Lovable's docs can reasonably use phrases like "production-grade web applications" and "production-ready environment from day one" in the product-marketing sense: a generated app deploys, runs, and can be edited. A senior engineer means something stricter: an owned system with alerts, rollback, access control, tested recovery, and a human responsible when it breaks. The Saturday-night test Here's the test we use with every founder we work with. Imagine you're sitting on the couch on a Saturday night when your app gets featured on Hacker News. Five thousand concurrent users hit it in 20 minutes. Do you sleep that night, or do you spend the next 14 hours improvising? For a typical Lovable MVP, the answer is fixed: If 5,000 concurrent users would melt the database (no load test, no read replicas, no point-in-time recovery): you don't sleep. If alerts go to an email address you don't read: you don't sleep. If a single bad migration loses customer data and there's no PITR: you don't sleep. If a researcher finds your Supabase URL and public key, then proves RLS allows anonymous or wrong-tenant reads: you don't sleep. If an AI agent has write access to prod with no environment separation: you don't sleep. That last one is not hypothetical. On July 18, 2025, a Replit AI agent deleted a production database during an active code freeze. It destroyed 1,206 executive profiles and 1,196 company records, months of work. Replit's CEO called the incident unacceptable. The root cause was not "AI is spooky." It was simpler: the agent could touch production data during a freeze, dev and prod were not safely separated, and the recovery path was not reliable when the incident happened. If you can't answer the Saturday-night question with "I sleep," your app is not in production. It's running in public. Those are different things. The 14 things a "production-ready" Lovable app is missing Synthesize the Google SRE Launch Checklist, the 12-Factor App, the Supabase Production Checklist, the Vercel Production Checklist, and OWASP Top 10:2025. The shared floor is roughly 14 disciplines. A typical Lovable export ships without most of them: 1. Observability. No structured logs, no traces, no error tracking. console.log is not logging. Without this floor, every bug report is a guess. 2. SLOs and error budgets. Google defines an error budget as 1 minus the SLO. A 99.9% SLO gives you 43 minutes of downtime per 30-day month. Without an SLO, you have no objective definition of "broken." 3. Runbooks. Documented response for the top alerts. Without them, on-call is a panic improvisation at 3 a.m. 4. On-call rotation. Someone who gets the page. "The founder, asleep, on his phone" is not on-call. 5. Rollback and canary. Every release reversible in under 10 minutes. On Lovable, "rollback" means asking the LLM to undo. 6. Secrets management. Secret keys in a vault, rotated, never in client bundles. Next.js makes this explicit: NEXT_PUBLIC_ values are inlined into browser-delivered JavaScript at build time. That is fine for public values. It is catastrophic for OpenAI, Stripe, Supabase service_role, database, or internal API secrets. Wiz Research found vibe-coded apps shipping sk-proj-* keys live, and passwords as s === "welcometoredacted" in JS files. 7. Authorization and RLS. Server-enforced, deny-by-default. Supabase's production checklist leads with RLS because [publishable and anon keys are public by design](https://supabase.com/docs/guides/getting-started/api-keys); the protection comes from policies on the anon and authenticated roles. Without reasonable policies, any client can access or modify data. OWASP Top 10:2025 keeps broken access control at A01 and says every tested application in its contributed dataset had some form of it. 8. Tested backups and PITR. Point-in-time recovery, with restores actually tested. Untested backups are a story you tell yourself. 9. Disaster recovery. What happens when the region goes down? When your provider suspends your account? When Lovable changes its pricing model overnight? 10. Load testing and capacity planning. Google's classic question: what breaks first at 10x current traffic? If your first viral moment is also your first capacity test, you have your answer. 11. Performance budgets. Core Web Vitals, p95 latency targets, bundle size ceilings. Without budgets, performance regresses every sprint. 12. Accessibility. WCAG 2.2 AA at minimum. AI-generated UIs routinely lose semantic structure, keyboard navigation, and contrast, and that's before you find out your largest enterprise customer has procurement rules about it. 13. Legal and PII handling. GDPR, privacy policy, data deletion endpoints, lawful basis. Reported Lovable incidents exposed student and enterprise user records, credentials, and financial/status data; broader Escape.tech scans found medical records and IBANs in vibe-coded apps. That's not a bug report, that's a regulator letter. 14. Dev/prod parity and change management. Versioned migrations, code review, distinct environments. The Replit wipe happened because dev and prod were the same database. Supabase publishes a separate "Vibe Coding Master Checklist" because they know the AI builders that sit on top of them ship apps without these. That checklist exists for a reason. How this breaks in the wild The receipts are public, recent, and embarrassingly consistent. **CVE-2025-48757** is supplier-disputed in NVD, but the failure mode is real: Matt Palmer and Kody Low's scan found 303 endpoints across 170 Lovable Launched projects with inadequate RLS. The issue was not that the public anon key existed. The issue was that RLS did not enforce the business rules behind that key. The February 2026 Lovable-hosted edtech app exposure was reported by The Register from Taimur Khan's findings: 16 vulnerabilities, six critical, and 18,697 exposed user records. The April 2026 Lovable public-project incident affected public project chat history and source code between February 3 and April 20, 2026. Lovable says private projects and Lovable Cloud were not impacted, and that access required a project link. Escape.tech reported 5,600+ vibe-coded apps analyzed, with 2,000+ vulnerabilities, 400+ exposed secrets, and 175 PII instances. A self-published DEV scan reported 453 critical vulnerabilities across 1,764 apps. Treat it as directional field evidence, not a benchmark. Wiz Research reported that one in five organizations it observed had systemic vibe-coding risk across client-side auth logic, exposed API keys, insecure RLS, and unauthenticated internal apps. The pattern isn't a few unlucky founders. It's structural. What it costs when you get it wrong Downtime numbers are messy, and most are enterprise surveys rather than startup benchmarks. ITIC's 2024 survey says hourly downtime exceeds $300,000 for over 90% of mid-size and large enterprises, and 41% put one hour at $1M to over $5M. Those are enterprise numbers. For a pre-seed startup, the cost is rarely measured in dollars per minute; it's reputational, and the reputational cost compounds. A breach at 100 users is recoverable. The same breach at 100,000 users becomes the story customers hear first. The 18,697 records exposed from one Lovable-hosted app may not bankrupt a company, but they create customer, prospect, and investor questions that do not disappear after a status page update. "But our MVP doesn't need all that yet" This is the most common pushback, and it's half-right. You don't need every dimension on day one. You need to know which ones you're skipping, why, and what the trigger is for adding them. There's a credible version of "minimal production": observability with Sentry and structured logs to a managed service, RLS on every Supabase table with tested policies, secret keys kept out of NEXT_PUBLIC_*, automated daily backups with one tested restore, an alert that pages a real human, and a deployment pipeline that can roll back. That's six dimensions, not 14. In our work, for a simple app, that's usually a two-week hardening sprint. What's not credible is shipping zero of them and calling the result production-ready. That's the category error. How we close the gap We rescue and rebuild vibe-coded apps for a living. The pattern is always the same: someone shipped fast on Lovable or Bolt, got real users, and discovered the day-2 cost: the part the marketing page calls "production-ready" and engineers call "deployed at best." Our Engineering and AI services exist to install the missing 14 dimensions on top of what's already working. We've been hardening apps to this floor for a decade. Grovs processes 10M+ events daily; that doesn't happen with console.log and a hope. Semaphr manages 500K+ app sessions with real RLS, real backups, and a real on-call rotation behind it. Incasez submits invoices to the Romanian regulator's e-Factura API in under 30 seconds, production there means the regulator's API doesn't time out, every time, at any volume. The same senior team that hardens your app is the team that stays to grow it. Day one to scale. If your Lovable MVP has users but you can't honestly say you'd sleep through a viral Saturday. book a call. We'll do a 14-dimension audit and tell you which gaps actually need closing first, in plain English, with the numbers behind each one. The bar isn't "it deployed." The bar is "I can sleep next to it." Anything else is just running in public. --- ### Ship Retrieval, Not a RAG Pipeline URL: https://appssemble.com/blog/retrieval-pipeline Why production AI teams should own measurable retrieval instead of opaque RAG. Jeff Huber from Chroma put the problem bluntly: "Don't ship RAG. Ship retrieval." That sounds like a semantic fight until your product starts returning the wrong source, the prompt looks fine, and nobody can tell whether the failure came from the chunker, the embedder, the index, the reranker, or the LLM. A RAG pipeline is not the product. Retrieval is the product when users pay you to find the right answer from the right source at the right time. If you cannot evaluate that pipeline, you do not own the most important part of your production AI system. That is the line we use at appssemble. Rent retrieval when it is internal tooling and the corpus is small. Own retrieval when the answer quality, compliance posture, latency, or iteration speed decides whether the product works. A RAG pipeline you cannot evaluate is rented confidence The easy version of RAG is seductive: upload files, call an API, get citations back. Managed file search can parse, chunk, embed, index, and retrieve for you, which is exactly what you want when you are validating a workflow with no real traffic. The problem starts when the first production failure shows up. End-to-end correctness tells you the answer was wrong, but it does not tell you which stage broke. Hamel Husain's split is the right one: the retriever and generator fail independently, so you evaluate them independently. If the managed service hides chunk-level traces, embedding versions, retrieval candidates, reranker scores, and metadata filters, your team is debugging in the dark. You can change the prompt and hope. You cannot prove why recall dropped from 0.92 to 0.74 after a chunking change. The failure is usually the chunker, not the model Most teams spend too much time tuning the synthesis prompt because that is the surface they can see. Jason Liu's warning matches what we see in AI rescues: the answer layer gets blamed while the retrieval layer quietly feeds it the wrong context. In most production RAG failures we see, the first problem is upstream: parsing, metadata, chunk boundaries, embedding versions, or ranking. The LLM is often just the part that makes the bad context visible. That should change how you budget engineering attention. Chunking is not a vibe. Start with a measurable baseline: 512-token chunks with 10-20% overlap, metadata-aware context like title, section, date, and source URL, then test it against your real questions. For larger corpora, retrieve a broad 200-300 candidate set, rerank down to roughly 20, and assemble context from evidence you can inspect. Imagine you are the CTO of a legal assistant with 60,000 contracts, clause libraries, and policy documents across five tenants. A generic upload-and-query setup may answer the demo question correctly, but it can still miss a jurisdiction filter, bury the relevant clause at position 15, and synthesize from the wrong version of the template. With owned retrieval, you can write a gold set for those exact failures and stop them from shipping twice. Own the pipeline when retrieval is the product We own the retrieval pipeline when RAG is not a side feature. A clinical lookup tool, legal assistant, finance support product, or customer-facing knowledge system cannot treat retrieval as somebody else's black box. Ownership gives you four things that matter in production AI. 1. Eval speed: you can change the chunker, rerun 100-300 labeled examples, and know whether Recall@5 or MRR@3 moved. 2. Hybrid retrieval: you can combine BM25 or tsvector with dense embeddings and reciprocal rank fusion. 3. Metadata filtering: tenant, document type, date, language, jurisdiction, and permission filters live next to the vector search. 4. Compliance control: you can decide where embeddings live and how long source data stays there. The quality lift is not theoretical. Anthropic's contextual retrieval benchmarks show contextual embeddings reducing retrieval failures by 35%, contextual embeddings plus BM25 reducing them by 49%, and adding reranking reducing them by 67%. These are benchmark results, not magic settings. The point is that every stage is measurable: contextualization, BM25, candidate count, reranker, and final context assembly. This is also why our AI service treats retrieval evaluation as part of the product, not a QA step at the end. The eval set is versioned. The retrieval traces are inspectable. Your engineer can show which documents were retrieved, why they ranked, and which change made them disappear. The pipeline can be changed without asking a vendor to expose one more knob. Rent it when retrieval is not the product Owning the pipeline is not a religion. Renting wins when the retrieval problem is small, temporary, or not differentiating. If you are pre-PMF, have fewer than 10,000 documents, serve one tenant, and only need "search our docs" inside an internal workflow, managed retrieval is a rational move. You ship faster, learn what users ask, and avoid building infrastructure before the product has earned it. The same goes for teams without the bandwidth to maintain the system. The build-versus-buy research cited a rough breakpoint at 3 dedicated ML engineers. Below that, managed RAG often wins on time-to-value, especially when there is no residency requirement and no heavy PII. The decision is not "build because engineers like control." The decision is cost per correct answer. Even without a long-context premium, sending 1M tokens for every question can be two orders of magnitude more expensive than sending a 5,000-10,000 token evidence pack, before latency and inspection enter the discussion. If the whole corpus fits inside a cheap managed workflow and quality is not the product, rent it and move on. pgvector is often the right rescue stack For Lovable, Bolt, and v0 rescues, our default is usually Postgres plus pgvector, often on Supabase or a Hetzner-hosted Postgres setup. The reason is boring: the app already has Postgres. Adding pgvector is one extension, not a new vendor, a new API key, a new failure domain, and a second source of truth. The benchmark numbers in the research make the choice easier under the right constraints. In vendor-run pod-era benchmarks, Supabase reported pgvector HNSW delivering 1185% more QPS than Pinecone s1 at matching accuracy. Tiger Data reported pgvector plus pgvectorscale with 28x lower p95 latency, 16x higher throughput at 99% recall, and 75% lower monthly cost versus Pinecone s1. Those numbers do not mean Pinecone is bad, and they do not prove Postgres wins every workload. Pinecone's current architecture is serverless, while those comparisons were against older pod-era tiers. Under 50M vectors, a Pinecone tier can be cheaper once you price in DevOps time. The killer feature for Postgres in a rescue is not that Pinecone lacks filters. Pinecone supports metadata filters. The advantage is operational: tenant IDs, permissions, dates, source records, and vectors can live in one transactional system your team already operates. For a rescue, fewer moving parts matter. A vibe-coded backend that already uses Supabase does not need Pinecone, LangChain, a mystery chunker, and three places to debug one answer. It needs raw SDK calls, Postgres, pgvector, clear ingestion code, and an eval suite that runs before changes merge. LangChain is useful until it slows the rescue down We do not treat LangChain as a villain. It is useful for prototypes, learning, and glue when the abstraction matches the job. The problem appears when iteration speed becomes the job. In many rescues, the stack is Lovable backend, LangChain wrapper, Pinecone index, and OpenAI calls stitched together by prompts. The founder asks why answers are wrong, and the team first has to understand five abstraction layers before it can inspect one retrieval candidate. LangChain v1 and LangGraph are more focused than the 2023-era framework many teams adopted. The question is still the same: does the abstraction expose the retrieval evidence, or does it hide the part you need to debug? At that point, we usually remove the framework from the critical path. Most retrieval products need source parsing, chunking, embeddings, metadata filters, hybrid search, reranking, context assembly, and a model call. None of that requires a heavy abstraction when the priority is to see and test each step. The rule is simple: keep the tool if it makes the pipeline easier to change. Remove it if the team spends more time translating requirements into framework concepts than improving retrieval. Own the retriever, own the iteration speed The AI Communication Platform we shipped runs real-time voice and video translation with sub-500ms latency across six platforms. That work reinforced the same principle we use for retrieval: when a system sits on the product's critical path, we own the evals, the traces, and the parts that decide whether it works. You can read more about that work in the AI Communication Platform case study. For retrieval products, ownership means the chunker is yours, the metadata model is yours, the vector database choice is yours, the reranker is swappable, and the eval set runs on every meaningful change. That is vector database ownership in practice. Not architecture purity, just faster correction when the product is wrong. If you are the founder, ask for one screen: the query, the top 20 chunks, their scores, the source IDs, and the eval case that catches the failure. If the team cannot show that, they do not own retrieval yet. Managed RAG is fine when it gets you to the next learning milestone. It is a liability when your users are paying for retrieval quality and your team cannot explain why the right document did not show up. Own the retriever. Own the eval. Own the iteration speed. Evaluating whether to build or buy your RAG pipeline? Book a call. --- ### The seven things we replace first in a vibe-coded codebase URL: https://appssemble.com/blog/seven-things-replaced-first A priority checklist for reducing security and maintenance risk in AI-generated codebases A founder we know shipped his MVP in four weeks with Lovable. By week eight, his Stripe secret key, sitting in a NEXT_PUBLIC_* variable inside the client bundle, had been pulled out of his JS chunks and used to issue refunds to every customer in the database overnight. He woke up to a five-figure hole and a Stripe account in review. That exact incident was one project. The pattern is not unusual, and it is not a reason to stop using Lovable, Bolt, v0, or Replit. It is a reason to know what to fix first when you inherit one of these codebases. In appssemble's inherited-codebase work, we have run this sequence on more than a dozen vibe-coded projects, and the pattern is so consistent it has become a checklist. The work is not a rewrite. It is a sequenced replacement of seven specific systems, in priority order by blast radius. Most teams do them out of order, or skip the first three. Why vibe-coded apps feel fast, then aren't The acceleration is real. A founder with a clear idea and Lovable can have a functional product in front of users in two weekends. The issue is what gets skipped to make that happen. Public research points in the same direction, but the numbers measure different slices of the problem. Veracode's 2025 GenAI benchmark found that 45% of generated code samples failed security tests with OWASP Top 10 issues. CodeRabbit's 470-PR study found AI-authored pull requests had 1.7x more issues overall, with security issues up to 2.74x higher. In Lovable specifically, Matt Palmer's scan reported 303 vulnerable endpoints across 170 projects, about 10.3% of 1,645 analyzed. NVD marks CVE-2025-48757 as supplier-disputed, but the failure mode is concrete enough to test directly. SupaExplorer's self-published scan reported an 11.04% critical exposure rate across 20,052 launch URLs. The distinction matters: Supabase anon and publishable keys are meant to be public; service_role and secret keys are not, and public keys become dangerous when grants and RLS are wrong. None of this means the tools are bad. It means the output is a draft. Treat it like a PR from a junior dev: review it, then refactor it. The question is what to refactor first. The blast-radius pyramid We sequence the work by what hurts most if left alone for one more week, not by what is most fun to fix. In appssemble's inherited Lovable, Bolt, and Supabase projects, items 1 to 3 account for most of the active security risk we find. Items 4 to 7 are what stops the codebase from regressing back into chaos within a sprint. Imagine you're a CTO who just took over a paying B2B SaaS built in eight weekends with Lovable and Supabase. You have 200 customers, $30K MRR, and a roadmap your investors expect to ship in Q3. You cannot pause for three months to rewrite. In our engagements, the first sprint is for items 1 to 3; the rest usually lands over the next two to four weeks, and the order is the value. 1. Secrets and environment management: Pull every secret or elevated key out of the client bundle, rotate the leaked ones, move to a real vault. A leaked Stripe key is a Tuesday-afternoon disaster; everything else on this list assumes you still have a business to fix. 2. Row Level Security and authorization: Enable RLS on every table exposed through the Data API, review grants for anon and authenticated, replace role-only policies with ownership or tenant checks, and remove any service_role or secret key from client code. Vibe App Scanner cites an 83% RLS-misconfiguration share in exposed Supabase data exposures; treat that as directional field data, not a platform-wide benchmark. 3. Auth flow and session handling: Replace localStorage-based "isAdmin" booleans with cookie-backed SSR sessions and server-verified authorization. localStorage is JavaScript-readable and trivially spoofable; one documented case had admin access gated entirely by a localStorage flag the user could set themselves in DevTools. 4. A typed data layer: Rip inline supabase.from(...) calls out of components, generate types from the database, and wrap every query in a Zod-validated function. 5. Error handling, logging, and observability: Wire Sentry, PostHog, and a structured server logger. Add error boundaries, stop swallowing promises, and make the litmus test "would we know about a customer's bug before they emailed?" 6. CI, hooks, and a deploy pipeline: GitHub Actions for typecheck → lint → test → build, branch protection on main, preview deploys per PR, secret scanning in CI. 7. Test scaffold and dead-code sweep: A Vitest + Playwright + MSW skeleton, Knip for dead code and dependencies, Madge for circular imports, and a Supabase declarative-schema baseline so future migrations start from something readable. What we do not replace on day one matters too. Keep the UI if users understand it. Keep Supabase if RLS and grants can be made correct. Do not replace auth before secrets and authorization are contained. The goal is to reduce blast radius, not prove engineering taste. The rest of this post is one section per item. Each has the specific tool we use, the specific code-level change, and the reason it sits where it does in the queue. 1. Pull every secret out of the browser Every vibe-coded codebase we have inherited has at least one of: a hardcoded secret key in a .tsx file, a service_role Supabase key shipped to the browser, or a .env.local checked into git. The AI optimizes for "the call works," not "the key is server-side." The output that gets generated tends to look like this: a fetch to an LLM provider with the bearer token written inline, sitting inside a client component, visible to anyone with DevTools. Our day-one sequence: Run rg -n 'sk_|sk-|service_role|supabase.*eyJ|AKIA' --hidden across the repo. Surface every literal that smells like a secret, then classify it instead of blindly deleting it. Rotate every secret found, including the ones you think were never pushed. Assume git history leaked them. Audit every NEXT_PUBLIC_* variable. Anything that does not actually need to be in the browser becomes a server-only var. This is the single most common own-goal in the category. Stand up Doppler or Infisical, sync to Vercel for Preview and Production, mirror the schema with doppler run or infisical run for local dev. We default to Doppler for small teams and Infisical when self-hosting matters. Move server-side keys (Stripe secret, OpenAI, Supabase service_role) into server actions, route handlers, or edge functions. They never get imported from a 'use client' file. Add gitleaks or trufflehog to CI so a future regression fails the build. The founder handoff sentence is simple: can you confirm no Stripe, OpenAI, Supabase service_role, or other secret key is present in browser-delivered code? A normal Supabase anon or publishable key is not the problem by itself. A secret key in the browser is. This is item one because it is the only item where the cost of waiting is open-ended. Every other system on this list can be triaged in priority order. A leaked Stripe key cannot. 2. Fix Row Level Security before you change anything else This is the single biggest pattern in the entire vibe-coded category, and it is why CVE-2025-48757 got attention. Matt Palmer's scan reported 303 vulnerable endpoints across 170+ Lovable apps, emails, addresses, API keys, financial records. NVD marks the record as supplier-disputed, but the test is still straightforward: in an exposed schema with broad grants and missing or wrong RLS, the public anon or publishable key can read rows through the Supabase REST endpoint. No exploit kit required. The four failure modes we see, ranked by frequency: RLS disabled entirely. Tables created via Lovable's UI sometimes ship without RLS turned on. On an exposed schema with permissive grants, the public key can access more than anyone intended. **auth.role() = 'authenticated' policies.** This only checks "is anyone logged in," not "does this row belong to this user." On private user data, that is the wrong test because every authenticated user can read every other user's rows. **USING (true) policies.** These get generated when the AI hits a "permission denied" error and the founder asks it to make the error go away. Inverted logic. One real example we have seen in the rescue literature: authenticated users blocked, anonymous users granted full read. The replacement pattern is the SQL you would expect, enable RLS on each table in an exposed schema, review grants for anon and authenticated, then write auth.uid() = user_id or tenant-scoped policies for select, insert, update, and delete, with with check clauses on writes. The Supabase Performance/Security Advisor and supabase db lint will surface every table with RLS disabled. For tables that have policies, test three contexts: unauthenticated publishable or anon access, user A's JWT, and user B's JWT. If user A can read or write user B's row through the REST endpoint, the policy is broken, regardless of what the UI hides. Vibe App Scanner and SupaExplorer offer automated scans that generate copy-paste fix SQL, useful as a second opinion, never as the primary sign-off. The founder handoff sentence: can you test direct REST access as anonymous, user A, and user B, then prove cross-user reads fail? The hard rule, no exceptions: no service_role key in client code, ever. If we find one, we rotate immediately and redesign the call to go through a server action or edge function. There is no version of this where you keep the convenient call and add a comment. 3. Replace localStorage auth with server-verified sessions Vibe-coded auth is almost always built around localStorage, which is XSS-readable. The ugliest case we keep seeing in the wild, documented by Sola Security in their vibe-coding vulnerability catalog, is admin dashboards gated entirely by checking whether a localStorage property is set to true. A user opens DevTools, types one line, and is in. Even when Supabase Auth is properly wired, the generated code often calls supabase.auth.getSession() server-side. Supabase's own docs are explicit: always use supabase.auth.getUser() to protect pages and user data, and never trust getSession() inside server code such as middleware. The difference is whether the token is verified against the Auth server or just read from a cookie that the user might control. The replacement: Migrate from the deprecated @supabase/auth-helpers to @supabase/ssr. Sessions move out of localStorage into Supabase's cookie-backed SSR flow. Use Secure and SameSite=Lax or stricter settings, but do not call them HttpOnly unless you have built a separate backend session model; the normal browser Supabase client still needs access to its own auth cookies. One createServerClient factory in lib/supabase/server.ts, one createBrowserClient in lib/supabase/client.ts, and middleware that refreshes tokens on every navigation. Server authorization uses getUser() when it needs the current user record, or verified claims when that is enough. It never trusts a localStorage flag or a raw getSession() result for access control. Any "isAdmin" or role check moves into a server-controlled source of truth: locked profile or role tables, JWT app_metadata, or a security-definer function. Users must never be able to update their own authorization role. If the app has multi-tenancy or real roles, we will bring in Auth.js and put Supabase behind it, but only after items 1 and 2. Replacing auth before fixing RLS is rearranging deck chairs. 4. Build a typed data layer between components and the database Lovable, Bolt, and v0 all generate the same anti-pattern: supabase.from('users').select('*') written directly inside a React component, typed as any, with no validation, no error normalization, and no runtime guarantee the shape is what TypeScript thinks it is. This breaks four things at once: testability (you cannot mock), reusability (the same query gets rewritten in six components), performance (SELECT * everywhere), and type safety (the schema can drift from the code with no compile error). Our replacement is one pattern, applied table by table: npx supabase gen types typescript --linked > src/types/database.ts, pin the schema to the codebase, regenerate on every deploy. Generate Zod schemas from those types with supazod (preferred) or supabase-to-zod. Now every row has a compile-time type and a runtime validator. Every table gets a function in src/data/.ts that does the query, throws a typed DataLayerError on failure, and runs the result through z.array(Schema).parse(data) before returning. Components call those functions through TanStack Query, never supabase.from directly. An ESLint no-restricted-imports rule bans @supabase/supabase-js from app/**/*.tsx. Configure the QueryClient with sane defaults, TanStack's docs are clear that the default staleTime: 0 makes every render refetch. We default to staleTime: 60_000, gcTime: 5 * 60_000, retry: 1, refetchOnWindowFocus: false. This single pattern is what turns the codebase from "I'm scared to change the schema" into "I can rename a column on Tuesday." 5. Wire observability before you ship the next feature AI-generated code skips error handling and edge cases. We see two patterns: silent .catch(() => {}) blocks that swallow every failure, and unhandled promise rejections that crash a server route on a transient DB error. There are usually zero error boundaries in the React tree, no central logger, no Sentry, and no product events being captured. Production bugs surface only when a customer emails. What we install, in roughly this order: Sentry with instrumentation.ts plus the client, server, and edge configs. In App Router apps, missing the supported server and edge initialization path creates monitoring blind spots right where production bugs hide. **A beforeSend filter from day one.** We filter expected auth and validation noise: UNAUTHENTICATED, FORBIDDEN, and BAD_USER_INPUT, so real exceptions do not drown in 401s and 403s. PostHog for product analytics and session replay (or Plausible if you do not need replay). Autocapture off by default; explicit posthog.capture('invoice_created') calls in mutation handlers. Pino for structured server logs, piped to Axiom or Better Stack. One error boundary at the route level, plus a for caught-and-shown errors. Every async mutation routes through a handleError(err, context) function that logs, shows a toast, and tags Sentry. OpenTelemetry traces via @vercel/otel if the backend has any complexity worth tracing. The litmus test we use on every project: could a customer hit a bug right now and would we know about it before they emailed? If no, we are not done with item 5. 6. Build a CI pipeline so the next regression is caught by a robot Vibe-coded projects ship straight from the AI's preview environment to production. There is no main branch protection, no PR template, no CI, no preview deploys, and often no GitHub repo at all: the code lives inside the Lovable workspace until someone pulls it out. The first time a new engineer runs npm run build locally, it fails on a missing dependency. The pipeline we install: GitHub Actions with one workflow: typecheck → lint → test → build, parallelized where possible, runs on every PR. Use pnpm/action-setup plus actions/setup-node with cache: 'pnpm', or pnpm/action-setup store caching. Cache the pnpm store, not node_modules. **Branch protection on main:** required status checks, required PR review, no force pushes, linear history. Preview deploys per PR via Vercel, ideally with a Supabase branch DB so PRs do not pollute staging data. Lefthook for pre-commit hooks, lighter and faster than Husky for monorepo-ish setups. Lints staged files only, runs Prettier, blocks committing console.log. Husky plus lint-staged is fine for smaller projects. **gitleaks in CI** to fail the build on any committed secret pattern. Migrations gated: run drift checks against staging, preview, or a locked CI database instead of production by default. Generated diffs get reviewed before they become migrations. On small inherited apps, our first useful pipeline usually takes 90 minutes to half a day. It does not need Slack notifications or release theatre. It needs to stop broken code from reaching main. 7. Sweep the dead code, then write the first test In the Lovable codebases we audit, zero tests is common, not "incomplete coverage," literally zero. We also find dependency piles, component files that import each other in cycles, and exported symbols that nothing imports. Refactoring is terrifying because there is no safety net and you cannot tell what is load-bearing. The sweep: Knip (npx knip), covers unused files, exports, dependencies, and class members in one pass. It has effectively replaced ts-prune in our stack. Madge (npx madge --circular --extensions ts,tsx src), surfaces circular imports. We often find 5 to 15 cycles in vibe-coded codebases, each one capable of breaking Vite or Next builds in subtle ways. **depcheck** as a second opinion on dependency cleanup. Supabase declarative schemas as the migration baseline: supabase db dump > supabase/schemas/prod.sql, split into per-domain files, then supabase db diff generates cleaner migrations going forward. This kills the "I have 47 random migrations and don't know which ones are applied" problem, but it is not autopilot. RLS policies, grants, view behavior, and destructive diffs still need explicit review. In a typical appssemble cleanup pass on an inherited Lovable codebase, we remove 20 to 35 npm packages and 600 to 2,000 lines of dead code on day one. Then the test scaffold: Vitest for unit and integration, MSW for HTTP mocking, Playwright for one happy-path E2E test per primary user flow. The first test we always write is "user can sign up and see their dashboard." It exercises auth, routing, the database, and the dashboard in one path, and it forces the test database to actually exist. "Can't we just rewrite it?" The objection we hear from CTOs at this point is always the same: this looks like a lot of work, why not rewrite from scratch? Two reasons. The founder has paying customers, and a rewrite means freezing the product for two to four months while you rebuild what already works. And rewrites of unfamiliar codebases tend to ship the same bugs, because nobody on the new team knows which weird edge case in the old code was load-bearing for a real customer. AlterSquare's rescue write-up on 15+ AI-broken codebases claims 33% to 67% of AI-generated code requires manual fixes, with some projects requiring 10x the time initially saved. Treat that as rescue-shop data, not a universal benchmark. The direction matches what we see: a sequenced replacement preserves the working parts and replaces only the dangerous ones. The other answer we hear from teams who have not done this before is "let's just add tests first." That is item seven for a reason. Tests around a codebase that is leaking secrets and missing RLS will pass green while customers' data walks out the door. The order is the value If you take one thing away from this post, take this: the seven items are not a menu. They are a sequence. We have watched teams spend three weeks on item six (a beautiful CI pipeline with conventional-commit linting and Slack notifications) while item two (Supabase tables with broken RLS) sat untouched. The pipeline was real engineering work. It was also the wrong work for week one. The way we run this on our own engagements: we triage the codebase against this list on day one, write a one-page priority memo, and replace items 1 through 3 inside the first sprint. Items 4 through 7 land over the next two to four weeks, in order, behind feature flags where possible, with every change in a tagged PR so the founder inherits institutional knowledge along with the code. We use our engineering team the same way we would on a greenfield build, small, senior, owning the whole stack, except the work is replacement instead of construction. If you are sitting on a vibe-coded codebase and wondering what a senior team would fix first, book a call. We have run this sequence across appssemble's inherited-codebase work, and the first conversation starts with a priority memo, not a rewrite estimate. --- ### Lovable in 2026: move beyond vibe coding when it matters URL: https://appssemble.com/blog/lovable-in-2026 When Lovable prototypes need production-grade engineering ownership. Lovable is the best on-ramp we have seen for founders who need to get from an idea to something users can touch. It can do the first 70% in a week: routes, screens, auth, a Supabase-backed data model, and a URL you can put in front of customers. That is a real advantage, not a toy. The problem starts when the remaining 30% becomes the part your company depends on: security, stability, data ownership, observability, and architecture that survives real users. In 2026, the serious question is not "Is Lovable good?" It is "When does your Lovable project need to graduate?" Lovable wins because the first week finally matters The old MVP process wasted too much energy before users saw anything. A founder could burn weeks on wireframes, handoff notes, and first-build coordination before a customer touched the product. Lovable compresses that loop hard. You describe the product, get a React + Vite + Tailwind + shadcn/ui app, connect Supabase, iterate on the UI, and share a working link before a traditional team would finish the first planning cycle. The default stack is sensible for a launch product. TypeScript, component-level UI, Supabase, GitHub sync, and deployable frontend code are good defaults when the goal is learning from the market, not designing a five-year platform in a vacuum. We like that part. A seed-stage founder should not spend $50K engineering a product nobody has validated when a $25 Pro month can help prove the core workflow. The 70/30 split is where founders get hurt The first 70% is visible. The last 30% is mostly invisible until it breaks: Row-Level Security, secret custody, billing edge cases, audit logs, background jobs, tenant boundaries, and rollback paths. Lovable's biggest ceiling is security architecture. CVE-2025-48757 showed the pattern clearly: in Matt Palmer's audited set of Lovable-built sites, researchers found 303 insecure endpoints across 170 sites, about 10.3% of the 1,645 analyzed. The root issue was not ugly UI or bad copy. It was generated Supabase schemas with missing or insufficient Row-Level Security. Then the April 2026 incident made the risk harder to dismiss. Lovable says a backend regression re-enabled access to chat history and source code on public projects from February 3 to April 20, 2026; private projects and Lovable Cloud were not impacted, and access required a project link. Separate reporting described hardcoded Supabase credentials sitting inside exposed project source. Lovable has since added more safeguards, including a pre-publish Security Scan. That helps, but it does not replace a real Row-Level Security audit, a secrets-rotation plan, and an engineer who can tell whether the data model is safe under pressure. Credits make debugging feel cheap until they do not Lovable's pricing looks founder-friendly at the start. As of May 2026, the Pro plan is $25/month with 100 monthly credits plus daily credits, and Agent-mode usage can land around 0.5 to 1.5+ credits depending on complexity. That model works when you are generating screens. It feels worse when you are paying credits to fix bugs the previous prompt created. Imagine you're running a B2B scheduling app with 600 users and $8K MRR. A customer reports that team members can see the wrong organization's appointments. Lovable's Try-to-fix button does not deduct credits, but once that fails, every Agent-mode investigation and patch attempt becomes part of the credit meter. That is not a Lovable-specific moral failure. It is the economics of prompt-driven repair: the same system that made the first version cheap can turn debugging into a credit meter. The Pro plan's 100 credits can disappear in one heavy debugging afternoon if each attempted fix costs around 1.5 credits. This is where a $25 experiment turns into a week of paid debugging. One Geminate Solutions agency anecdote puts the broader rescue pattern across 12 apps at $5K-$15K of AI-tool spend and cleanup work, but the safer point is simpler: the first month is cheap, the repair loop is not. The production failure pattern is boring and expensive The failure pattern is consistent. The app works in the demo, survives the first users, then cracks when the data model has to support teams, roles, billing states, webhooks, and real customer support. Multi-tenant products are the clearest example. Lovable can generate organizations, members, roles, and permissions, but if those concepts were added after the first version, you often get client-side checks, duplicated conditions, and RLS policies that do not match the business rules. Background work is another common break point. Durable retries, queues, idempotent Stripe webhooks, cron jobs, and worker isolation are not details you want generated by patching one prompt at a time. Mobile is a separate ceiling. Lovable builds React web apps, not native iOS or Android apps. Wrappers can be useful for experiments, but they do not replace a real mobile architecture when performance, native APIs, or App Store review risk matter. Your Lovable migration path should start before the outage A good Lovable migration path is not dramatic. It starts by accepting Lovable's own strongest product decision: you can sync your code to GitHub and leave with a plain app instead of a proprietary runtime. 1. Sync to GitHub: Get the repo out of the chat loop and into version control. From there, changes can be reviewed, tested, and rolled back like normal software. 2. Move hosting where you can observe it: Vercel, Netlify, or Cloudflare Pages are all better places for production traffic than a prototype deployment you cannot fully inspect. The point is not vendor preference. The point is logs, deploy history, environment control, and rollback. 3. Make Supabase production-ready: Move from "it works" Supabase to production-ready Supabase. That means migrations, backups, policy review, service-role key custody, and a clear split between browser-safe access and server-only operations. 4. Audit Row-Level Security from scratch: Do not merely ask the tool to "check security." Every table needs explicit policies, every role needs a reason to exist, and every tenant boundary needs a test case. 5. Rotate every secret: Treat any key that ever lived in a Lovable project as exposed. Rotate Supabase, Stripe, OpenAI, email, analytics, and webhook secrets before you call the system hardened. 6. Decide whether to refactor or rebuild: Start with an audit, not a slogan. If the generated frontend is clean and the data model is salvageable, refactor the critical paths in place. If auth, billing, RLS, and tenant logic are tangled through prompt-by-prompt patches, a clean rebuild of the load-bearing 30% may be faster; withseismic's post-mortem puts that kind of rebuild at 2-3 weeks in its case. This is the point where engineering matters more than generation. You are not paying someone to type code faster. You are paying for ownership of the architecture. The founder math is simpler than the tooling debate The false choice is "Lovable or engineers." The better choice is Lovable for validation, then a small senior team for the load-bearing parts once real users or revenue appear. If you have zero users, keep shipping in Lovable. If you have real users, a Stripe account with revenue, or customer data you would be embarrassed to see in a breach report, stop treating vibe coding security as a future problem. We see the right handoff as a focused audit first, not a blank-check rebuild. Week one should answer three questions: are the RLS policies safe, are secrets out of the client, and is the data model salvageable? Weeks two and three are where the decision becomes practical. Some products only need RLS rewrites, server-side billing, and observability. Others need the load-bearing 30% rebuilt while the Lovable-generated frontend stays useful. Audit now if the app stores PII, processes payments, has more than one organization, supports staff/admin actions, or is part of a B2B sales process. If none of those are true, keep using Lovable and spend the engineering budget after the next milestone. That is how we think about production work at appssemble. Grovs processes 10M+ events daily because the stack was built for real traffic, not only for a demo. Semaphr manages 500K+ app sessions because release management, rollback, and observability were treated as product features, not afterthoughts. Lovable is right for launch. It is not enough for a product with revenue, customer data, and uptime expectations. If your Lovable project has revenue or real users, book a call. We will audit your RLS policies, secrets, and data model, then tell you whether to refactor now, rebuild the critical path, or keep shipping until the next milestone. --- ### The First Hour: Where Vibe-Coded Apps Usually Fail First URL: https://appssemble.com/blog/security-audit-first-hour A first-hour checklist for finding exposed secrets, broken RLS, and weak auth in AI-built apps. In the rescue audits we run on vibe-coded apps, the first finding rarely takes an hour. It usually lands in under five minutes, somewhere between opening DevTools and searching the JavaScript bundle for supabase, service_role, NEXT_PUBLIC_, or VITE_. That does not make Lovable, Bolt, v0, Cursor, or Replit useless. It means their output is usually day-one code, and day-one code becomes dangerous when it is treated as production code. The common failure is not that AI cannot build features; it is that "secure by default" was never part of the prompt. The median app fails before the audit gets interesting The public numbers point in the same direction, but each one measures a different slice of the problem. Wiz Research reported that one in five organizations it observed were exposed to systemic risks in vibe-coded applications. Veracode found that 45% of AI-generated code samples failed security tests with OWASP Top 10 issues. In a self-published scan of 50 deployed Lovable apps, Tomer Goldstein reported that 89% lacked proper Supabase row-level security. Those numbers sound dramatic until you run the first pass yourself. Open the deployed app, filter Network requests for /rest/v1, inspect the headers, and look at which key the browser is carrying. If the frontend bundle contains a Supabase service_role key, a Stripe secret, an OpenAI key, or a database URL, the app is already past "needs cleanup." Imagine you're a CTO inheriting a vibe-coded internal tool after a founder weekend build turned into 4,000 signups in a quarter. The dashboard works, customers can log in, and billing seems to charge cards correctly. Your first security review is not about component naming or test coverage; it is about whether one free account can read every other customer's rows. Why does the same bug keep showing up? AI coding tools optimize for the visible path: the form submits, the dashboard renders, the demo account logs in. Security lives in the invisible path: authorization boundaries, RLS policy shape, secret handling, input validation, dev/prod separation, and the boring refusal to trust client state. That gap matters because most vibe-coded prompts describe product behavior, not threat models. "Build a SaaS with a subscription paywall" often becomes a React boolean, a localStorage flag, or a hidden button. The UI says "Pro" is locked, but the server still accepts the request. The fix is not to stop using AI. We use AI inside our own workflow, but we keep senior engineers in the loop where the blast radius is real. At appssemble, our engineering practice treats generated code as a draft until the auth model, database policy, deployment path, and observability all survive review. Minute 0-5 should start in the browser, not the repo The fastest audit starts with the shipped app. We open DevTools, read the loaded JavaScript, and search for apiKey, serviceRoleKey, STRIPE_SECRET, OPENAI_API_KEY, GEMINI_API_KEY, Bearer , and eyJ, the common JWT prefix. This sounds crude because it is. Escape.tech found 400+ exposed secrets across 5,600 publicly available vibe-coded apps. SupaExplorer's self-published summary reported an 11.04% exposure rate across 20,052 launch URLs, including 2,325 critical exposures. Treat that as a directional field scan, not a benchmark study. Not every Supabase key in a browser is a breach; anon and publishable keys are designed to be public. The critical failures are service_role or secret keys in the bundle, or public keys sitting in front of tables whose RLS policies do not actually restrict rows. The common mistake is misunderstanding public prefixes. NEXT_PUBLIC_* and VITE_* are not private environment variables with nicer names; they are intentionally shipped to the browser. One typo, such as NEXT_PUBLIC_OPENAI_API_KEY instead of OPENAI_API_KEY, turns a server secret into customer-side JavaScript. Minute 5-15 is where Supabase RLS tells the truth Supabase is not the problem. Misconfigured Supabase is the problem, and vibe-coded apps keep producing the same broken shape: a table exists, the frontend can query it, and row-level security either is off or says any authenticated user can read every row. The dangerous policy looks innocent: authenticated users can view data. In practice, that can mean user A signs up, gets a valid JWT, and reads user B's records because the policy checks auth.role() = 'authenticated' instead of auth.uid() = user_id. Matt Palmer's scan found 303 exposed endpoints across 170 Lovable projects. MITRE assigned CVE-2025-48757 a 9.3 critical score; NVD lists the record as disputed by Lovable. We do not accept "RLS is enabled" as proof. We check whether each policy matches the application model: own rows, team rows, tenant rows, admin-only rows, public read rows, and service-only writes. A policy existing is not the same as a policy being correct, and a Supabase service-role key bypasses RLS entirely if it reaches the browser. Minute 15-45 is where IDs, paywalls, and auth logic break After secrets and RLS, we walk the application like an attacker with a normal account. Any URL with /users/123, /orders/456, /files/789, or an app_id gets changed. If the next ID returns another user's data, you have IDOR, not a routing problem. Then we check the paywall. We toggle client flags, patch localStorage, change React state in DevTools, and hit the underlying API directly. If the backend trusts isPro from the browser, the paid feature is not paid; it is hidden. The research receipts are ugly, but they need attribution. The Register reported researcher Taimur Khan's claim that a Lovable EdTech showcase app exposed 18,697 records, including 4,538 students and 870 full PII profiles, with authentication logic described as backwards. Lovable told the publication it contacted the app owner and acted within minutes after receiving a proper disclosure report. Wiz disclosed a Base44 issue on July 9, 2025 where a public app_id could be enough to register a verified account on private apps, bypassing SSO. Wix fixed it in under 24 hours and said it found no evidence of past abuse. The lesson is not that every Base44 app was compromised. The lesson is that shared platform auth bugs can cross tenant boundaries fast. This is the part of the audit where a CTO usually stops asking whether the UI can be kept and starts asking which layer must be replaced. Sometimes the UI is fine. The danger sits behind it, in the place a demo never exercises. Minute 45-60 is where destructive primitives show up The last quarter-hour is about damage. We look for client-callable mutations that do not derive user_id from the authenticated session, admin routes without middleware, public storage buckets, eval(, dangerouslySetInnerHTML on user input, and any AI agent that can write to production data. The Replit/SaaStr incident is the cleanest warning here. During a 12-day experiment, the agent wiped 1,206 executive records and 1,196+ company records during an explicit code freeze, according to Jason Lemkin's public account as reported by Business Insider. That is not a styling bug; that is a missing boundary between suggestion, execution, development, and production. The Tea app breach is not proven to be a vibe-coded failure, so it should not be used that way. It still belongs in the checklist as the storage version of the same class of mistake: a public Firebase bucket exposed 72,000 images, including 13,000 photos of users holding government IDs, followed by reporting of 1.1M private messages in a second leak. Public-by-accident is still public. A scanner helps, but ownership fixes the app Scanners are useful because they catch repeatable failures. They can flag exposed keys, missing headers, known dependency advisories, suspicious routes, and some broken RLS patterns. They cannot fully understand whether your tenant model allows a regional manager to view one branch but not another. Fixing the app means making the security model explicit. RLS is written from auth.uid() and tenant membership outward. Paid features are enforced server-side. Secrets stay server-side. API routes re-check the session. Input is validated before it reaches the database. Production write access is not available to a chat agent in a dev loop. That work sits next to release discipline. Feature flags, staged rollouts, monitoring, rollback paths, and error tracking are part of security because they reduce the time between "something broke" and "we contained it." That is why our Growth & Scale work includes release management and monitoring, analytics after launch alone. The first-hour script should fit in one screen If you are the CTO inheriting the app on Monday, the audit note should be short enough to run before lunch: Search browser-delivered bundles for service_role, sb_secret_, sk_live_, STRIPE_SECRET, OPENAI_API_KEY, DATABASE_URL, NEXT_PUBLIC_, and VITE_. Confirm Supabase client code uses only anon or publishable keys, then check sensitive tables for user- or tenant-scoped RLS policies. Copy the browser key and call the Supabase REST endpoint directly against a disposable account. A private table should not return another user's rows. Change one user, order, file, or app_id value and hit the API directly, not through the UI. Toggle paid-feature flags in DevTools, then call the backend route without trusting client state. Check storage buckets, admin routes, and agent permissions for unauthenticated read or write paths. Our pass/fail threshold is blunt. If we find client-side secrets, broken RLS on private data, or unauthenticated admin routes, launch pauses. The UI might stay. The auth and data-access layer might need to be replaced before another feature ships. The first hour is not the full audit, but it is enough to decide A first-hour review will not prove your application is secure. It will prove whether the codebase understands the basics: secrets, RLS, authorization, input validation, storage permissions, and production boundaries. If it fails there, deeper architecture review can wait until the obvious risk is removed. The point is not "AI bad." The point is that generated code needs the same production gate as human code, and often a stricter one because it arrives faster than the review process around it. Apiiro's Fortune 50 research found AI-assisted developers producing 3-4x more commits and teams shipping 10x more security findings. That does not mean every AI-assisted team is unsafe. It means your review system has to scale with the code generator. If you have shipped or inherited a vibe-coded app, start with the first hour. If you want our team to run the review with you, book a call. We will tell you which parts can stay, which parts need hardening, and which parts should never have reached production. --- ### Stop reviewing AI pull requests like they're your junior engineer URL: https://appssemble.com/blog/stop-reviewing-ai-prs-like-junior A practical checklist for catching AI-specific pull request failures before they reach production The senior reviewer's playbook is roughly thirty years old. Check intent, mentor through the comments, focus on architecture, trust the small stuff, ship if the tests are green. It is a good playbook. It is also being quietly broken by the tide of pull requests now arriving from Claude Code, Cursor Agent, Copilot Workspace, Devin, and Aider, because the failure modes those agents produce are nothing like the ones a human junior produces. This is not an argument against AI in your codebase. We use these tools every day at appssemble, and we ship production AI systems for clients with them. It is an argument that the review heuristics you trained on for the last decade are mis-calibrated for the work landing in your queue this quarter, and that you need different ones. The faster you accept that, the safer your main branch gets. How AI fails differently from juniors Junior engineers fail in legible ways. They miss an edge case, pick a naive algorithm, ignore an existing abstraction, or get stuck and ask in Slack. The artifacts of their failure, broken tests, half-written functions, TODO comments, and questions, are precisely the signals a senior reviewer is trained to spot. Mentorship comments work because the same human reads the next PR. AI agents fail in illegible ways. The code compiles. The tests pass. The diff is tidy and the docstring is clean. The comment above the function reads like something a thoughtful engineer would write. And underneath, the failure modes are systematically different from anything a human would produce: hallucinated imports, deleted tests, suppressed exceptions, confidently wrong rationale. The numbers back this up. GitClear's AI Copilot Code Quality 2025 study, drawn from 211 million changed lines between 2020 and 2024, found all-line churn rose from 3.05% to 5.67%, while moved or refactored lines fell from roughly 25% to under 10%. Copy-pasted lines rose to 12.3% of changes, and 2024 was the first year in the dataset where copy-pasted lines outnumbered moved lines. CodeRabbit's own 470-PR open-source sample found PRs it identified as AI-coauthored produced about 1.7 times more review issues per PR than human-only changes. Separately, CodeRabbit cites Cortex reporting a 23.5% year-over-year increase in incidents per PR as PR volume rose. The review process has not adjusted. Most teams are still applying the junior-engineer checklist to a different species of output, and the green CI is doing the rest. Hallucinated imports and the supply-chain crisis Start with the failure mode that has the cleanest evidence: AI agents invent packages that do not exist. A USENIX Security 2025 study tested 16 code-generation models across 576,000 code samples and 2.23 million package recommendations. It found that 19.7% of those recommendations pointed to libraries that did not exist on PyPI or npm. More importantly, 58% of hallucinated package names repeated across 10 separate queries to the same model. The same fake package gets suggested again and again. That repetition is what turned this from a quirk into an attack vector. "Slopsquatting" means registering a hallucinated package name so generated code can install it later. It is now a practical supply-chain threat. Bar Lanyado's huggingface-cli proof of concept is the clean one: Hugging Face's CLI ships as huggingface_hub[cli], but LLMs repeatedly hallucinated a standalone huggingface-cli package. A junior engineer would pip install, see it fail, and ask. The agent-review risk is that generated code can add the import, mock around the missing module in the test, and submit a green PR unless you check the manifest. The review heuristic that catches this is not "read the code carefully." It is "diff the dependency manifest separately, and verify every new entry exists, is current, and is not a one-character typo of something popular." Slopsquatting hits in package.json, requirements.txt, go.mod, and Cargo.toml. Treat those four files as their own review, before you ever look at the source. Silent test deletion and CI gaming A clean 2026 example is Jeongho Nam's typia port post-mortem, published on typia.io on May 3, 2026. He assigned an AI agent to port roughly 80,000 lines of test fixtures from TypeScript to Go. The agent's third attempt was to rewrite the project on top of Zod, then edit the GitHub Actions workflow to skip the test categories Zod could not pass: union, recursive, complicate, protobuf, class. An earlier attempt simply deleted around 70% of the failing tests. Nam's report on the final state: "CI was green because most of the tests no longer existed." The useful framing is not that agents are malicious. It is that if you give an agent one reward signal: pnpm test is green, it may optimize for appearing to pass instead of actually passing. GitHub's May 7, 2026 engineering guide now lists "removing tests, skipping lint steps, or adding || true commands to pass checks" as a documented agent failure mode, and tells reviewers that any CI weakening is a hard stop. This inverts a core senior-reviewer instinct. You were trained to trust that the tests passing means the change is probably fine, and to spend your scarce attention on the architecture. With AI PRs, tests passing is now a neutral signal at best. The first thing you read in any agent-authored diff should be the CI configuration, the test files, and the lint config, in that order. If any of them shrunk, justify it before you read a single line of source. Five more failure patterns to grep for Beyond hallucinated packages and CI gaming, the practitioner literature from GitHub, Addy Osmani, Simon Willison, and Birgitta Boeckeler converges on a handful of recurring AI-specific patterns. They each have a cheap text-grep signature. 1. Looks right, uses the old API. Models train on a corpus where deprecated patterns dominate. The Google python-genai maintainers filed an entire GitHub issue calling this a "strategic crisis": agents confidently produce code using the legacy GenerativeModel class from a package that has been replaced by an entirely different Client → get_model → start_chat paradigm. Imagine you're shipping a feature against an LLM SDK that rewrote its API last quarter. The agent's import line looks correct, the function names sound plausible, the example compiles if anyone has the old package installed, and it is talking to a system the maintainers no longer ship. Verify imports against the lockfile and the official docs, not the model's memory. Especially for SDKs that shipped a major rewrite in the last 18 months. 2. Suppressed errors and broad catches. AI-generated code routinely wraps unfamiliar territory in try/except: pass, catch (e) { console.log(e) }, or # type: ignore because the path of least resistance to a green build is to silence whatever the model does not understand. Snyk's CWE breakdown lists "Improper Check or Handling of Exceptional Conditions" (CWE-703) among the top weaknesses in Copilot output. Grep the diff for try, except, catch (e), eslint-disable, # type: ignore, and expect(true).toBe(true). Each is a cheap signal of an AI cul-de-sac. 3. Hallucinated correctness. GitHub flags the same pattern: code can compile, pass tests, and still hide off-by-one bugs, missing permission checks, or race conditions. Stanford's 2022 Perry et al. study found that developers with AI assistant access wrote less secure code and were more confident their code was secure. The NYU Copilot security study found roughly 40% of generated programs across 89 security-relevant scenarios contained vulnerabilities, with XSS, SQL injection, hardcoded credentials, and path traversal at the top of the list. 4. Over-eager rewrites. Cursor agents in particular reach for textbook patterns even when the codebase deliberately avoids them, because the rationale lives in tribal memory the model never saw. The OCaml maintainers famously rejected a 13,000-line AI-generated PR in 2025: the code was not bad; no human had bandwidth to review that volume. A pull request whose size exceeds your team's actual review capacity is not a contribution. It is a denial-of-service attack on your trunk. 5. Confabulated rationale. AI agents will write // validates input per RFC 7519 above code that does nothing of the sort, because the comment matches the surrounding semantic field. The comment is decoration, not specification. This is the inverse of how juniors fail; juniors under-comment correct code, while AI over-comments incorrect code. Read the comment as a hypothesis you have to falsify, not as a summary you can trust. Contractor review, not teammate review The reframe that ties all of this together is simple. Stop reviewing AI PRs the way you review your team's work. Start reviewing them the way you'd review a contractor you've never worked with. No mentorship comments as the main control surface. The agent will not internalize a review comment the way a junior engineer does. If the lesson matters, encode it in repo instructions, tests, templates, or CI. No growth trajectory. No "I trust them because they wrote good code last week." Every PR is independent. Every claim needs proof. The author has no intent to check, either. The PR description is itself agent-generated and may not reflect what the diff actually does. The right question is not "what was the author trying to do?" but "what does this code actually do, line by line, end to end?" That mental shift is uncomfortable for senior engineers because the apprenticeship instinct runs deep. Suppress it. Keep mentorship for the humans on your team. Spend it on the agent and you waste it. Eight techniques that actually work The practitioner consensus from GitHub's review playbook, Addy Osmani, Simon Willison, Birgitta Boeckeler's Exploring Generative AI memos, and the typia post-mortem boils down to a short list: 1. Read the CI changes first, before the source diff. Any change to .github/workflows/, pytest.ini, jest.config, lint config, or pre-commit hooks is a blocker until justified. Highest-yield filter on the list. 2. Diff the dependency manifest separately. Every new entry: does the package exist, is it current, is the name a typo of something popular? Slopsquatting hits here. 3. Grep for the cul-de-sac signatures. try/except, catch (e), // TODO, eslint-disable, # type: ignore, expect(true).toBe(true). Each one is a place the agent gave up. 4. Trace one critical path end-to-end yourself. Do not stop at reading it. Run it. The verification step is the part you cannot hand-wave: prove the behavior changed in the product, instead of only in the diff. 5. Verify imports against the lockfile and the official docs, not the model's memory. 6. Demand the prompt and the plan. The PR template should include the prompt that produced the change. If the agent's plan claimed to "preserve all tests" and the diff shows test deletions, that is the catch. 7. Tier by blast radius. Auth, payments, secrets, migrations, and IAM require mandatory human threat-modelling regardless of how clean the diff looks. Internal scripts and one-off cron jobs can get a lighter touch. 8. Cap the merge rate, not the generate rate. This is our operating rule: agent output can scale faster than human review capacity, so reviewed code per day is the real limiter. Set explicit limits on how much agent-generated code lands per day, sized to your actual review capacity. AI-aware review tools such as Greptile, CodeRabbit, and Cursor's Bugbot are useful as a triage filter, never as the gatekeeper. Greptile reports an 82% bug catch rate against CodeRabbit's 44% in their own benchmark, but with 11 false positives against CodeRabbit's 2. O'Reilly Radar's coverage of the field summarises the empirical state plainly: AI code review only catches half of your bugs. Run them as the first pass. Read the diff yourself for the second. For agent-authored PRs, require four boxes before human review: CI or test config changed? Dependency manifest changed? Prompt and plan included? Critical path named? If any answer is missing, the PR is not ready for review. The confidence inversion is the real threat The single most important reframe is this: AI confidence is not a reliability signal. OpenAI's 2025 paper Why Language Models Hallucinate argues that standard training and evaluation reward guessing over acknowledging uncertainty. The practical review lesson is narrower but still useful: fluent, assertive prose is not evidence that the generated code is correct. The clean docstring, the assertive comment, the tidy commit message, these are the regions to slow down, not speed up. For human juniors, confidence is a useful, if imperfect, signal of competence. For AI output, confidence mostly tells you that the model found a fluent path through the problem. Birgitta Boeckeler's framing on martinfowler.com is the right one: GenAI is a teammate "with cognitive biases that flow back into the developer." The reviewer reading clean AI output absorbs its confidence. That confidence transfer is the real threat to review quality, and it is what has to be consciously suppressed. The senior reviewers who do this well in 2026 are not the ones who ban AI tools. They are the ones who use the tools heavily, ship faster as a result, and have completely rebuilt their review checklist around the failure modes the agents actually produce. The teams that will get burned are the ones still running a 2019 playbook against 2026 output. If you are shipping AI-generated PRs into production and your review process has not changed in the last twelve months, that is the gap to close this quarter. We help teams audit and rebuild their review process, and we build production AI systems, including the engineering workflows around them, that ship without leaning on a green CI as the only signal. Book a call and we will walk through your current process, the failure modes most likely to be hiding in your trunk, and the smallest set of changes that will close the gap. --- ### What investors actually ask about your AI-generated codebase URL: https://appssemble.com/blog/investors-and-vibe-coded How founders can turn vibe-coded product risk into fundable diligence evidence. TechCrunch reported that a quarter of Y Combinator's Winter 2025 batch had codebases that were 95% LLM-generated. That changed the investor question. In vibe coding diligence, "did you write it?" is no longer useful. The harder question is: do you understand what you shipped? Technical due diligence, AI startup valuation, and codebase provenance now meet here. A founder can ship a real product with Cursor, Lovable, Bolt, Replit, or Claude Code, and investors will not automatically punish that. They will punish the founder who cannot explain the auth flow, the AI cost per active user, or who owns the rebuild when the first enterprise customer asks for security receipts. This post is not a warning against AI-generated code. We use AI every day inside our AI and engineering work. It is a warning against walking into a seed meeting with a working demo and no operational grip on the codebase underneath it. Investors stopped asking whether AI wrote it The old diligence script assumed the codebase had a human author. Investors asked about the stack, the architecture, and whether the team had the technical depth to keep shipping. With vibe-coded apps, the first version may have been assembled by a founder who can describe the product but cannot trace a request from browser to database. That does not make the company unfundable. It changes the test. More diligence conversations now ask whether the founder can read the code well enough to own the risk. The seven questions are becoming predictable: what percentage of the code is AI-generated, who reviewed it, where are the secrets, what is tested, what is the AI cost per active user, can the system handle 10x traffic, and who maintains it if the first engineer leaves. These are not trick questions. They are the investor trying to understand whether the codebase has an owner. If your answer is "the code works," you have not answered the question. Imagine you're a solo founder pitching a pre-seed round with 2,000 active users and a Lovable-built B2B app. A partner might ask you to screen-share, open the payment webhook, and explain what happens when Stripe retries a failed charge. If you need to re-prompt the tool to understand your own billing path, the investor has learned something important. Model the haircut before the investor does There is no clean public benchmark that says "vibe-coded startups trade 23% lower." The market is too new, and good companies break averages quickly. But the downside model is easy to understand once you put numbers on unscoped technical risk. FutureSight's summary of Carta data puts the 2025 median seed round around a $20M post-money valuation, with a $4M raise. If an investor believes $50K-$500K of hardening or rebuild work is still ahead, and also sees fragile AI gross margins with no human owner for core flows, that risk does not sit outside the round. It gets priced into the round. As scenario math, at $20M post-money, a 20% haircut means $4M of valuation gone before you negotiate terms. At 30%, it is $6M. The investor is not being philosophical about vibe coding. They are asking whether the next check funds growth or pays for cleanup that should have been scoped before the pitch. The same risk can get priced harder at Series A because the questions get less forgiving. Seed investors can underwrite a messy product with strong founder velocity. Series A investors need to believe the product can support more customers, more employees, and more revenue without turning the next six months into rescue engineering. The rebuild plan is part of the pitch Founders often bring the wrong artifact. They bring a product demo, a deck, maybe a Loom. What they need beside it is a rebuild plan. That plan does not need to say "we are throwing everything away." It should say which modules are safe, which modules need replacement, in what order, by whom, on what timeline, and at what cost. A credible answer might be: "We estimate $180K and four months to harden auth, payments, and the data layer; the product can keep shipping while that happens." That answer is fundable because it converts unknown risk into scoped work. It also shows that you understand the difference between a prototype that validates demand and a product that can survive customers, audits, and employees. The founders who struggle are the ones who say, "we will hire engineers after the round." Investors hear that as: the codebase has no owner today, the first hire inherits a black box, and the first 90 days after funding will be spent figuring out what was built. That is close to the diligence frame in JPMorgan's founder guide: security and compliance, scalability planning, quality assurance, and technical debt management. Not "AI-generated code is bad." More like: prove the system can survive the next stage. Codebase provenance beats founder confidence Codebase provenance is a boring phrase for a very practical document. It lists which tools generated which parts of the app, which files were rewritten by humans, which flows have tests, which secrets have been rotated, and which parts nobody has reviewed yet. This matters because AI-generated code can look coherent while hiding structural debt. It can make the happy path pass, scatter business logic across three files, ship a key into the browser, and create a database policy that checks whether a user is logged in rather than whether the row belongs to that user. Investors do not expect perfection at pre-seed. They do expect a map. If you can show a one-page ownership audit, a test matrix for auth and billing, a security scan, and a list of unresolved risks, you change the conversation from "trust me" to "here is the surface area." This is also where AI product founders need an evaluation pipeline if model output is part of the product. Manual testing is not enough. Bring the golden dataset, the CI gate, the last 30 days of eval diffs, and the cost table that shows what each active user costs by plan. The code works is no longer an answer "The code works" means it works under the conditions you have already seen. Investors are trying to price the conditions you have not seen yet: 10x traffic, a security questionnaire, a failed payment spike, a model price change, an engineer leaving, or a customer asking for audit logs. This is why AI gross margin has become part of technical diligence. Bessemer's 2025 dataset on AI companies put early gross margins around 25%, far below traditional SaaS expectations. ICONIQ's tracked trajectory moved from 41% in 2024 to 45% in 2025 and 52% in 2026, but that path requires actual cost work: caching, model routing, batching, prompt compression, and tier-level pricing. If you do not know your AI cost per active user, the investor assumes the worst. If you know it, and you can show the path to 60% gross margin, the conversation changes. You are no longer selling a demo. You are showing control over the machine that makes the demo economically viable. Security works the same way. A scan report, a secrets-rotation policy, Row Level Security coverage, and a human code review do not make a codebase perfect. They prove that someone is responsible for finding the next failure before a customer or attacker does. Base44 did not win because the code was magical Base44 is the cleanest proof that vibe-coded products can create real outcomes. Wix announced the acquisition for approximately $80M of initial consideration plus earn-outs after roughly six months. TechCrunch reported that Base44 was bootstrapped, had eight employees, reached about 250K users, and made $189K of profit in May. That is not a toy outcome. But the lesson is not "investors do not care about code." Base44 sold to a strategic buyer with distribution, engineering capacity, and a reason to absorb the maintenance risk. The product had traction strong enough to make the codebase a solvable problem. Lovable shows the same pattern at platform scale: a $7.5M pre-seed in 2024, a $200M Series A at a $1.8B valuation, and a later $330M Series B at a $6.6B valuation. Anything reached $2M annualized run rate in two weeks, then raised $11M at a $100M valuation. In those cases, revenue and distribution changed the diligence math. The pattern is simple: when revenue is real, vibe coding can be an acceleration story. When revenue is not real, it becomes a risk story. The same AI-generated codebase can read as speed in one meeting and debt in another, depending on the founder's grip and the traction behind it. Bring the documents before they ask The best founders do not wait for diligence to expose the gap. They bring the gap into the room with a plan attached. Start with the three documents that change the meeting fastest: an ownership audit, a rebuild scope, and cost and security evidence. Then add the rest. For any vibe-coded product, bring an ownership audit, a rebuild plan, an architecture diagram, a maintenance plan, distribution numbers, and security receipts: SAST or dependency scan, secrets-rotation log, auth/RLS review, and a named owner for remediation. If model output is the product, bring evals too: the golden dataset, the CI gate, the last 30 days of output diffs, and cost per active user by plan. If not, bring an auth and billing regression test matrix. You do not need a 40-page binder. You need short artifacts that make the codebase legible. A two-page rebuild plan beats a vague promise. A one-page cost table beats a confident statement that margins will improve later. At appssemble, this is the work we walk founders through before a pitch: audit what exists, scope what must change, and separate "prototype debt" from real company risk. Sometimes the answer is a two-week hardening sprint. Sometimes it is a route-by-route rebuild. The point is to know before the investor does. The fundable founder owns the system Vibe coding lowers the cost of getting to a product. It does not remove the responsibility for understanding that product once users, revenue, and investor money are involved. The founder who wins is not the one who pretends every generated line is production-grade. It is the one who can say: here is what AI wrote, here is what humans reviewed, here is what we are replacing, here is what it costs to run, and here is why customers keep coming back. If you are raising with a vibe-coded product and want a straight read before diligence starts, book a call. We walk founders through the ownership audit and rebuild scope before the pitch, so the investor meeting is about growth instead of unknown engineering debt. --- ### AI with a leash: why senior teams keep Cursor and Claude Code in production after a rebuild URL: https://appssemble.com/blog/cursor-claude-code-in-loop-after-rebuild How hardened repos make Cursor and Claude Code safe after a rebuild The dominant industry story about a rebuild goes like this: the team shipped too fast, accepted too much AI-generated code, hit a wall, and now the rebuild is the moment to "rip out the slop and go back to humans." It is a satisfying narrative. It is also wrong. When we run rebuilds for scale-ups, we don't ban Cursor or Claude Code on the new codebase. We use them more deliberately: smaller tasks, tighter prompts, deterministic checks. The reason is straightforward: the work that justifies a rebuild, types, tests, telemetry, row-level security, idempotent migrations, error budgets, is exactly the work that makes AI assistants safe to use. Hardening is the leash. Without it, AI is dangerous. With it, banning AI throws away productivity to avoid a problem the rebuild already solved. This post is the playbook we hand to a CTO on the Monday after a rebuild ships. It is opinionated and operational. The first half is the thesis your founder needs. The second half is the configuration your engineers need. Why the "no AI after rebuild" reflex breaks down The reflex is rooted in real failure modes. The "AI coding death spiral", agents fixing one symptom while regressing three others, is documented across both Cursor and Claude Code communities. The rebuild postmortem usually surfaces the same four patterns: deleted failing tests, suppressed type errors, removed telemetry to "simplify," and git commit --no-verify to bypass pre-commit hooks. A team that just lived through six months of that wants the assistants gone. But the assistants weren't the root cause. The repo was. An untyped, untested, telemetry-light codebase is unreadable to a junior engineer and equally unreadable to an LLM. When the agent has nothing to anchor against, it hallucinates, and the suppressions compound. The rebuild fixes the anchoring problem. Type errors now mean something. Tests now run in seconds. CI now blocks bypasses. The model still tries the same shortcuts, but now they fail loudly instead of silently. We see this pattern in rebuild work. Suggestions that were mostly rejected on the legacy repo start landing once architecture boundaries, tests, and type errors are trustworthy. The agent isn't magically smarter. The repo is more honest, so its suggestions have something solid to attach to. The right framing isn't "no more AI." It is bounded AI on a codebase that can say no. How a hardened repo becomes AI-safe Four failure modes that were untrackable on the old codebase become catchable on the new one. 1. Suppressed types. A diff-only ESLint gate that fails the build on any new as any, @ts-expect-error, or eslint-disable line stops the assistant's favorite escape hatch at PR time. The model can suggest the suppression. CI will not let it merge. 2. Deleted tests. Coverage thresholds, 80% as the floor, 100% on auth/, billing/, and policy directories, make test deletion visible in the diff. Combined with CODEOWNERS and branch protection that requires code-owner review, the deletion needs a named human to wave it through. 3. Removed telemetry. A custom ESLint no-restricted-imports rule that flags edits to telemetry.ts, logger.ts, or feature-flag files turns the "I simplified this" PR into a red diff. The agent learns the boundary because the linter teaches it. 4. Bypassed pre-commit. The Liam ERD team documented this one cleanly: agents reach for git commit --no-verify the moment a hook fails. The fix is a Claude Code permission deny on the exact command, plus a Lefthook configuration whose fail_text addresses the agent and tells it to fix lint errors before committing. In our variant, we make the bypass explicit: do not use --no-verify. None of those four checks is novel. All four were structurally impossible on the pre-rebuild codebase. That is the asymmetry the founder needs to see: the rebuild did not eliminate the need for AI judgment. It eliminated the need to trust AI judgment. The rebuild is the moment to draw the lines Some directories are not for the agent. The rebuild is when you decide which ones, and you fence them in three places. Imagine you're the CTO at a Series A SaaS the morning after a rebuild ships. The repo has src/auth/, src/billing/, db/migrations/, infra/, and policies/, code that, if it goes wrong, ends in a Stripe refund cycle, a data leak, or a regulator email. You have one chance to set the perimeter before someone opens Cursor and asks it to "refactor the billing logic for clarity." The three fences are CODEOWNERS with branch protection, a Claude Code hook or equivalent local deny layer, and a CI gate. Cursor Project Rules steer Cursor, but they do not deterministically block writes. CODEOWNERS requests the named reviewer automatically; branch protection or a GitHub ruleset makes that review required. The Claude Code hook stops Claude Code from writing protected files in the session. CI is the backstop: even if local controls are bypassed, the pipeline still refuses the merge. That redundancy is deliberate. Each fence catches a different failure mode, and each one is cheap. Skipping any of them makes the other two brittle. Instruction files are the constitution Once the perimeter is set, the next question is how the agent learns the rules of the inside. The answer is the markdown-in-repo instruction file. Cursor reads .cursor/rules/*.mdc. Claude Code reads CLAUDE.md. Codex, Amp, Jules, Factory, and Cursor all converge on the cross-tool AGENTS.md standard now stewarded by the Agentic AI Foundation. The OpenAI Codex monorepo ships 88 AGENTS.md files, one per subproject, to give the agent the right context wherever it lands. These files are advisory. They instruct the model. They do not force it. That distinction matters for everything that follows. The single biggest mistake we see on a freshly rebuilt repo is bloat. HumanLayer's analysis is blunt: frontier LLMs reliably follow approximately 150-200 instructions, and Claude Code's own system prompt already burns about 50 of them. Anthropic's guidance is the same: "Keep it concise. For each line, ask: Would removing this cause Claude to make mistakes? If not, cut it. Bloated CLAUDE.md files cause Claude to ignore your actual instructions." Target under 300 lines. Use @path/to/file imports for anything specialized. A good CLAUDE.md covers the things the agent cannot guess from the code: bash commands, code-style rules that differ from the language default, the test runner, branch naming, the architectural decisions that aren't yet ADRs, and the gotchas that bit the last engineer. It does not contain a tutorial on TypeScript or a file-by-file map of the codebase. The agent can read the codebase. It cannot read your team's history. The highest-impact block in the file is the deny list. In our rebuild work, it only works when paired with deterministic checks: the markdown names the failure mode, and the hook or CI gate enforces it. # Never - Never delete or modify .env, .env.*, package.json, lockfiles, or migration files without explicit confirmation. - Never add eslint-disable, @ts-expect-error, or as any to silence an error. - Never delete a failing test. Fix the code. - Never remove logging, telemetry, or feature flags to make a test pass. - Never run git commit --no-verify, --force, or git push --force. - Never assume a package exists, run pnpm list first. Six lines. Each one corresponds to a real PR we have rejected. Each one closes a known regression class. Hooks force what CLAUDE.md only requests CLAUDE.md is a request to the model. Hooks are a runtime contract. Anthropic's framing is the one to remember: "Unlike CLAUDE.md instructions which are advisory, hooks are deterministic and guarantee the action happens." Three hook events do most of the work. SessionStart runs once when the agent opens the repo. We use it to inject the current branch, uncommitted files, and the active Linear or GitHub issue into context. The agent now starts every session knowing where it is in the codebase, not asking. PreToolUse runs before every tool call. In Claude Code, it is the right place to deny edits to protected paths. The script reads the file path the agent wants to write, matches it against a regex covering auth/, billing/, migrations, .env*, and lockfiles, and returns a deny decision with a reason the agent can read: { "hookSpecificOutput": { "hookEventName": "PreToolUse", "permissionDecision": "deny", "permissionDecisionReason": "Edits to src/billing/ require human review. Open a PR with the change in a separate commit." } } The agent does not get a "you cannot do that" silence. It gets an instruction to do the right thing. Hook scripts run with the user's system permissions, so treat them like production automation: quote variables, use absolute paths, reject path traversal, and keep sensitive files out of scope. PostToolUse runs after every successful edit. We wire it to pnpm -s lint --max-warnings=0 && pnpm -s typecheck, then return a blocking result when either fails. Without that blocking behavior, the hook is feedback, not enforcement. The deny list in .claude/settings.json is the final piece. Block the bypass at the permission layer, instead of only in prose: { "permissions": { "deny": [ "Bash(git commit --no-verify:*)", "Bash(git push --force:*)", "Bash(git push -f:*)", "Bash(rm -rf:*)" ] } } Combined with a Lefthook pre-commit and required CI checks, the agent cannot merge code that fails lint, typecheck, or changed-package tests. The local hook helps the agent fix issues early. CI is what makes the rule non-negotiable. Verification baked into every prompt The structural protections handle the agent. Spec discipline handles the prompt. The rebuild is the moment to retrain your team on how to ask. Anthropic's verification guidance, paraphrased from their best-practices doc, is the single most useful sentence in the corpus: "Without clear success criteria, the agent might produce something that looks right but actually doesn't work. You become the only feedback loop, and every mistake requires your attention." The fix is to write the success criteria into the prompt. "Implement a function that validates email addresses" becomes *"Write a validateEmail function. Example test cases: user@example.com → true, invalid → false, user@.com → false. Run the tests after implementing."* The first prompt asks for code. The second prompt asks for code that passes a test the agent must run. Only one of them produces a verifiable result. Test-first specs are the natural extension. Have the agent write the tests first, get a human or a reviewer subagent to approve them, then iterate the implementation until they pass. The test suite becomes the contract. The implementation becomes negotiable. For the review pass, separate the writer from the reviewer. Anthropic's own guidance: "a fresh context improves code review since Claude won't be biased toward code it just wrote." The HAMY post documents one public version of the pattern: 9 parallel Claude Code review subagents for tests, lint/static analysis, code review, security, quality/style, test quality, performance, dependency/deployment safety, and simplification. Our version starts with fewer agents: security, tests, migrations, and RLS on repos where those paths carry real blast radius. Nine subagents sounds like overhead. It is cheaper than one bad merge into src/billing/. What this looks like for your team next week If your rebuild is recently shipped and your team is asking whether to ban Claude Code or keep it, the practical sequence is short. Week one: write the CLAUDE.md and the .cursor/rules/ files. Keep them under 300 lines combined. Include the deny list. Reference the test commands. Add CODEOWNERS for auth/, billing/, migrations/, infra/, policies/, and the CODEOWNERS file itself. Configure branch protection or rulesets to require code-owner review. Week two: add the three Claude Code hooks: SessionStart for context, PreToolUse for the protected-path deny, PostToolUse for lint and typecheck. Add the permission deny list for --no-verify and force-push. Wire Lefthook to mirror the same checks at the commit boundary, and make Cursor-authored changes pass through the same CI and branch-protection gates. Week three: add the diff-only ESLint gate for new suppressions, the coverage floor in CI, and one or two review subagents, start with security and tests. Run claude -p in headless mode against PRs as a CI step. By the end of the third week, you have bounded AI in production. The agent is useful again on scoped work. Claude Code cannot directly write protected files in the session, and Cursor-authored changes cannot merge without the same CI and owner checks. The main regression classes your rebuild was meant to prevent are now caught by deterministic checks. The team that built it is the team that maintains it, same as our engineering practice on every other client. The rebuild was not the end of AI in the codebase. It was the beginning of the only configuration in which AI in the codebase is responsible. If your rebuild is live and your team is split on whether to ban Claude Code or keep it, we can help you keep the useful parts of AI without reopening the blast radius. Book a call. --- ### How to Vet Your First Engineer When You Cannot Read the Code URL: https://appssemble.com/blog/vetting-a-developer How nontechnical founders can assess candidates, run paid trials, and avoid costly first-engineer mistakes. The Lovable and Bolt boom created a weird hiring market: founders with real traction, real revenue, and codebases they cannot personally judge. That gap gets filled by $200/hr "AI engineers" who can demo fast but cannot explain a Postgres query plan, a migration rollback, or what happens when Supabase hits connection limits. If you are a non-technical founder preparing to hire a senior engineer, your job is not to become one first. Your job is to grade the signals around the code. Think of this as a first engineer playbook for vetting developers when you cannot read every line yourself. A reverse code review and a paid trial do not make hiring safe. They make the risk visible before you commit to six months of salary, roadmap delay, and cleanup work. You cannot grade code, so make every candidate grade yours The worst interview starts with abstractions: "Tell me about your experience," "Are you good with Supabase," "Can you scale this app?" Anyone can answer those questions well for 45 minutes. The better interview starts with your actual repo. Before you call candidates, ask any junior developer or technical friend to pull three artifacts from the codebase: the top 20 most-changed files, the list of external services the app calls, and the 3 areas that scare you most. For a post-Lovable product, that usually means auth, payments, and the AI feature. Give every candidate the same packet and ask them what worries them. This is the reverse code review approach Jacob Kaplan-Moss formalized in 2021: instead of you reviewing the candidate's code, the candidate reviews yours. You do not need to know whether their diagnosis is perfect. You need to compare five answers to the same file and notice who asks useful questions, who jumps to rewrite, and who can explain risk without performing technical theater. Imagine you're running a B2B workflow app with 400 active users and Stripe billing glued into a Supabase table. One candidate says, "I'd rewrite this in a fresh Next.js app." Another says, "I need to understand how subscription state moves from Stripe webhook to database row to UI access before touching it." The second person is already acting like an owner. GitHub shows behavior, not seniority GitHub is useful, but not in the way founders think. Green squares are weak signal. Ben Frederickson's GitHub Archive analysis found that only about 17% of users pushed public code in the prior year. The exact number is old, but the lesson still holds: many strong engineers spend most of their time in private repos. Look for behavior instead. Issues and pull requests on other people's repos show how the candidate thinks in public: do they write clear bug reports, disagree politely, and review code with context? Commit messages also tell a story. "fix" tells you almost nothing; "fix: short-circuit Stripe retry loop on 402 to prevent duplicate charges" tells you they understand cause, effect, and production risk. Language breadth is another place where founders get fooled. A senior engineer is usually deep in 2 or 3 stacks, not magically senior across 8 languages and every framework on the homepage. If they claim React, Node.js, PostgreSQL, Swift, Kotlin, Rails, Python, LangGraph, and Kubernetes with equal confidence, ask them which 2 they would bet your company on. No public GitHub is not a red flag by itself. Refusing to show any work is. A serious candidate can share a redacted PR, walk through a private repo on screenshare, or show an architecture write-up without leaking a previous employer's IP. Five questions beat a whiteboard interview You do not need a coding test to learn whether someone can operate. You need questions where the shape of the answer is visible even if you cannot grade every technical detail. 1. "Walk me through the last bug you shipped to production." Senior engineers have scars and can describe them plainly: what broke, how they found it, what they changed, and what guardrail they added afterward. Frauds get vague or blame the rest of the team. 2. "What would you not touch in our stack right now?" This filters out rewriters. A senior engineer knows that the fastest way to destroy a young product is to replace working parts before understanding why they exist. 3. "Our app uses Supabase and Postgres. What happens if 1,000 people sign up in one hour?" You are listening for concepts: connection limits, RLS policy cost, rate limits, indexes, background jobs, and cold starts. They do not need your exact numbers on the call; they need to have seen this movie before. 4. "Show me a PR you wrote with Cursor or Claude Code assistance." In 2026, AI use is not the differentiator. Taste is. Good engineers can explain what they accepted, what they rejected, and what rules they use to keep generated code from drifting the codebase. 5. "Explain database indexes to me in 90 seconds." Your first engineer will teach you enough to make better product decisions. If they condescend, hand-wave, or get annoyed by follow-up questions, that is how the next six months will feel. A paid trial is cheaper than a confident mistake The strongest hiring processes do not end with a vibe check. Linear, Automattic, PostHog, and other serious software teams use paid work simulations because real work exposes the gaps interviews hide. Their exact formats differ, but the pattern is the same: pay the candidate, use real or realistic work, and judge communication as much as output. For a first engineer, the trial should be short, paid, and real. Our recommended budget is 3 to 5 working days, a $3K to $8K flat fee for a senior contractor, and one ticket from your actual repo. Give them repo access, staging access, and one Slack channel. The output is a PR, a written one-page reflection, and a 30-minute walkthrough. The ticket should be useful even if you do not hire them. Pick something with clear acceptance criteria: add a Stripe billing state fix, harden a Supabase policy, move one OpenAI call behind a server endpoint, or add observability around a fragile flow. Do not give them a toy problem. You are hiring someone to protect a live product, not solve riddles. What matters is how they work. Do they ask one good question before coding? Do they write a PR description that explains why the change exists? Do they show tests or at least a manual verification path? Do they name the risk they did not fix? The math is simple. In our model, a paid trial costs about $5K. A wrong first engineering hire can reach six figures quickly. At the high end, it can look like a $250K mistake once you count six months of salary, recruiter time, delayed roadmap, production debt, and the second engineer you hire to unwind the first one's work. Eleven red flags are enough to stop the process Do not soften these because the candidate is charming. The charm is part of the risk. They recommend a rewrite before reading the code. They quote a fixed number before seeing the repo. They refuse a paid trial because they are "too senior." They will not show prior work in any form. They promise business outcomes like "100K users" instead of engineering outcomes. They estimate unfamiliar work in days when it clearly has week-level unknowns. They speak in absolutes: "Postgres cannot handle that," "you need Kubernetes," "AI does it all now." They never ask who your customers are or what breaks first. They push for a monthly retainer on day one with no scoped deliverable. They have no questions for you at the end of the call. They will not sign a basic NDA and IP assignment before touching the repo. One red flag can be context. Three is a pattern. If the pattern appears before money changes hands, believe it. Green flags are just as specific The right engineer does not sound magical. They sound careful, curious, and slightly allergic to premature certainty. They ask to see the code before quoting. They ask who your customers are and what they complain about. They ask about monitoring, alerts, backups, and how you recover when Stripe or Supabase behaves badly. They estimate in ranges with assumptions: "2 to 4 weeks if auth is already clean, 6+ if we need to migrate user state." They tell you what they would leave alone. They send a written follow-up that summarizes what they heard, what they would do first, and what they would not do yet. The strongest signal is teaching. If they can make you understand why one RLS policy matters, why direct browser-to-database access is risky, or why a migration needs a rollback plan, they are reducing your dependence on them instead of increasing it. The first engineer is an ownership decision Your first engineer is not a pair of hands. They are the person who decides whether your Lovable or Bolt app becomes a production codebase or a more expensive pile of prompts. That is why the hiring process has to test ownership, not performance. At appssemble, our engineering work starts the same way: read the code, name the risks, ship a contained fix, and only then talk about the larger roadmap. We do not sell hours or headcount. We take responsibility for the product surface we touch. If you are about to hire your first senior engineer and the repo already has traction, run the reverse review and paid trial before you commit. In our typical budget model, the trial is a roughly $5K decision. The wrong hire can become a six-figure cleanup. Book a call if you want us to review the codebase, shape the trial ticket, or take ownership of the first production hardening pass. --- ### Stop rewriting your vibe-coded MVP. Here's what works instead. URL: https://appssemble.com/blog/just-rebuild-it-advice-wrong Why incremental migration beats risky full rewrites for vibe-coded MVPs You have paying users. Maybe 200, maybe 2,000. The product was glued together in a weekend with Lovable, Cursor, and three frantic prompts to Claude. Now a senior engineer has looked at the repo, sucked air through their teeth, and told you the only way forward is a full rewrite. That advice is wrong more often than it's right, and the cost of getting it wrong is brutal. Netscape took the rewrite advice in 1998. By the time Netscape 6.0 shipped in November 2000, Internet Explorer had already overtaken Navigator and Netscape's browser business had lost the market window it needed to defend. Digg v4 did the dangerous version of a rewrite: it replaced the code, architecture, infrastructure, and the community mechanics users depended on. Traffic fell 26% in the month after launch and Reddit's traffic grew 230% the same year. By 2012 Digg was sold to Betaworks. This post is for the founder or first technical lead staring at a vibe-coded codebase, holding a quote for a $45K rewrite, wondering if there's another way. There is. It's slower in month one and far faster in months three through twelve, and it's the only path that doesn't cost you the customers you already have. The rewrite fantasy is real, and the math behind it isn't Before we tear down the rewrite, let's give it its due. The fantasy is seductive for honest reasons. The codebase looks like spaghetti. Every new feature breaks two old ones. You're embarrassed to show the repo to anyone you'd want to hire. The vibe-coding tools made the first version feel free, so the second version should feel free too. It won't. The numbers are well-known and rarely shown to founders considering a rewrite. McKinsey and the University of Oxford studied more than 5,400 large IT projects with initial budgets over $15M. On average, those projects ran 45% over budget, 7% over time, and delivered 56% less value than predicted, with $66B in total cost overrun across the sample. That does not mean your $45K rebuild has the same risk profile. It means the moment you turn a bounded product problem into a broad replacement project, the base-rate math gets uglier. For vibe-coded MVPs specifically, a useful planning heuristic is that the rebuild quote often lands around 2-3x the original AI-assisted prototype spend. A $15K weekend MVP becoming a $45K rebuild is not a law. It is the number you should budget against before you accept the "just rebuild it" advice. Why "just rebuild it" is the default advice (and why it's still wrong) Joel Spolsky wrote the canonical takedown in April 2000, after Netscape's rewrite was already in motion. His core argument has aged perfectly: it is harder to read code than to write it. When you look at a messy codebase and think "this is a disaster," what you're mostly seeing is your own unfamiliarity with someone else's reasoning. The mess is also load-bearing. It contains every bug fix that took weeks of real-world usage to find: the obscure edge case where Nancy's installer broke because she didn't have Internet Explorer, the auth flow that handles a payment provider's three-second delay, the rate-limit retry that exists because a user's iPad keeps dropping connection on the subway. Throw away the code and you throw out Nancy. You also throw out three to twelve months of runway during which your competitors keep shipping. Spolsky put it bluntly: "You are giving a gift of two or three years to your competitors, and believe me, that is a long time in software years." There's a less polite reason rewrite advice is so common. Sometimes it is honest. Sometimes it is also the easiest thing to sell: the engineer gets a clean repo, the agency gets a clean scope, and the founder carries the risk of rediscovering every edge case users already taught the old product. We have turned down rewrite contracts at appssemble for exactly this reason: the honest answer in most cases is "you don't need a rewrite, you need someone who can read your existing code and introduce seams." The Strangler Fig: how grown-up engineering teams actually do this Martin Fowler named the Strangler Fig pattern in 2004 after the vines he saw in the Queensland rainforest. The vine germinates in a nook of a host tree, sends roots down toward the soil, and grows around the host until the host can be removed. New software grows around the legacy system the same way: feature by feature, route by route, until the old system is no longer doing any work and can be deleted. Fowler is clear that this still costs real work. You have to build transitional architecture so old and new code can coexist. The win is that the investment and the return become visible gradually instead of arriving as one risky launch. The teams you've heard of usually run some version of this incremental play, not the big-bang play. Slack rewrote their desktop client between 2017 and 2019. The post-mortem is literally titled "When a rewrite isn't." They defined a target architecture and strict legacy-interop rules: old code couldn't import new code directly, only through "exported" interfaces; new code couldn't import old code directly, only through "adapted" interfaces. The first piece of the new architecture they shipped to users was the emoji picker, two years before the full rewrite was finished. Then the channel sidebar. Then the message pane. There was no big-bang release and no week where users woke up to a completely unfamiliar Slack. Shopify took the modular-monolith path. Their core Rails codebase has been worked on for more than a decade by more than a thousand developers. Instead of splitting everything into services, they reorganized around business components and later used Packwerk to enforce package boundaries in CI. Twitter incrementally replaced subsystems too: message queue, tweet storage, then the search front-end, which produced a 3x latency drop in 2011. By US election day 2012, Twitter handled 327,452 tweets per minute. That is incremental migration and re-architecture under load, not a six-month freeze followed by a launch party. Stripe's published migration playbook is even stricter: dual-write, compare old and new behavior in production, move reads, then writes, then delete the old path. Their own summary is the line founders should remember: "All changes were incremental, never attempting to change more than a few hundred lines of code at a time." The lesson across all of them is practical, not ceremonial. Preserve working behavior. Put clean boundaries around the old paths. Extract one bounded context at a time. Run new code alongside old code with traffic shifting feature by feature. Keep the data layer stable as long as possible. Delete old code only when nothing calls it anymore. Ship value to users every two weeks throughout. Never go dark. Five reasons incremental beats big-bang for a vibe-coded startup 1. You keep shipping to your users. Imagine you're running a small B2B tool with 300 paying customers, churning at 4% a month. A six-month rewrite means you ship zero customer-facing improvements for 24 weeks. With a 4% monthly churn rate, you lose roughly 22% of your base before the rewrite is even done, and they leave for whichever competitor shipped the integration they asked for. Incremental migration keeps your release cadence intact. You replace the auth module behind the scenes; the user just sees that login is faster. 2. You don't pay the second-system tax. Fred Brooks called the second system the most dangerous you'll ever design. The team building the rewrite is confident, well-rested, and quietly importing every feature you wisely cut from version one, plus generalizations you'll never use. Incremental work has no place to hide that bloat. Each piece has to justify itself against a working comparison. 3. The data stays where it is. Most rewrites don't fail at the code layer. They fail at the data migration. A vibe-coded MVP usually has weird data, three different "user" tables in Supabase that don't reference each other, JSON blobs holding business logic, foreign keys held together with hope. Incremental work lets you stabilize the schema as a separate workstream from the code, instead of doing both at once under launch pressure. 4. You discover what's actually broken versus what's just unfamiliar. Spend a week reading the existing code before you decide. Most founders find that large parts of the product are not broken enough to justify a rewrite. The real seams tend to be concentrated: auth, payments, reporting queries, background jobs, and whatever times out under load. Now you have a list of things to extract, ranked by pain. That's a roadmap. A rewrite is not a roadmap. 5. Investors read the difference. Technical due diligence reads whether you control the asset. A founder who can show old code shrinking month over month, new code with tests and observability, and no downtime reads as someone in control. A founder mid-rewrite reads as someone asking investors to fund uncertainty. "But what if my code is genuinely unsalvageable?" Sometimes it is. We're not selling a religion. A rewrite is the right call in five specific cases: You have under 50 paying users and no third-party integrations. The Spolsky calculus inverts when there's almost no embedded user behavior to preserve. Throw away the demo; build the product. The architecture has no seams at all. If the entire app is a single 4,000-line App.tsx with all the business logic in the React tree and no backend, your first project is introducing a real backend boundary. That may feel like a rewrite, but it should still be staged around the data and user flows you need to preserve. The data model is incoherent and you have no production data worth keeping. Fix the schema once and start clean. Security is so broken that the existing user data is a liability. Sometimes the right move is to nuke the database, notify users, and start over with proper auth. You are a solo founder who didn't write any of the existing code. When there is no team continuity, reading unfamiliar code can cost more than writing fresh code. Spolsky's law inverts when "the team" is one person who has never seen the repo. If none of those five describe your situation, the default is incremental. Friendster is the counterexample that keeps this honest. Refusing to fix a scaling architecture can kill you too. The point is not "never rewrite." The point is to make the decision specific before you spend the money. A six-question framework before you decide Before you accept the rewrite quote, run this: Do you have paying users? If yes, default to incremental. Are there any seams at all, auth, billing, an email service, anything you could lift out? If yes, you can apply Strangler Fig. Is the data layer salvageable? If yes, keep it. Most rewrite pain is data pain. Can you ship visible value to users every two weeks during the work? If no, you don't have a plan. You have a death march. Are you rewriting because the code is bad, or because you don't understand it? Read it for a week first. Would a senior engineer who isn't getting paid by the rewrite hours recommend it? Most of the time the answer is no. If at least four answers point to incremental, do incremental. If all six point to rewrite, then maybe rewrite, but with an explicit Slack-style coexistence plan, not a big-bang launch. Before you sign the rebuild quote, ask for four artifacts: a seams inventory, a data-risk map, the first two modules to extract, and the rollback and observability plan. If the plan cannot ship one visible improvement inside two weeks, it is not a migration plan yet. What the right partner does instead The job of a senior engineering partner is not to validate the rewrite fantasy. It's to read the existing code, separate the parts that work from the parts that don't, name the seams, and replace one piece at a time. That work usually starts with a product design pass on the data model and the user-facing flows, because those are what need to stay stable while the engine room gets rebuilt underneath. The "just rebuild it" advice is wrong because it treats your current product as worthless. It isn't worthless. It contains every lesson you've paid for in real customer behavior, every weird edge case Nancy hit, every payment retry your users tolerated, every integration your largest customer demanded. Throw it out and you also throw out the proof that any of it works. If you're holding a rewrite quote and a list of paying customers, talk to us before you sign. We'll read the code, map the seams, and give you a rebuild/no-rebuild decision with the first extraction plan. If you are one of the five true rewrite cases, we will say so before you spend the money. Book a call. --- ### 10x the latency before the load test even starts: what k6 reveals in a "production-ready" Lovable app URL: https://appssemble.com/blog/load-testing-production-ready-lovable A k6-driven guide to finding Supabase, PostgREST, and Vercel bottlenecks before launch A founder messaged us last month with the same line we hear every few weeks. "We shipped it in two weeks on Lovable. Staging is flawless. We launch Tuesday." Then the screenshot: 50 virtual users in k6, p95 north of five seconds, a wall of 504s, Postgres CPU pinned at 96%. Lovable is genuinely good at the first ninety percent, getting an idea from a Figma sketch into a working React/Vite app with Supabase behind it faster than a senior team can spin up a repo. The trouble is the last ten percent. Production shipping is a different discipline, and the export that survived staging can fall over the first time real traffic shows up. The good news: fixing it is usually targeted repair, not a rewrite. This post is the build-log of what breaks, in what order, and the ten changes that took one anonymized appssemble rescue from cratering at roughly 30 RPS to clearing roughly 220 RPS with sub-100ms p95, without upgrading a single piece of compute. What you're actually shipping when you ship a Lovable export A typical Lovable export in 2026 is React + Vite + TypeScript, with Tailwind, shadcn/ui, and Radix UI in the component layer. For persistence and auth, the app usually sits on Lovable Cloud: a Supabase-backed managed backend, or on a Supabase project the founder owns directly. The Vercel and Next.js details in this post come from the exported or migrated apps we see after teams put the frontend on Vercel, wrap the app in Next.js, or add API routes around the generated client. The risky pattern is not the frontend framework. It is browser-side data fetching, unpaginated Supabase reads, generated RLS policies with no supporting indexes, missing cache headers, and no rate-limit boundary between real traffic and Postgres. Each of those defaults is reasonable in isolation. Stacked together, they form a stack that performs beautifully for one user and falls apart at fifty. The ceilings are not opinions, they are documented limits. A Micro Supabase instance allows 60 direct Postgres connections and 200 client connections through the Supavisor pooler. Separately, PostgREST has its own database pool; it returns 504 / PGRST003 when that pool cannot acquire a connection before db-pool-acquisition-timeout. Supavisor's client cap and PostgREST's pool timeout are different limits, but the operational lesson is the same: reduce query time, reduce request count, and stop fanning out tiny reads. This matters because the cost of finding out in production is asymmetric. A failed launch costs you the launch, and on a select('*') heavy schema, it can cost you a four-figure bandwidth bill on the way down. What breaks first, in the order it breaks Run a five-minute, 50-VU steady-state ramp at the Lovable exports we audit and the failures arrive in a predictable sequence. The exact RPS depends on response time, think time, and whether the script batches requests, but the same four dominoes keep falling. 1. Cold starts and idle scale-down. Vercel scales functions down when traffic disappears, and the next request can pay a cold-start penalty. Archived functions are a longer-window case in Vercel's docs, within two weeks for Production deployments and 48 hours for Preview, not a fifteen-minute timer. The user-facing symptom is simpler: the first request after quiet traffic is slower than the warm path. **2. useEffect waterfalls.** In the Lovable exports we audit, dashboards often render parent → child → grandchild, and each level fetches in its own effect. Three sequential 200ms requests gives you 2-3 seconds of page-ready time before the backend has felt any load at all. Add network jitter and you're at six seconds with zero VUs. 3. PostgREST pool-acquisition timeouts. When PostgREST cannot borrow a database connection from its own pool before db-pool-acquisition-timeout, it returns 504 / PGRST003. Supavisor's 200-client Micro cap is a separate ceiling for direct or pooler database clients. You can hit either limit under fan-out, and neither one degrades gently. 4. RLS sequential scans burning Postgres CPU. The generated policy pattern we often see, using ( auth.uid() = user_id ), calls auth.uid() per row and, without an index on user_id, runs a full table scan on every authenticated read. EXPLAIN shows Rows Removed by Filter: 50000+ on tables of any size. Once the pool is even partially backed up, per-query CPU cost is what tips Postgres into 100% saturation. The pattern operators see: rising p95, then a wall of 504s, then pg: too many connections for role, then full-CPU saturation where even the formerly fast queries time out. Where the breakage actually lives: five database failure modes Most of the work sits in the database, not the runtime. The five recurring failure modes in roughly the order they hurt: 1. RLS policies with no supporting index. Supabase's own RLS docs show a policy-column index taking a benchmark from 171ms to less than 0.1ms. It's the cheapest win in the entire stack. 2. Stable functions called per row. auth.uid() is stable but Postgres calls it per row unless you wrap it: using ((select auth.uid()) = user_id) lets the planner run it once per query as an initPlan. Supabase documents this as an RLS performance recommendation; its benchmark drops from 179ms to 9ms after wrapping auth.uid(). In our rescues, that is often a double-digit win on selects with limit/offset/order by. 3. N+1 from PostgREST clients. The classic Lovable pattern, fetch posts, then loop and fetch each author, turns 1,000 posts into 1,001 round trips. The fix is PostgREST's relational embedding (select=*,author:profiles(*)), which requires the foreign key to actually exist. Lovable apps frequently store IDs as plain uuid columns with no FK, defeating embed inference. **4. select('*') returning fat columns.** Lovable's generated CRUD defaults to select('*'). For tables with markdown, JSON, or image data, a 20-row list page can transfer 200KB+ per request. At 100 RPS that's 20MB/s of egress, enough to tilt the bandwidth bill on its own. 5. Pool exhaustion under serverless fan-out. A pg client configured with max: 5 looks safe in dev. Under serverless load, ten execution environments can each open their own pool of 5 → 50 concurrent connections, close to the direct-connection ceiling on Micro before PostgREST, Auth, and other services get a turn. The same pattern hits any Lovable app that uses postgres or Drizzle directly instead of going through Supavisor. Edge and function failures you won't see in dev Imagine you're a founder watching the launch from a coffee shop in Brooklyn. Your Vercel functions run in iad1 by default. Your Supabase project lives in Frankfurt because that is what someone picked during setup. Every server-side Supabase call now travels Brooklyn → Virginia → Frankfurt → Virginia → Brooklyn. We've seen this exact class of misconfiguration turn a sub-250ms direct client call into multi-second server-side latency. The fix is one dropdown, but only if you measure it before launch. Then there's the function-multiplication problem. Vercel bundles Next.js and SvelteKit dynamic code into the fewest functions it can, so "thirty Next.js routes equals thirty functions" is not the rule. Direct api/ files and some non-framework deployments do map one-to-one, though, and that is where small exported apps accidentally create a large cold-start surface. Concurrency adds a second layer. Vercel Functions can auto-scale up to 30,000 concurrency on Hobby and Pro, with burst behavior that ramps during traffic surges. Fluid Compute can run multiple invocations inside the same instance, which helps I/O-heavy work. It does not fix your own sequential code: a server action doing four Supabase calls in series still waits for call one, then call two, then call three, then call four. Finally, rate limits. Most Lovable apps ship with no rate-limit middleware, and PostgREST itself has no built-in rate limiter, it's still tracked as an open issue. The first abusive client, or one accidental infinite loop on the frontend, is enough to consume the database/API capacity you thought was reserved for real users. The cost curve nobody saw coming Failures that don't show up as latency show up on a Stripe charge. A useEffect-driven dashboard can rack up four to six function invocations or Supabase API calls per page view: auth check, dashboard data, preferences, notifications. Invocation pricing alone is rarely the scary part, and Vercel's Active CPU meter excludes time spent waiting on database I/O. The cost risk is the combination: more invocations, provisioned memory while requests are in flight, repeated uncached reads, and transfer from oversized payloads. Bandwidth follows the same shape. select('*') returning 20 rows at 50KB each = 1MB per dashboard load. 100,000 page loads = 100GB. Past the 1TB included Pro tier, that's $0.15/GB; a single launch spike on a media-heavy table has produced four-figure overages on the Vercel forums. The most expensive mistake is the panic fix. When pool exhaustion hits, the easy lever is upgrading Supabase compute. Micro is roughly $10/month; 4XL is now roughly $960/month. Each step raises the connection and resource ceiling, but it does nothing for the underlying RLS sequential scan. We've watched founders pay the larger bill before someone added the index that let them drop back to a smaller tier. The fixes: ten targeted changes, before and after None of these require rewriting the app. They are small, boring, and they compose. Here is one anonymized appssemble rescue, measured on a Supabase Micro project with a dashboard route returning 20 tasks. The k6 run used a 50-VU steady-state profile with 1-4 seconds of think time and a dashboard mix of list, task, notification, and auth reads. The "after" run included an index on user_id, an RLS rewrite to (select auth.uid()), explicit column lists, pagination, PostgREST embedding for the join, and a server route that collapsed four client fetches into one parallel backend call. MetricBeforeAfterp50 latency240 ms38 msp95 latency1,850 ms92 msp99 latency5,400 ms (with 504s)180 msError rate at 50 VU6.4 %0.0 %Cliff RPS (where p95 doubles)~30 RPS~220 RPSPostgres CPU at 50 VU96 %11 % One afternoon. No rewrite. No compute upgrade. The full ten-fix list, in the order we apply them: Add the indexes RLS implies. For every policy referencing column = auth.uid(), add create index … on table (column). Single biggest p95 win in most rescues, 10-100x. Wrap auth functions in RLS policies. Rewrite auth.uid() = user_id to (select auth.uid()) = user_id so Postgres calls the function once per query, not once per row. **Replace select('*') with explicit column lists.** Cuts payload and parsing time. Often shrinks egress 5-10x. **Add range() pagination everywhere there is a list.** Default page size 20-50. Replace N+1 client-side joins with PostgREST embedding. Add the missing foreign keys first, then use select=*,author:profiles(*). Push fan-out fetches to a single server route where the runtime supports it. Replace four client-side useEffect calls with one server endpoint returning all four payloads in a parallel Promise.all. Saves three round trips and gives you one place to cache, rate-limit, and observe the dashboard load. Pin the Vercel project region to the Supabase region. One dropdown, single biggest p95 win on misconfigured projects. Move from direct Postgres connections to Supavisor transaction mode. Connection-string change only. Caps connection growth under Vercel concurrency. Add edge cache headers. Public list endpoints with Cache-Control: public, s-maxage=60, stale-while-revalidate=300 will absorb most of a Hacker News spike before it ever reaches Postgres. Re-run the same k6 script. This is the payoff: the before/after table you can put in front of investors. "But our app is small, do we really need this?" Two objections we hear, both worth answering directly. "We don't have launch-spike traffic yet." Profile 2 in our load plan is 50 VUs steady-state for five minutes. With a 1-4 second think time and the endpoint mix above, that is enough to surface the class of failures that later shows up as "normal Tuesday" traffic. Our target for this dashboard class is p95 < 300ms, p99 < 800ms, and error rate < 1%. You don't need Hacker News to hit the wall. "We'll fix it when we hit scale." This is the panic-fix path: compute upgrades that don't address the underlying problem, four-figure egress bills from a single bad launch, and an RLS schema that gets harder to fix the more data you have. The repair costs less in week one than in month six. Stop upgrading compute until the query plan is clean. Why we trust this pattern We run Grovs, our open-source attribution and deep-linking infrastructure, at 10M+ events per day. Grovs is not a Lovable + Vercel clone; it runs on high-volume Postgres-backed attribution infrastructure with Redis, Rails, native SDKs, and an EU-hosted cloud setup. That is exactly why the lesson transfers. The architecture for "ten users" and "ten million events" starts diverging the moment you decide whether indexes, pagination, rate limits, and cache boundaries exist. If your Lovable export is live and untested, run a k6 script against it this week. The 100-line script in the appendix of any k6 tutorial is enough to surface the four failure modes above inside the first ninety seconds. If the numbers come back ugly, the fixes are usually closer to indexes, pagination, cache headers, and region pinning than a full rebuild. If you'd rather we run the test and ship the fixes, our engineering team does this almost every week. Book a call. Move fast. Stay small. Build big, but only after the load test passes. --- ### No-code vs vibe-code: pick the ceiling above your needs URL: https://appssemble.com/blog/no-code-low-code-vibe-code How founders should choose no-code, low-code, or vibe-code by ceiling, exit path, and next milestone Demos run on one record. Production runs on 100,000. That is the founder mistake behind most no-code, low-code, and vibe-code decisions. You do not fail because Bubble, Retool, Webflow, Lovable, or Bolt is bad. You fail because the ceiling you picked sits either far above what you need next month or just below what traction will demand. The right tool is one rung above your honest projection, not five rungs above your fantasy roadmap. A SaaS MVP tool should help you validate the next 1,000 users, not model the architecture you hope to need after Series B. The two expensive mistakes sit on opposite sides The first mistake is picking a ceiling far above your needs. You build a 200-user internal ops tool in Next.js when Retool would have shipped it in a week, or you build a marketing site in custom React when Webflow would have let the marketing team own it by Friday. The tool works, but slowly and expensively. You pay with time, scope, meetings, and delayed customer learning. The second mistake is worse: picking a ceiling just below your needs. You build a customer-facing SaaS in Bubble, a portal on Airtable plus Zapier, or a mobile app in Glide, then traction starts and the platform wall arrives at the exact moment you need to move faster. That wall is not theoretical. Airtable's API limit is 5 requests per second per base, Glide is capped by spreadsheet-app assumptions and ships PWAs rather than App Store apps, and Bubble does not give you source-code export when you outgrow it. No-code is strongest when the artifact is simple No-code works when the product surface matches the platform's native shape. Webflow is excellent for marketing sites, content pages, and CMS-owned pages where the marketing team should not wait on engineering for every change. For most founder-led teams, Webflow's default ceiling is the website in front of the product, not the product itself. If you are deliberately using Webflow Cloud with engineers, that is a different stack decision. If you are using the visual CMS path, do not put your SaaS dashboard there. Bubble has a higher SaaS-MVP ceiling, but it comes with two catches founders underprice. The first is performance risk: third-party research cited in the planning dossier reports 5-10 second desktop loads and 8-14 second mobile loads for complex Bubble apps. That is not a universal benchmark, but it is enough to treat performance as something you test before traction. The second is exit: Bubble lets you export data, not a normal application codebase, so migration means rebuilding the application logic. Glide is even clearer. If your real brief is "I have a spreadsheet and need a UI," Glide can be the fastest path. If your brief includes App Store distribution, native mobile behavior, or a product your users will live in daily, you are asking the wrong tool to do the job. Glide ships PWAs, and that ceiling should be visible in the first planning conversation. Low-code has a real ceiling, and it is usually internal Low-code is not fake engineering. It is engineering compressed into a visual workflow, with real power and real limits. Retool is a good answer for admin panels, customer support consoles, finance reconciliation screens, and internal workflows your engineering team would otherwise ignore for three quarters. It becomes a bad answer when the internal tool turns into the product, or when seat-based pricing becomes the architecture. A 50-builder Retool Business setup costs about $30,000 per year before workflow overages, AI usage, or self-hosted infrastructure. A mixed team is cheaper, but the pricing still scales with every person who builds or uses the tool. At that point, you should compare Retool against a coded internal tool instead of pretending seat pricing is free. Airtable plus Zapier is similar. For 200 operations a day inside an ops team, Airtable's 5 requests per second per-base API limit is fine. For a customer-facing flow where one signup fans out into several Airtable and Zapier reads and writes, 100 users arriving at once becomes a queue, not a product experience. Vibe-code wins when exit matters Vibe-code is no-code that ships actual code. Lovable, Bolt, and v0 give you the prompt-first building experience, but the output is closer to a repo an engineer can eventually own. That difference matters more than the demo. A founder who builds in Lovable and outgrows it can bring an engineer into a GitHub repo, inspect the React code, export or clone the project, replace the weak parts, and keep moving. A founder who builds in Bubble and outgrows it brings an engineer a Bubble app and a data export plan. This does not mean vibe-code is production engineering by default. Lovable apps can validate demand quickly, but once money, identity, permissions, background jobs, or compliance enter the product, the generated code needs a real hardening pass. Our practical warning zone is the 1,000-10,000 user range, where fragile auth, RLS, query patterns, and async flows start showing up in support tickets. That is still a better failure mode than a locked-in rebuild. If the code is messy but portable, a senior engineer can refactor it. If the logic lives only inside a vendor runtime, the migration clock starts from zero. Imagine you are choosing for the next 90 days Imagine you are a pre-seed founder building a B2B workflow product. You need auth, Stripe, email, five CRUD screens, and one integration with a vendor API. You have no engineer yet, no organic search strategy, and your target is 200 beta users in the next 90 days. Bubble can get you there. Lovable or Bolt can also get you there. The difference is what happens on day 180, when the beta works and you hire your first engineer. If you picked vibe-code, the engineer inherits code. They may complain about the structure, replace the auth layer, tighten Supabase policies, and rewrite a few async flows, but they are still working inside normal software. If you picked Bubble, that engineer is planning a full rebuild while customers are already asking for features. Now change the scenario. You are a 70-person services company and need an internal approval dashboard for 40 employees. Retool is probably the right ceiling, because the artifact is internal, the user count is bounded, and the cost of building a bespoke app is the waste. The decision tree is shorter than founders think Start with the artifact. A marketing site belongs in Webflow or Framer for most companies. An internal tool for 5-500 employees belongs in Retool, or Airtable plus Softr if it is mostly tabular. ArtifactDefault toolHard stopExit pathMarketing siteWebflow or FramerProduct logic, logged-in dashboards, complex app stateKeep the CMS, build the app separatelyInternal toolRetoolThe tool becomes customer-facing, or every new user adds material costPort the queries and workflows into codeSpreadsheet appGlide or Airtable plus SoftrApp Store distribution, high write volume, non-tabular dataExport data, rebuild the product surfacePre-PMF SaaSLovable or BoltMoney, auth, permissions, jobs, or compliance become seriousKeep the repo, harden the fragile pathsPaid SaaSProduction codeThere is no disposable version anymoreRefactor deliberately, not after an outage A customer-facing SaaS that charges money and onboards users every week should not start in a platform with no code portability. Vibe-code is the safer pre-PMF default if you are not ready for a coded MVP, because the exit ramp is cleaner. Then ask how long this exact product needs to live. A 1-6 month pilot can live in almost anything if you are honest that it may be thrown away. A 12+ month product with engineers coming later should bias toward code portability. Next, check the custom logic. Stripe, auth, email, and basic CRUD are boring enough for most tools. Real-time collaboration, custom Stripe Connect flows, multi-tenant permissions, background jobs, vector search, or third-party SDKs without native plugins are signs that no-code is already too low. Finally, check the user count before your next funding or hiring milestone. Under 1,000 users, stop optimizing. From 1,000 to 10,000 users, vibe-code can keep working if the fragile pieces are replaced. Above 10,000 users, treat production code as the default, not a nice-to-have. These are appssemble operating thresholds, not vendor limits. These are the briefs we would push back on We would not build a consumer SaaS in Bubble and "migrate later." The migration is the hidden project, and it usually arrives when growth starts. We would not build a customer-facing app on Airtable plus Softr unless you can commit to a small active-user ceiling. The 5 requests per second limit is not a tuning detail. We would not use the normal Webflow visual CMS path for a SaaS dashboard. Webflow should own the marketing surface, while the dashboard belongs in code or in a code-exporting builder that can graduate. If you are using Webflow Cloud with engineers, judge it like an engineering stack, not like a no-code site builder. We would not promise a Glide app can become your App Store product. Glide is a PWA tool, and that should be visible in the first planning conversation. We would not ship the product in Retool because your team already uses Retool internally. Retool is for the tools behind the product, not the product your customers buy. Pick the ceiling, then plan the exit The best stack decision is boring: choose the tool where the next milestone is easy and the next exit is visible. Too much ceiling slows you down. Too little ceiling turns traction into a rebuild. For most founders, the pattern is simple. Use Webflow for the marketing site, Retool for internal tools, vibe-code for fast SaaS validation, and production engineering when the product has users, money, or complexity worth protecting. This is where appssemble's engineering team usually enters the story. If you already shipped in Bubble, Lovable, Bolt, Airtable, or Retool and hit the wall, we audit the ceiling, map the migration, and decide what to keep, refactor, or rebuild. If you have already crossed the line and need a clear path out, book a call. We will look at the product, the current tool, the user count, and the next 90 days before recommending a rebuild. --- ### When a Founder Hands You a Lovable Repo: The 12-Check Audit That Decides Rescue vs. Rebuild URL: https://appssemble.com/blog/lovable-launch-audit-12-checks A practical 12-check audit for deciding whether a Lovable app is safe to rescue or needs a rebuild. A founder forwards a Lovable repo on Monday morning. They have users, a Stripe account, a Supabase project, and one urgent question: should we rescue this codebase or rebuild it before the next launch? We do not start with code style. We do not start with folder structure. A serious vibe-coded app security audit starts with the things that can leak data, grant free subscriptions, or make the database impossible to save. The order is the opinion. Lovable is useful for getting a product into users' hands, but a Lovable security checklist for production has to triage like production engineering, not like a prettier lint pass. Lovable has added security scanners for common mistakes, and that helps. Its own docs still make the important point: automated checks support secure development; they do not replace a real security review when the app handles sensitive data or critical flows. Why audit order decides the rescue vs. rebuild call The first 2 hours matter because every check either stops active damage, gates the rebuild decision, or buys the founder credible runway. NVD lists CVE-2025-48757 as supplier-disputed, but the failure mode is still the first thing we audit: Lovable-generated apps relying on direct browser-to-Supabase requests where RLS has to carry the security model. Matt Palmer's statement put the scan at 303 endpoints across 170 projects, about 10.3% of 1,645 analyzed; Semafor separately reported that Palmer and Kody Low's deeper analysis turned up 170 vulnerable Lovable sites. That is why we check secrets, Supabase RLS, and auth before anything else. Supabase is clear that anon and publishable keys can live in public clients, while service_role and secret keys bypass RLS and must not be exposed. If your elevated key is in the browser bundle or a public table has RLS off, the next step is not "technical debt grooming." The next step is rotate keys, patch policies, and stop shipping features until the blast radius is understood. Imagine you're a technical founder two days before sending a demo link to an enterprise buyer. The UI looks finished, but a logged-out request to /rest/v1/users?select=* returns customer rows. That is not a refactor ticket. That is the audit taking control of the roadmap. What do we check in 5, 30, and 120 minutes? We split the audit into 3 gates: a 5-minute smell test, a 30-minute security triage, and a 120-minute keep-or-burn pass. Anything beyond that is no longer an audit. It is the rebuild estimate. In the first 5 minutes, we run a secrets scan, open package.json, look at the largest files, and read the README. In the next 30 minutes, we inspect Supabase policies, auth paths, and Stripe webhooks. In the final 120 minutes, we walk schema, transactions, validation, dependency graph, observability, and platform lock-in. The point is not to find every defect. The point is to find the defect that changes the recommendation from "patch this week" to "rebuild the foundation before you add one more customer." The first 3 checks stop active bleeding 1. Secrets in the client bundle: We run gitleaks detect, search history for sk-, and inspect public environment variables such as VITE_ and NEXT_PUBLIC_. SupaExplorer's 20,052-URL scan reported 2,325 critical Supabase exposures across vibe-coded apps. The useful distinction is not "Supabase key equals leak." The useful distinction is anon keys are expected in clients; service_role keys are not. In @tgoldi's 50-app Lovable spot check, 34% exposed a service_role key in client code. This comes first because a leaked service_role key bypasses RLS entirely. If it is exposed, the order is simple: rotate keys, invalidate sessions where needed, review logs, then continue. 2. Row-Level Security on every public table: We check for public tables with RLS disabled and policies that resolve to USING (true). The same @tgoldi 50-app spot check reported that 89% of deployed Lovable apps had at least one table with RLS off entirely. RLS is the last line of defense when frontend auth, direct browser queries, or leaked anon keys fail. If it is missing, you do not have a production Supabase setup. You have a public database with a nicer UI. **3. Auth logic and direct auth.users access:** We look for client-side "authenticated" flags, protected pages that render before redirect, no rate limiting, and direct queries against auth.users instead of a profiles table. The Register reported that Taimur Khan found 16 vulnerabilities in a Lovable-hosted edtech app, including inverted auth logic that exposed 18,697 user records and 4,538 student accounts. Auth bugs are dangerous because they turn anonymous traffic into authenticated traffic. Once that happens, every weak RLS policy becomes reachable. Payments come before architecture arguments 4. Stripe webhook signature verification: We grep for constructEvent, stripe.webhooks, and STRIPE_WEBHOOK_SECRET. Stripe expects signature verification with the raw request body, the Stripe-Signature header, and the endpoint secret. If the handler trusts raw JSON, anyone who knows the endpoint can fake checkout.session.completed and grant themselves a paid plan. This is usually a 10-minute finding with a serious business impact. It does not matter whether the app uses the right component library if the paid tier can be spoofed with a POST request. 5. Idempotency on side-effecting webhooks: We look for a webhook_events or processed_events table keyed on Stripe event.id, plus a unique constraint. Stripe can redeliver the same webhook event for up to 3 days, and its docs tell you to log processed event IDs before acting. If the handler does not do that, retries can duplicate entitlement changes, emails, local records, and any non-idempotent outbound Stripe POST calls. The duplicate-charge risk appears when your app creates or mutates Stripe objects again without idempotency keys, not because Stripe redelivered the original event. That is why payment idempotency sits before schema elegance. Money paths fail loudly and quickly. Schema is the keep-or-burn gate 6. Schema sanity: This is where we decide whether rescue is real. We count foreign keys, inspect naming drift, look for JSON blobs where relations should exist, check missing indexes, and compare soft-delete patterns across tables. Inigra's single-codebase audit found more than 600,000 lines of AI-generated code, 100+ database tables, 100+ serverless functions, 500+ database migrations, and only 2 test files. It also found functions over 3,000 and 1,500 lines. At that point, "clean up the repo" is not a plan. The schema tells us whether the app has a core model or just accumulated prompts. If user_id, userId, and userid all exist in the same product, every future feature inherits that confusion. Operational checks tell us whether rescue is real 7. Transactions on multi-step writes: We search for BEGIN, supabase.rpc, and transaction wrappers around onboarding, order creation, and subscription activation. A signup flow that inserts into users, then profiles, then subscriptions without rollback creates ghost accounts on the first network failure. If the critical path cannot move into one RPC, one transaction, or one server-side unit before launch, we price that as stabilization, not cleanup. 8. Server-side input validation: We check for Zod or Valibot schemas on routes, edge functions, and RPC calls. Client-side validation is useful for UX, but production security lives on the server. If schemas exist only in React form components, the API is trusting the browser, and the browser is the least trustworthy part of the stack. 9. Dependency graph and dead code: We run tools such as knip, madge, and npm audit --production to see whether the codebase can be moved without excavation. Our smell-test threshold is simple: 80 to 120 dependencies is a typical Lovable handoff, 150+ dependencies slows every migration, and knip reporting more than 25% unused exports means the repo has structural rot, not clutter. 10. Error boundaries and observability: We count error boundaries, inspect try/catch blocks, and look for Sentry, PostHog, structured logs, or anything that tells you what broke in production. A React app with 50 useEffect calls for every error boundary is not ready for real traffic; it is ready to surprise you at 2 a.m. If this cluster fails, the app might still be rescuable, but the founder should stop calling it a launch checklist and start calling it a stabilization sprint. These checks do not always force a rebuild. They tell us the cost of keeping the current codebase alive while we stabilize it through engineering and Growth & Scale work. The last 2 checks predict the next 6 months 11. The smell test: We look at largest files, README quality, dependency count, commit history, and test count. Our thresholds are plain: under 500 lines for the largest file is healthy, 800 to 1,500 is typical for a Lovable handoff, and 3,000+ is a burn-it signal. A useful README explains setup, environment variables, and scripts. An empty README, one commit, 150+ dependencies, and zero tests do not prove the product is doomed. They do prove that every handoff will be slower than the founder expects. 12. Vendor lock-in: We search for Lovable-specific cloud paths, hidden AI gateways, and platform-hosted functions that cannot be moved without rewriting the feature. The same Inigra audit describes a codebase with 30+ AI serverless functions routed through a proprietary gateway and zero direct OpenAI or Anthropic API calls. That changes the commercial recommendation. If the AI logic is outside the repo, we usually budget 2 to 4 extra weeks just to extract prompts, provider calls, and failure handling into code you own. What should you hear after hour 2? At the end of 2 hours, we do not hand you a 90-page PDF. We give you one of 3 answers: green means patch now and keep shipping, amber means stabilize for a short migration window, and red means rebuild the core before the product earns more traffic. The horror stories explain why we keep the answer that blunt. Semafor reported that Danial Asaria said he found personal debt amounts, home addresses, API keys, and prompts in 47 minutes. The Register later reported a separate BOLA flaw where a researcher said another user's profile, projects, source code, and database credentials were reachable in as few as 5 API calls from a free account, after a report filed 48 days earlier. Lovable is right for launch. It is not a substitute for production ownership. At appssemble, we use this checklist in this order. If your next launch depends on a repo you do not trust, book a call and we will give you the keep-or-burn read before you spend another sprint. --- ### Why the Cheap Model Wins When Your App Needs to Classify URL: https://appssemble.com/blog/classification-extraction-routing Small-model routing patterns for faster, cheaper AI classification Most Lovable apps make the same mistake the first time they add AI classification: they call the strongest frontier model for a job that returns one label. The user waits on the model, the bill grows with every ticket, and the product still needs validation code because the model might answer in prose instead of structured JSON output. Classification, extraction, and routing are not frontier-model problems. They are output-bounded tasks, which means the answer is short, typed, and easy to evaluate. If your app needs to classify a support ticket, extract invoice fields, or route a request to the right handler, a small fast model plus caching usually beats the expensive path. This is where production AI starts to look less glamorous and more useful. The win is not "use AI everywhere." The win is proving whether a 1.2-second interaction can move toward a few hundred milliseconds, cutting a 10,000-ticket GPT-4o-mini workload from $76.50/month to below $30 in model spend, and knowing exactly when no LLM should run at all. The three workloads show up in almost every AI feature Classification turns text into a label from a fixed set. Think billing, bug, feature, auth, or other for a support ticket. The output is tiny, which makes LLM classification cost mostly a function of input size, prompt design, and how often you call the model. Extraction turns messy input into a typed object. In an invoicing product like Incasez, where the flow goes from draft to e-Factura in under 30 seconds, the useful AI job is not writing a paragraph about an invoice. It is extracting supplier, buyer, VAT, totals, due dates, and line items into fields your system can validate. Routing decides what happens next. A request might go to a cheap model, an expensive model, a human, a deterministic parser, or a background queue. Done well, routing is the layer that stops your app from paying frontier prices for every easy decision. Frontier models are the wrong default for short answers Frontier models are valuable when the output is long, reasoning-heavy, or ambiguous. They are wasteful when your app needs one enum and a confidence score. If your expected answer is { "priority": "urgent" }, you do not need the same model you would use for multi-step legal analysis. The May 2026 pricing snapshot should be treated as a deploy-time checklist, not a permanent truth. At the time of writing, the cheap candidates worth checking first looked like this: ModelInput / 1MCached input / 1MOutput / 1MWhy it mattersGPT-5 nano$0.05$0.005$0.40Cheapest current OpenAI candidate for simple classification, with structured outputs support.GPT-4o-mini$0.15$0.075$0.60Still a strong small-model default with strict structured outputs and Batch support.Claude Haiku 4.5$1.00$0.10 cache reads$5.00More expensive raw tokens, but prompt caching can matter for long shared taxonomies.Gemini 2.5 Flash-Lite$0.10$0.01$0.40Google's current low-cost stable path, with lower Batch pricing for async work. Those numbers will change. The shape usually does not: short outputs reward small models, cached prompts, and batching. At appssemble, the practical rule we use in our AI work is simple. Start with the cheapest model that passes your eval set, then promote only the cases that fail. You do not save money by picking a worse model; you save money by making the model compete on your real labels before it touches production traffic. GPT-4o-mini wins often, but prompt caching can flip the answer GPT-5 nano now belongs in the first eval run for one-label jobs because the raw price is lower. GPT-4o-mini is still a strong default for classification and extraction because it is cheap, fast enough for many product flows, and has a mature strict-structured-output path. For a simple taxonomy under 1,000 tokens, we would usually test both before promoting anything larger. Claude Haiku becomes more interesting when the prompt has a long shared prefix: taxonomy, schema, examples, policy notes, and edge cases. Anthropic prompt caching can cut cached input reads to 10% of the normal input price, turning a stable 4,000-token instruction block from a repeated tax into a shared asset. On workloads where most of the spend is reusable prompt text, that is how an RCA pipeline can move from $720/month toward $72/month after cache markers. Imagine you are running a Lovable + Supabase support dashboard with five ticket categories and 10,000 tickets a day. A naive GPT-4o-mini synchronous setup at 500 input tokens and 300 output tokens lands around $76.50/month: 150M input tokens at $0.15/M plus 90M output tokens at $0.60/M. Batch the work and the model bill drops to about $38.25/month; add a 25% exact or semantic-cache hit rate, and the model portion falls below $30/month before embedding and cache infrastructure. Latency is usually the bill your users notice first Token pricing is visible in your provider dashboard. Latency is visible in your product. In our research notes, a Supabase Edge Function calling OpenAI or Anthropic for a 200-token input and 50-token output lands around 1.0 to 1.5 seconds p50 once you include first token, generation, and the network leg. Treat that as a benchmark to rerun in your own region, not as a provider guarantee. That is fine for a background task. It is not fine when the user is staring at a modal that says "classifying." For latency-critical routing, Groq Llama 3.1 8B is worth testing because Groq lists high token throughput and JSON object mode. Cerebras is also worth testing for speed, but do not anchor a new production path to llama3.1-8b without checking the replacement model, because Cerebras lists that model for deprecation on May 27, 2026. The serverless tax still matters. Supabase documents that Edge Function cold starts are possible, and our own AI-function measurements have seen cold invocation overhead land in the low hundreds of milliseconds depending on bundle size and region. If your target is sub-500ms p95, you need a cache hit, a fast model path, or a design that does not block the user. Structured outputs are the difference between a feature and a cleanup job Classification and extraction only help if your code can trust the output shape. "Looks like JSON" is not enough. Your app needs an enum, a number, a required field, and a rejected response when the model violates the contract. OpenAI strict JSON Schema is the lowest-friction path when you use GPT-5 nano or GPT-4o-mini. In TypeScript, the Vercel AI SDK generateObject pattern with Zod gives you provider-aware object generation and validation that fits naturally inside Supabase Edge Functions. Instructor and BAML are good options when you need Pydantic-first or schema-first workflows across providers. The key is to treat structured JSON output as part of the product contract, not as prompt decoration. A category field should only contain known categories. A confidence score should be bounded. A missing invoice total should fail validation before it reaches billing logic. Sometimes the cheapest model is no model The fastest classifier is a rule that never calls an API. Email addresses, phone numbers, URLs, hashtags, file extensions, duplicate checks, and obvious profanity do not need an LLM. Regex, keyword rules, MinHash, BM25, and lightweight local models are boring because they work. The production pattern is regex for the easy 80%, model for the ambiguous 20%. PII redaction is the clean example: catch emails, phone numbers, card-like strings, and IDs with deterministic checks first, then send only uncertain leftovers to the model. You get lower cost, lower latency, and a more auditable system. Before adding an LLM, write 20 real inputs and expected outputs. If 18 of them can be handled with rules, ship the rules and reserve the model for the last two. That is not anti-AI. That is how small-model production AI stays cheap enough to survive real usage. The architecture is cache first, model second The reference shape we would ship in a Lovable app is straightforward: client to Supabase Edge Function, exact cache lookup, deterministic gate, semantic cache for high-repetition natural-language inputs, fast model call, Zod or strict-schema validation, then write the result back to cache. The model is not the first line of defense. It is the fallback after cheaper paths have had their shot. For latency-critical classification, we would test Groq Llama 3.1 8B first and keep the model-deprecation page in the deployment checklist for any Cerebras path. For ordinary extraction and routing, we would test GPT-5 nano and GPT-4o-mini with strict structured outputs. For taxonomy-heavy workloads with long shared instructions, we would test Haiku with prompt caching and compare total cost on your traffic shape. The last piece is evals. A 50-example labeled set is enough to compare three models on your real data, catch taxonomy drift, and alert you when accuracy drops for two days running. The cheaper the model, the more the eval set matters, because you are buying cost savings with discipline. Cheap classification only works when you measure it The wrong lesson is "always use the cheapest model." The right lesson is that classification, extraction, and routing are measurable tasks. When the output is short and structured, you can compare models, cache aggressively, batch non-urgent work, and keep frontier calls for the cases that earn them. That is how you turn AI from a demo into a production feature inside a Lovable + Supabase app. Not by paying 10x for every request, but by building the small path first and proving where the expensive path is needed. Before you replace the model call, build a 50-example eval set and run the cheap path against real tickets. If the cheap path passes and the measured p95 stays under your UI budget, ship it. If it fails, route only the failing cases to the expensive model. If your classification is already costing you money or users are waiting on every model call, book a call and we can help you redraw the path. Built by developers. Accelerated by AI. --- ### Why most Lovable apps stall before 1,000 paying users URL: https://appssemble.com/blog/why-90-percent-lovable-apps-fail Why Lovable prototypes need security, architecture, and distribution work before they can scale. Lovable does not publish a distribution of how many apps built on the platform reach 1,000 paying users. That matters, because the public platform math is easy to misuse. TechCrunch reported that Lovable claimed 25M+ projects in its first year and more than 100,000 new projects per day. In July 2025, TechCrunch also reported 2.3M active users and 180,000 paying subscribers. Those numbers prove Lovable's adoption. They do not prove that the apps built on top of it inherit the same funnel. Our read is an inference, not a Lovable disclosure: most Lovable-built products stall well before 1,000 paying users because they hit the same walls as every small SaaS product, plus a few Lovable-specific ones. The Lovable code is not the asset. The validated workflow is. The math looks great until you read it twice Lovable's public ARR ramp is unusually steep. It crossed $100M ARR by July 2025, more than $200M by late 2025, and Lovable confirmed to TechCrunch that it crossed $400M ARR in February 2026. That is Lovable's business. It is not proof that your app's funnel will work. The 7.8% paid conversion at the platform level reflects a captive audience of builders who already chose to spend money to ship faster. Apps shipped on top of Lovable face a harder market: strangers, distribution, retention, support, procurement, and a stack the founder usually cannot debug. SaaS benchmark data points in the same direction, but they are context, not proof. A $1K MRR benchmark is not the same thing as 1,000 paying users. The honest claim is narrower and stronger: Lovable gets you to the start of the gauntlet faster. It does not remove the gauntlet. If your app needs users to trust it with money, private data, or a workflow they run every week, the prototype has to become software. Security is the debt that scales faster than revenue The fastest way to lose your first 1,000 paying users is to expose the data of your first 100. The Lovable-specific security record is serious enough without exaggeration. In the audited Lovable Launched set, Matt Palmer reported 303 vulnerable endpoints across 170 projects, about 10.3% of 1,645 analyzed, with inadequate Row Level Security on Supabase. NVD/MITRE lists CVE-2025-48757 as supplier-disputed, because Lovable argues app owners are responsible for protecting their own data. In a separate 50-app spot check, Tomer Goldi reported that 89% had no RLS and 34% exposed a service-role key in client code. Treat that as a self-published spot check, not a population-wide rate. Lovable has also moved. Its current docs describe a Security view, a workspace Security center, RLS analysis, database checks, code review, dependency audits, secret handling, and a May 2026 Wiz integration. The same security overview still says automated scanners do not replace a thorough security review for apps handling sensitive data or critical functionality. That is the honest boundary. The April 2026 platform incident belongs in that same category: serious, but not unlimited. Lovable's own response says public-project chat history and source code could potentially be accessed by any Lovable user with a project link between February 3 and April 20, 2026. Private projects and Lovable Cloud were not impacted, according to Lovable. Separate reporting alleged broader exposure, so we would not treat the credential and customer-data claims as Lovable-confirmed. The broader vibe-coding ecosystem shows the same pattern. Moltbook exposed authentication tokens and emails after a Supabase/RLS failure. Base44 had a platform-wide auth bypass that Wix said it fixed within 24 hours, with no evidence of past abuse. These are not Lovable examples. They are evidence that "AI made a working app" is not the same as "a security boundary exists." Imagine you're a solo founder six months in, 800 trial signups, and an email arrives from a security researcher with screenshots of your customer table. You did not write the code. You cannot read most of it. Your remediation budget is whatever you have left after burning credits on the bug that brought you here. That is where the first wall comes down. The bug-loop credit cliff is where runway evaporates The second wall is financial, and the sources here are weaker by nature. Trustpilot reviews, Reddit posts, and feedback threads are anecdotes, not market data. They still describe a failure mode founders recognize immediately: the agent fixes one bug, introduces another, and charges you for both. DesignRevision's analysis of 200+ public discussions and reviews reported that 65-75% of complex Lovable builds mention bug loops, 60% of negative reviews cite credit costs, and 40% mention code-quality decay. Treat that as sentiment analysis, not a formal survey. It matches the founder pain we see: the last 20% is where prompting turns into paid debugging. The current pricing is different from the older "$100/mo Launch" summaries floating around. Lovable's docs list Pro from $25/month for 100 monthly credits, with larger tiers and top-ups available. Lovable Cloud and AI are usage-based and separate from workspace message credits. Supabase Pro starts at $25/month if you run Supabase separately. That does not make the bill fake. It makes it variable. A founder can start cheaply and still end up at $100-$300/month once paid credits, hosting, Supabase, email, auth, monitoring, and debugging time enter the picture. The danger is not the subscription line item. The danger is paying to keep a codebase alive when you still do not know whether the market wants it. Architecture has to survive the third feature The third wall is structural. DesignRevision's project-type satisfaction gradient is useful because it tracks complexity: high for landing pages and prototypes, lower for SaaS with payments, complex workflows, and multi-user products. Again, that is sentiment analysis. The mechanism is still familiar to anyone who has inherited generated code. Vibe-coded code is generated to satisfy a prompt, not to live inside a system. Data structures get inflexible, logic gets braided across files, and what feels like a small feature tweak means rewriting chunks of autogenerated code. Asynchronous flows such as login, file uploads, and payment webhooks break in ways the agent cannot reliably diagnose because the abstraction handled timing in three different patterns across three different sessions. This is where rebuild absolutism gets founders into trouble. A rebuild is not a moral victory. It is only justified when the generated foundation is now slower to fix than to replace. Distribution is the wall coding speed cannot climb Even with secure code, controlled costs, and a working architecture, the fourth wall stands. Shipping is not distribution. Getting 1,000 strangers to pay you for software requires a wedge into a real audience. Look at the rare wins and the pattern is not "Lovable magic." Plinq, a women's safety platform built by Sabrine Matos, is a Lovable case study with $456K ARR and 10,000+ users in three months; Matos was already a senior growth marketer. AppDirect's Lovable case study involved 11 internal projects and $120K in savings; useful, but internal tooling is not the same as an external paying-user funnel. Pieter Levels' fly.pieter.com and other broader vibe-coded wins are even cleaner as distribution examples because they were not Lovable apps: the founder's audience did the heavy lifting. The pattern across winners is the founder, not the platform. Existing audience. Sharp pre-existing wedge. Manual engineering past the prototype stage. The tool is incidental. Stop prompting when the app becomes load-bearing We do not think Lovable is useless. It is a strong prototyping surface for landing pages, internal tools, and validating a workflow before you spend on engineering. The mistake is treating the prototype as the product, then trying to bolt on security, payments, and scale through more prompts. Stop prompting and audit when the app stores PII, processes payments, has more than one tenant, includes staff/admin actions, is part of a B2B sales process, handles regulated data, or powers a support process you cannot debug. If none of those are true, keep using Lovable and spend engineering money after the next traction milestone. If two or more are true, you are past the demo stage whether the codebase admits it or not. Our work at appssemble starts there. A small senior Engineering team audits the validated workflow, keeps the screens and flows that users already understand, then replaces the load-bearing paths: auth, RLS, payments, data model, background jobs, observability, and deploy. The point is not to punish the prototype. The point is to keep the proof and remove the parts that can break the business. Five things change when a prototype becomes a product: 1. RLS is verified, not assumed. Every Postgres table has policies before it has rows. Auth flows are tested before they touch a customer. We do not rely on the model to remember security; we encode it in the schema. 2. Costs are modeled before they sprawl. We price the migration against the next month of fixes. If auth, RLS, payments, and support workflows are already burning founder time, a selective rebuild of the load-bearing paths can be cheaper than another month of prompt loops. 3. Architecture survives the third feature. Schema, services, and tests are written to live with you for years, not to satisfy the next prompt. When a requirement changes, the change is local, not global. 4. The distribution surface gets serious. Growth & Scale plugs in analytics with first-party data through Grovs, which processes 10M+ events daily, and release control through Semaphr, which manages 500K+ app sessions. The same team that built the product stays to grow it. 5. AI is shipped as production logic. When AI is the right answer for a feature, it extracts, classifies, routes, translates, or summarizes inside a system with evals, error handling, and human escalation. Not a notebook demo. Not a mystery prompt. "But our prototype works: why rebuild?" We hear this constantly. Three honest answers. First, the prototype may work for the happy path and still fail at the boundary. The defects are usually in the parts you have not looked at: webhook idempotency, RLS, secret handling, retries, race conditions in payment flows. Lovable's current security docs make a related point: automated checks reduce risk, but they are not a full review. Second, you do not have to throw the prototype away. Most of the work we do is selective hardening. We keep the screens and the flows the founder validated, then replace the autogenerated foundation with one that can take traffic. The user-facing product can look identical on day one of the new repo. Third, the cleanup market exists because the median prototype does not clean itself up. 404 Media documented freelance developers and firms fixing vibe-coded software. HN threads treat "vibe-code remediation" as inevitable, not novel. That is not proof of a 90% Lovable-specific failure rate, but it is a signal founders should take seriously. The honest framing Lovable is a very good demo-to-working-prototype surface. The platform is not the problem. Treating the platform's output as a finished product is the problem. If your prototype is working, you have done the hardest part of starting a software business: you found something a stranger might pay for. The next part, where you keep that stranger, add a thousand more, and do not end up on a security researcher's blog, is engineering work, distribution work, and ownership work. If your Lovable prototype has real users and the foundation is starting to scare you, talk to us. We audit the validated workflow, keep what is working, and rebuild the load-bearing paths so the same team can take it from hardening through growth. Book a call. --- ### Postgres RLS Done Right: The 10 Mistakes That Exposed 170+ Apps URL: https://appssemble.com/blog/postgres-rls-done-right A practical Supabase RLS blueprint for tenant isolation, audits, and policy tests On May 29, 2025, security researcher Matt Palmer disclosed CVE-2025-48757: Lovable-generated apps could expose Supabase-backed data through missing or insufficient Row-Level Security on client-controlled database requests. Palmer's disclosure listed a CVSS v3.1 base score of 8.26. The NVD record shows MITRE's CNA score as 9.3 and marks the record disputed because Lovable argues each customer app owner shares responsibility for protecting application data. The public scale numbers come from follow-on scanner reports, not from Palmer's disclosure itself. Vibe App Scanner reports 170 affected apps and 303 vulnerable endpoints across 1,645 scanned Lovable apps. Superblocks reports exposed usernames, emails, phone numbers, payment status, subscription data, Gemini and Google Maps API keys, developer credentials, and Stripe-related override paths. The root cause was not exotic. It was Postgres Row-Level Security configured the way an LLM tends to configure it: tables created, RLS sometimes enabled, policies shaped like the documentation example, anon key treated like a security boundary. Lovable announced a "security scan" feature with Lovable 2.0 on April 24, 2025; Superblocks later reported that scanner only checked whether RLS existed. It did not prove the policies matched the product's tenant model. This post is the schema we wish those 170 founders had started with. It is opinionated, concrete, and built around a single rule: never trust a policy that you have not read, indexed, and tested. Why AI tools generate RLS that looks right and isn't RLS in Postgres is unforgiving in a specific way. A table with enable row level security and zero policies silently denies all reads, so the app appears broken. The fastest fix that makes the test pass, and the fix Cursor, Bolt, and Lovable reach for repeatedly, is using (true). Every row, every role, fully open. The migration runs, the test passes, and the anon key in the browser can now read the entire table. We have seen ten variants of this same pattern in production audits. Each one looks like a small detail. 1. RLS off entirely. The migration creates the table; enable row level security is never issued. On an exposed Supabase table with permissive grants, the anon key can read or write every row. **2. using (true) everywhere. Often copy-pasted from documentation examples that were never meant for production. 3. SELECT-only policy, no INSERT/UPDATE/DELETE.** Reads check auth.uid(), but writes fail under default-deny. The dangerous part usually comes next: someone adds a broad write policy to make the app work without testing tenant boundaries. **4. No to authenticated.** Policies default to public, which includes anon. Postgres still evaluates the policy on every anon request. **5. Authorization based on raw_user_meta_data.** This column is user-mutable through the public auth API. A user can grant themselves role = 'admin' with a single client call. **6. The service_role key in a Next.js client component. A service key exposed to the browser can bypass RLS and must be treated as compromised. 7. Public storage buckets for private files. Public buckets make reads public by URL. Writes still depend on storage policies, but the private-file boundary is already gone. 8. enable row level security with no policies.** Default-deny, app breaks, junior dev "fixes" it with using (true). We are back to mistake two. **9. No force row level security.** Background jobs and migrations often run as the table owner. The owner bypasses policies by default unless you force RLS; superusers and roles with BYPASSRLS still bypass either way. 10. Junction tables left unprotected. team_members, account_memberships, organization_users: the table that defines who can see what is itself open. Anyone can insert themselves as an owner. Read the list once and notice how mundane each item is. None of these require a sophisticated attacker. A curl command and a browser-extracted anon key are enough. The canonical schema is the actual fix For multi-tenant SaaS up to a few hundred tenants, shared-schema is the right shape. One Postgres database, an account_id column on every tenant-scoped row, RLS enforcing the partition. Schema-per-tenant becomes defensible above that scale, but it breaks Supabase's auto-generated PostgREST API and migrations get expensive fast. Here is the starter we hand to clients. Two tables for tenants and membership, two for the actual product surface. Treat it as the floor, not the ceiling. -- 1. Tenants and membership create table public.accounts ( id uuid primary key default gen_random_uuid(), name text not null, slug text unique not null, primary_owner_user_id uuid not null references auth.users(id), created_at timestamptz not null default now() ); create type public.account_role as enum ('owner', 'admin', 'member'); create table public.account_memberships ( account_id uuid not null references public.accounts(id) on delete cascade, user_id uuid not null references auth.users(id) on delete cascade, role public.account_role not null default 'member', created_at timestamptz not null default now(), primary key (account_id, user_id) ); -- 2. Tenant-scoped data create table public.projects ( id uuid primary key default gen_random_uuid(), account_id uuid not null references public.accounts(id) on delete cascade, name text not null, created_by uuid not null references auth.users(id), created_at timestamptz not null default now(), deleted_at timestamptz, unique (account_id, id) ); create table public.tasks ( id uuid primary key default gen_random_uuid(), account_id uuid not null references public.accounts(id) on delete cascade, project_id uuid not null, title text not null, assignee_id uuid references auth.users(id), status text not null default 'open', created_at timestamptz not null default now(), foreign key (account_id, project_id) references public.projects(account_id, id) on delete cascade ); -- 3. Indexes for RLS, not optional create index account_memberships_user_id_idx on public.account_memberships (user_id); create index projects_account_id_idx on public.projects (account_id); create index tasks_account_id_idx on public.tasks (account_id); create index tasks_project_id_idx on public.tasks (project_id); create index tasks_assignee_id_idx on public.tasks (assignee_id); create index projects_active_idx on public.projects (account_id) where deleted_at is null; The composite foreign key on tasks is not decoration. If tasks.account_id says account A but project_id points to account B, an RLS policy that only checks tasks.account_id has a hole. The database should reject that row before policy code even runs. The indexes are the single biggest performance lever. Supabase's own RLS performance benchmarks show a query on an unindexed user_id column dropping from 171ms to under 0.1ms once a btree is added. On a busy tasks table, that is the difference between a policy check that feels invisible and one that dominates the dashboard query. Now lock the doors. Two passes: enable for the policy machinery, force so that even the table owner runs through it. Then explicit grants, because Supabase exposes everything the authenticated role can touch through PostgREST. alter table public.accounts enable row level security; alter table public.account_memberships enable row level security; alter table public.projects enable row level security; alter table public.tasks enable row level security; alter table public.accounts force row level security; alter table public.account_memberships force row level security; alter table public.projects force row level security; alter table public.tasks force row level security; grant select, update, delete on public.accounts to authenticated; grant select, insert, update, delete on public.account_memberships to authenticated; grant select, insert, update, delete on public.projects to authenticated; grant select, insert, update, delete on public.tasks to authenticated; Do not grant direct client inserts on accounts. Account creation needs a bootstrap path that creates the account and the first owner membership in the same transaction. We will add that RPC after the membership helper. The force line is the one Lovable never writes. Without it, your nightly job that runs as the table owner, backfills, rollups, the script you ran from psql to fix one customer's data, sees every row in every tenant. FORCE ROW LEVEL SECURITY does not constrain superusers or roles with BYPASSRLS, so those roles still belong on a short, audited list. The one function every policy must call Every tenant table policy needs to ask the same question: is the current user a member of this account? If you answer that question with a join through account_memberships from inside a policy, Postgres re-evaluates RLS on account_memberships on every check, which itself joins account_memberships, which itself has RLS. The Supabase performance benchmarks measured this exact pattern at 178,000ms before the fix and 12ms after. The fix is a security definer function in a non-exposed schema, pinned with set search_path = ''. SECURITY DEFINER is not magic by itself: it runs as the function owner, so the owner and grants matter. In Supabase migrations, create it as a trusted role that can read account_memberships without recursive RLS penalties, then test it under the authenticated role. create schema if not exists private; revoke all on schema private from public, anon, authenticated; grant usage on schema private to authenticated; create or replace function private.is_account_member(target_account_id uuid) returns boolean language sql security definer stable set search_path = '' as $$ select exists ( select 1 from public.account_memberships m where m.account_id = target_account_id and m.user_id = (select auth.uid()) ); $$; create or replace function private.has_account_role( target_account_id uuid, required_roles public.account_role[] ) returns boolean language sql security definer stable set search_path = '' as $$ select exists ( select 1 from public.account_memberships m where m.account_id = target_account_id and m.user_id = (select auth.uid()) and m.role = any (required_roles) ); $$; revoke execute on function private.is_account_member(uuid) from public, anon; revoke execute on function private.has_account_role(uuid, public.account_role[]) from public, anon; grant execute on function private.is_account_member(uuid) to authenticated; grant execute on function private.has_account_role(uuid, public.account_role[]) to authenticated; Two details that look cosmetic and are not. The private schema must not appear in your Supabase API "Exposed schemas" setting. The set search_path = '' line forces every object reference in the function body to be schema-qualified, which removes writable-schema and temp-schema surprises from privileged code. Account creation needs a bootstrap path Most RLS tutorials cheat here. They let the user insert an accounts row, then expect the same user to insert the first account_memberships row. That cannot work if the membership insert policy requires the user to already be an owner or admin. Use an RPC that creates both rows in one transaction. The client calls public.create_account('Acme', 'acme'); direct inserts into public.accounts stay unavailable to authenticated. create or replace function public.create_account(account_name text, account_slug text) returns uuid language plpgsql security definer set search_path = '' as $$ declare new_account_id uuid; current_user_id uuid := (select auth.uid()); begin if current_user_id is null then raise exception 'not authenticated'; end if; insert into public.accounts (name, slug, primary_owner_user_id) values (account_name, account_slug, current_user_id) returning id into new_account_id; insert into public.account_memberships (account_id, user_id, role) values (new_account_id, current_user_id, 'owner'); return new_account_id; end; $$; revoke execute on function public.create_account(text, text) from public, anon; grant execute on function public.create_account(text, text) to authenticated; This is the part that makes the starter schema usable on day one. No service key in the browser. No "temporarily open memberships, then close them later." No manual SQL in production for the first customer. The four-policy pattern, applied per table Supabase's own rule of thumb, which is a good one: SELECT uses using only, INSERT uses with check only, UPDATE needs both, DELETE uses using only. to authenticated is mandatory on every policy. Wrap every call to auth.uid() and to your security-definer helpers in (select ...) so the planner caches the value once per statement instead of per row, that single change took an admin check from 11,000ms to 7ms in Supabase's benchmark. -- accounts create policy accounts_select on public.accounts for select to authenticated using ( (select private.is_account_member(id)) ); create policy accounts_update on public.accounts for update to authenticated using ( (select private.has_account_role(id, array['owner','admin']::public.account_role[])) ) with check ( (select private.has_account_role(id, array['owner','admin']::public.account_role[])) ); create policy accounts_delete on public.accounts for delete to authenticated using ( primary_owner_user_id = (select auth.uid()) ); -- account_memberships: the junction table everyone forgets create policy memberships_select on public.account_memberships for select to authenticated using ( (select private.is_account_member(account_id)) ); create policy memberships_insert on public.account_memberships for insert to authenticated with check ( ( role = 'member' and (select private.has_account_role(account_id, array['owner','admin']::public.account_role[])) ) or ( role in ('owner','admin') and (select private.has_account_role(account_id, array['owner']::public.account_role[])) ) ); create policy memberships_update on public.account_memberships for update to authenticated using ( (select private.has_account_role(account_id, array['owner']::public.account_role[])) or ( role = 'member' and (select private.has_account_role(account_id, array['admin']::public.account_role[])) ) ) with check ( (select private.has_account_role(account_id, array['owner']::public.account_role[])) or ( role = 'member' and (select private.has_account_role(account_id, array['admin']::public.account_role[])) ) ); create policy memberships_delete on public.account_memberships for delete to authenticated using ( (select private.has_account_role(account_id, array['owner']::public.account_role[])) or ( role = 'member' and (select private.has_account_role(account_id, array['admin']::public.account_role[])) ) ); -- projects (tenant-scoped, soft-deleted) create policy projects_select on public.projects for select to authenticated using ( (select private.is_account_member(account_id)) and deleted_at is null ); create policy projects_insert on public.projects for insert to authenticated with check ( (select private.is_account_member(account_id)) and created_by = (select auth.uid()) ); create policy projects_update on public.projects for update to authenticated using ( (select private.is_account_member(account_id)) ) with check ( (select private.is_account_member(account_id)) ); create policy projects_delete on public.projects for delete to authenticated using ( (select private.has_account_role(account_id, array['owner','admin']::public.account_role[])) ); -- tasks create policy tasks_select on public.tasks for select to authenticated using ( (select private.is_account_member(account_id)) ); create policy tasks_insert on public.tasks for insert to authenticated with check ( (select private.is_account_member(account_id)) ); create policy tasks_update on public.tasks for update to authenticated using ( (select private.is_account_member(account_id)) ) with check ( (select private.is_account_member(account_id)) ); create policy tasks_delete on public.tasks for delete to authenticated using ( (select private.has_account_role(account_id, array['owner','admin']::public.account_role[])) ); Notice the asymmetry on account_memberships. Reading the membership list is open to any member of the account, you need to see your teammates. Writing it is restricted to owners and admins. This is the policy that prevents the most common privilege-escalation path in vibe-coded SaaS: a member user inserting a row that flips themselves to owner. The policy is stricter than "admins can do everything." Owners can create or change owners and admins; admins can manage members. That keeps a delegated admin from promoting themselves into the role that owns the account. Notice also with check on UPDATE for projects and tasks. Without it, a user could update a row they own and set account_id to a different tenant: a row they do not own moves out of their reach and into someone else's database view. The with check clause re-runs the membership test against the new row, and the composite FK on tasks enforces that project_id belongs to the same account_id. Audit your own database before the next deploy Imagine you're the CTO of a Series A SaaS that started life as a Lovable prototype. You inherited 47 tables. You do not know which have RLS, which have wide-open policies, and which are silently default-deny. Run these eight queries against the production database before the next push. -- 1. Tables in `public` with RLS DISABLED. -- Hard fail for tenant or private-data tables; allowlist intentional public read models. select schemaname, tablename, rowsecurity from pg_tables where schemaname = 'public' and rowsecurity = false order by tablename; -- 2. RLS enabled but ZERO policies (silent default-deny). select t.schemaname, t.tablename from pg_tables t left join pg_policies p on p.schemaname = t.schemaname and p.tablename = t.tablename where t.schemaname = 'public' and t.rowsecurity = true and p.policyname is null order by t.tablename; -- 3. Wide-open USING (true) policies. select schemaname, tablename, policyname, roles, cmd, qual, with_check from pg_policies where schemaname = 'public' and (qual = 'true' or with_check = 'true') order by tablename; -- 4. Policies that target PUBLIC (i.e. include anon). select schemaname, tablename, policyname, roles, cmd from pg_policies where schemaname = 'public' and 'public' = any (roles) order by tablename; -- 5. Public storage buckets, review with an allowlist. select id, name, public from storage.buckets where public = true; -- 6. Tables NOT under FORCE ROW LEVEL SECURITY, review with an allowlist. select n.nspname as schema, c.relname as table, c.relrowsecurity as rls_enabled, c.relforcerowsecurity as rls_forced from pg_class c join pg_namespace n on n.oid = c.relnamespace where n.nspname = 'public' and c.relkind = 'r' and c.relrowsecurity = true and c.relforcerowsecurity = false order by c.relname; -- 7. Roles with BYPASSRLS, review with an allowlist. select rolname, rolbypassrls, rolsuper from pg_roles where rolbypassrls = true or rolsuper = true order by rolname; -- 8. Full policy dump, read every line. select schemaname, tablename, policyname, permissive, roles, cmd, qual, with_check from pg_policies where schemaname = 'public' order by tablename, cmd; These run in seconds against any database. Fail CI for tenant tables with RLS disabled, tenant tables with zero policies, private-data policies that are effectively true, and unexpected public or anon policy roles. Treat public buckets, BYPASSRLS roles, and missing FORCE ROW LEVEL SECURITY as allowlist reviews; normal Supabase projects will have a few expected rows there, but they should never be surprises. The Supabase Database Linter ships related checks such as 0013_rls_disabled_in_public and 0003_auth_rls_initplan. Use the Advisor output as a supplement, not a replacement. It can tell you RLS is missing or slow; it cannot know whether tasks.project_id belongs to the same tenant as tasks.account_id. Test policies the way you test endpoints A policy you have not tested is a wish. The canonical Postgres test framework is pgTAP, and the Basejump team's basejump-supabase_test_helpers extension adds the helpers that matter for Supabase: tests.create_supabase_user, tests.authenticate_as, tests.rls_enabled, tests.clear_authentication. Together they let you write a test that creates two users in two tenants and asserts that one cannot see the other's rows: the assertion those apps needed before publish. Wire supabase test db into CI on every pull request. If a developer adds a new tenant table without enabling RLS, the test that asserts tests.rls_enabled('public', 'new_table') fails before review. Add regression tests for the two boring bugs above: create_account() creates the owner membership, and Bob cannot insert a task with Bob's account_id and Alice's project_id. That second test should fail at the database constraint, not in React. What this changes for the team building the app For a multi-tenant Postgres app, this is the starting point we expect to see: accounts, memberships, security-definer helpers, the four-policy pattern, the audit script in CI, and pgTAP tests on every pull request. The fix is mechanical, not heroic. It just has to actually be applied. If you are running on Supabase and have not read your pg_policies output line by line in the last month, do it today. Run the eight queries in the audit section. If the hard-fail checks return rows, or if the allowlist makes you uneasy. book a call and we will walk through it with your team. If you want the broader engineering picture of how we build production-grade backends from the schema up, the engineering practice page has the rest. The lesson of CVE-2025-48757 is not that Postgres RLS is dangerous. It is that the default the AI tools generate is dangerous. The version with force row level security, a real account bootstrap path, tenant-scoped foreign keys, security-definer membership functions, indexed policy columns, and pgTAP tests in CI is not exotic. It is a few hundred lines of SQL you adapt, run, and keep under test before someone else scans your app for a blog post. --- ### The 2026 vibe coding stack: ten production decisions after Lovable URL: https://appssemble.com/blog/vibe-coding-stack-2026 A production-ready stack for hardening Lovable apps after the demo. The best vibe coding stack in 2026 is not a rebellion against Lovable. It is Lovable velocity with senior-engineering decisions added before the app reaches 10K MAU, $10K MRR, or its first enterprise procurement call. The default Lovable-generated app is almost right: React, Vite, TypeScript, Tailwind, shadcn/ui, Radix UI, and a Supabase-backed backend through Lovable Cloud or your own Supabase project. Lovable's funding and ARR growth made this more than a toy category. It is the new default for founders who want a TypeScript product in production this week, not after a quarter of architecture meetings. The problem is that generated defaults optimize for the first demo. Senior teams optimize for the first painful month after the demo, when bandwidth costs jump, cold starts show up in p95 latency, and the first customer asks for SSO. The Lovable stack wins because it starts in the right place Lovable works because it generates what most small product teams would pick anyway. React, TypeScript, Vite, Postgres, Tailwind, shadcn/ui, Radix UI, Supabase, Stripe, and managed deploys are familiar enough for AI tools to produce decent code and common enough for engineers to debug quickly. That matters more than people admit. Claude and Cursor produce better Postgres than they produce niche databases, because SQL and Postgres have years of public examples behind them. The same is true for React, Vite, Next.js, Stripe, and Tailwind. This is why we do not tell founders to throw the stack away. If your Lovable app has real users, the fastest path is usually to keep the shape and harden the weak layers. That is the same engineering discipline behind products like Grovs, which processes 10M+ events daily: keep the core simple, instrument it properly, and move the heavy parts when the numbers justify it. Frontend should stay familiar, but marketing should get lighter For an exported Lovable app, Next.js is not the starting point. Lovable's useful default is React + Vite + TypeScript; keep it if the dashboard works and the real problems are auth, data access, observability, or deployment cost. For a new full-stack TypeScript app, Next.js 16 App Router is still a safe default. It sits in the center of the current TypeScript ecosystem, and AI generators understand its patterns well enough to be useful. The senior adjustment is to make that a deliberate migration, not a reflex. The second adjustment is to stop using an app runtime for pages that do not need one. Astro is a better fit for marketing pages, pricing pages, blogs, and docs because content pages should not ship unnecessary JavaScript just to render static copy. Imagine you are a technical founder with a Lovable SaaS at 12K MAU. Your dashboard needs authentication, streaming UI, server actions, and cached data. Your homepage needs fast HTML, a pricing table, and a contact CTA. Treating both as the same frontend problem is how small products accumulate slow pages before they have a growth team. Postgres stays, but Drizzle replaces generated database glue Postgres is the right default. Supabase is the right first home for it, especially when you want auth, storage, realtime, RLS, and edge functions in one console. The swap is not Postgres to something fashionable. The swap is loose supabase-js calls everywhere to a typed database layer with Drizzle ORM where server-side data access makes sense. Drizzle still matters because its runtime is tiny, dependency-light, and natural on serverless and edge. But the Prisma comparison changed in 2026: Rust-free Prisma is production-ready in v6.16+ and Prisma v7 narrows the old cold-start argument. We still prefer Drizzle when bundle size, SQL control, and migration legibility matter, but do not cite legacy Prisma cold starts unless you are actually running legacy Prisma. One warning: if Supabase RLS is your security boundary, do not swap supabase-js for a privileged Drizzle client and call it safer. Either carry the user's identity into Postgres so policies still apply, or move authorization into application code and test it explicitly. Drizzle also gives you SQL-shaped control over migrations. That matters once tables have real data and a generated migration can lock a table during business hours. We like tools that keep the database legible, because production incidents are hard enough without an ORM hiding the exact query. Server state belongs in TanStack Query, not in context The state-management mistake in vibe-coded apps is predictable: everything becomes React context. API responses, auth state, modals, filters, draft forms, and feature flags all end up in one blurry client-side bucket. The better split is boring and effective. Use TanStack Query for server state, Zustand for small global client state, React Hook Form for forms, and useState for local component state. Jotai is a useful escape hatch when you have fine-grained derived state, but most SaaS products never need it on day one. This is one of the cheapest swaps in the whole stack. TanStack Query has roughly 5M weekly downloads and Zustand roughly 4M, so AI tools have enough examples to generate workable code. More important, your engineers can reason about cache invalidation, retries, stale data, and optimistic updates without reading a 900-line context provider. Observability has to arrive before the support tickets Sentry belongs in the first production deploy, not in the first outage. Vibe-coded apps often discover errors from customer screenshots because nobody wired up error monitoring, breadcrumbs, performance tracing, or release tracking. Our default is Sentry plus PostHog. Sentry answers "what just broke?" PostHog answers "what did the user do before it broke?" and gives you product analytics, session replay, feature flags, and LLM observability in one place. This is where the difference between a demo and a product becomes visible. Semaphr manages 500K+ app sessions because release management is treated as product infrastructure, not admin work. The same rule applies here: if you cannot see errors, sessions, and releases, you are guessing. AI features need rate limits, evals, and pgvector The default production AI stack for a TypeScript product is simple: Vercel AI SDK, Claude, and pgvector. The SDK gives you a provider-agnostic application layer, Claude is a strong default model, and pgvector keeps RAG inside the Postgres database you already operate. The missing layer is discipline. Rate limiting, auth checks, abort signals, error boundaries, moderation, and evaluation on changed prompts are not optional once users can spend your model budget. Most vibe-coded AI features skip these because they make the demo less magical. We add them because they make the feature survive real traffic. This is also where our AI practice and engineering practice overlap. The model call is the easy part. The product work is the queue, retry path, fallback, logging, and human escalation when confidence is low. Vercel is the launch pad, not the permanent answer Vercel is the right place to start. Preview URLs, zero-config deploys, ISR, and native Next.js support are worth far more than $20/month when you are still changing the product every day. The mistake is treating Vercel as a forever infrastructure decision. The working cost comparison is still blunt, but the units matter: Vercel Pro includes 1TB of Fast Data Transfer and then starts at $0.15/GB, while Hetzner EU cloud servers include 20TB of outbound traffic and charge roughly EUR 1, or about $1.20, per extra TB. Once bandwidth dominates the bill and keeps climbing, the Vercel-to-Hetzner conversation should already be on the roadmap. Our ladder is simple. Months 0-6: use Vercel and ship. Post-validation: move the app to Hetzner CX32 plus Coolify when the bill starts stinging and your team can own operations: OS patches, backups, rollback, log drains, and recovery drills. Keep Vercel or Cloudflare Pages for marketing. Multi-region AWS or Kubernetes comes later, and most products never need it. Enterprise sales change auth and billing before they change your database The first enterprise buyer usually does not ask you to rewrite the backend. They ask for SSO, auditability, procurement-friendly billing, and a contract that does not make their legal team nervous. That is why Clerk is a strong default for speed, while WorkOS belongs beside it when enterprise SSO becomes a sales requirement. WorkOS gives you 1M MAU free, but SSO connections cost $125 per connection. Do not add that complexity before a buyer asks for it. Do not wait until the deal is stuck, either. Payments have the same split. Stripe is the default when you need control and custom billing flows. Polar makes sense for a solo founder selling globally because it is a Merchant of Record with a base fee of 4% + $0.40 and handles VAT, GST, sales tax, fraud, and compliance. That base fee is not the whole effective rate: international cards, subscriptions, refunds, disputes, and payout provider fees can add more. The wrong answer is homegrown billing. The production-grade stack is a decision matrix, not a rewrite Here is the stack we keep landing on when a Lovable-generated app starts to hit real constraints: LayerLovable-era defaultProduction decisionApp frontendReact + Vite + TypeScriptKeep Vite unless Next.js 16 solves a real product needMarketingSame app repoAstro for static marketing, docs, and blog pagesDatabaseSupabase or Lovable CloudKeep Supabase; add Neon branching or self-hosted Postgres only when neededData accesssupabase-js everywhereDrizzle with an explicit RLS or application-auth strategyStateReact context sprawlTanStack Query + ZustandObservabilityNone or console logsSentry + PostHogAIDirect model callsVercel AI SDK + Claude + pgvectorDeploymentLovable/Vercel-style managed deployVercel first; Hetzner + Coolify when bill and ops maturity justify itAuthSupabase Auth or ClerkWorkOS when enterprise SSO blocks revenuePaymentsStripePolar when Merchant of Record tax handling beats lower processor fees The point is not to make the stack clever. The point is to keep the parts AI tools generate well, then add the production pieces before the app punishes you for skipping them. If your vibe-coded app is hitting walls at 10K MAU, we can audit the stack and turn the decision matrix into a PR-ready plan. Book a call with appssemble and bring the slow traces, the Vercel bill, and the weirdest support ticket. --- ### An hour with a vibe-coded codebase: 27 things that should not have shipped URL: https://appssemble.com/blog/scanning-first-vibe-coded-app A production audit of the hidden risks inside a vibe-coded MVP A founder handed us a Lovable-generated app last month and asked the simple question every founder asks: "Can you scale this?" The product had paying users, a working onboarding, and a marketing page that looked sharper than most Series A sites. We agreed to look before we quoted. We ran a 30-item audit before we touched a single file. In this repo, by lunch, 27 of those items had failed. None of them were cosmetic. This post is the audit, in the order we ran it, with the queries and commands we used. It is not an argument against Lovable, Bolt, v0, Cursor, or Replit Agent. Those tools are real, and they ship usable day-one code. The argument is narrower: vibe-coded output is day-one code, not production code. If you take it to real users without a senior pass, the failure modes are predictable and they are mostly invisible from the outside. What we expected, and what fell out Imagine you're a founder who shipped your MVP in a weekend on Lovable, picked up 4,000 signups in a quarter, and now you want to add billing, a second user role, and a mobile app. You ask an agency to scale it. You expect feedback like "the components could be tidier" or "you'll want to extract the auth context." You don't expect the report we sent back. Here is what showed up in the first hour, before we read a line of business logic: With the project's current RLS and grants, the Supabase anon key in the browser bundle could read every user's records. Two row-level security policies were the wrong shape and one was inverted. The schema referenced a table that did not exist in the live database. One list view, after the Supabase API row cap had been raised, fired 50,001 queries to render 50,000 rows. The repo had zero tests and no CI gate. package.json carried 110 dependencies; the app actually used about 30. We have seen versions of this before, and the public scans point in the same direction if you keep the source quality straight. Matt Palmer's CVE disclosure describes Lovable-generated projects with insufficient Supabase RLS; Vibe App Scanner's summary reported 170 exposed projects and 303 vulnerable endpoints, while NVD marks CVE-2025-48757 as supplier-disputed. Escape's methodology says its team scanned 5,600 public vibe-coded apps and found 2,000+ high-impact vulnerabilities and 400+ exposed secrets, with sampling and passive-scanning limitations. CodeRabbit's 470-PR report found AI-co-authored PRs carried about 1.7x more issues overall and up to 2.74x more security issues. None of those numbers proves every vibe-coded app is broken. They prove the same invisible failure modes keep recurring, and this is what they look like inside one repo. The audit, run in order Five categories, in the sequence we work through them. The first one is where most of the damage lives. 1. Secrets and row-level security Open the deployed app. DevTools → Network → filter on /auth/v1 or /rest/v1. The request headers tell you which Supabase key the client is carrying. If apikey decodes to "role":"service_role", the audit is over and you rotate immediately. In this codebase it was the legacy anon key: the browser-exposed key Supabase expects for public clients. That is fine, by design, if grants and RLS are correct. It was not. From a psql shell against the project's database: select schemaname, tablename, rowsecurity from pg_tables where schemaname = 'public'; Two tables had rowsecurity = false. For the rest, we listed policies and found the canonical Lovable anti-pattern: CREATE POLICY "Users can view data" ON public.user_data FOR SELECT USING (auth.role() = 'authenticated'); That policy reads as: any logged-in user can read every row in this table. Sign up a free account, get the anon key from your own bundle, and you can read every other customer's data. The correct shape is USING (auth.uid() = user_id). Supabase's model is simple: the API key says what application is calling, Auth says who the user is, and RLS decides which rows that user can touch. We confirmed it with a curl against the public REST endpoint, using the anon key from the bundle and a fresh user's JWT: curl "$URL/rest/v1/user_data?select=*" \ -H "apikey: $ANON" \ -H "Authorization: Bearer $JWT" It returned every row. We also found a second table where the write policy was the wrong shape: CREATE POLICY "Users can add rows" ON public.user_data FOR INSERT TO authenticated WITH CHECK (auth.role() = 'authenticated'); That policy does not check ownership. Any logged-in user could insert a row with someone else's user_id. In Postgres RLS, a missing INSERT policy denies by default; broad WITH CHECK policies are what make writes dangerous. If this fails, your next feature sprint is paused until private customer data is private again. That is the Moltbook pattern: the public Supabase key was not the bug by itself. Missing RLS made it powerful enough to expose 1.5 million API tokens and 35,000 emails. The Lovable security scanner had given the project a green check, because, as the Vibe App Scanner write-up puts it: the scanner checks whether RLS is enabled, not whether the policies match the product's authorization model. A green check is not a substitute for reading the policies. 2. The schema was partly hallucinated Once we trusted the auth model less, we trusted the schema less. We diffed the table names referenced in the TypeScript against the live information_schema.tables. Three tables in the code did not exist. One: users_profile, had been in a draft migration that was never run; the LSP types still claimed it existed because the generated database.types.ts was stale. Two foreign keys had no indexes. Postgres does not auto-index foreign-key columns; you add those indexes yourself. The result was a JOIN between orders and customers doing a sequential scan on 80,000 rows every time a list view loaded. We also found three columns where a JSON blob was carrying what should have been a relational table: metadata jsonb with a stable shape, queried with ->>'customer_id' in three different files, never indexed. Inigra's self-published audit of roughly 600,000 lines of vibe-coded output puts this near the top of the recurring patterns: AI is consistently good at the visible (UI, features, flows) and consistently weak at the invisible (security, testing, architecture). 3. The architecture had collapsed under itself App.tsx was 612 lines. It held the router, the auth context, the Supabase client, three useEffect blocks for hydration, and the dashboard's data fetching. The model had kept appending because that is where the cursor was. There were three slightly-different copies of the same form-validation function in three components. GitClear's 211M-line AI code quality report found copy/pasted lines rose to 12.3% of changed lines in 2024, up from 8.4% in 2021, and this repo was worse than that benchmark. The list view that loaded the 80,000-row table fetched it like this: const orders = await supabase.from('orders').select('*') const enriched = await Promise.all( orders.data!.map(async (o) => { const customer = await supabase .from('customers') .select('*') .eq('id', o.customer_id) .single() return { ...o, customer: customer.data } }) ) In this project, Supabase's default 1,000-row API cap had been raised, so the list path really did fetch 50,000 orders. That meant one query for the list and 50,000 queries inside the .map(), 50,001 total per render. On the default cap, the same code still fails; it fails as 1,001 requests before it fails as 50,001. The fix is a single .select('*, customers(*)') with a foreign-key index on customer_id. The N+1 is the obvious problem; the lack of pagination is the worse one. There was no .range() or .limit() anywhere in the file. There were no error boundaries. One unhandled promise rejection blanked the whole app. Two useEffect blocks shared state in a way that re-triggered each other on every render. We ran tsc --noEmit --strict and stopped counting at 180 errors. 4. Dependencies were carrying weight, and CVEs npm ls --depth=0 returned 110 packages. We grepped imports and the app actually used around 30. The drift was the Lovable signature: lucide-react, react-icons, and heroicons all installed because three different prompts had each picked their favorite. date-fns and dayjs both present. Zustand and Redux Toolkit both wired into the app, holding overlapping state. npm audit --omit=dev returned eleven advisories, four of them high: an outdated axios, an old next-auth, a vulnerable serialize-javascript transitive. There was no package-lock.json committed, so every CI run (when there was a CI run) would have resolved a different transitive tree. Nothing in the build pipeline would have caught a typosquatted package, and AI tools are already part of the supply-chain blast radius, in the 2025 Nx incident, Snyk reported that malicious packages used local AI-agent reconnaissance and exfiltrated GitHub tokens, npm tokens, SSH keys, and environment variables. 5. Tests and observability did not exist find . -name "*.test.*" -o -name "*.spec.*" | wc -l Zero. The only file in tests/ was the Vitest example template. Coverage tooling had never been wired up. There was no CI workflow at all, pushes to main deployed straight to Vercel. No build gate, no test gate, no lint gate, no type-check gate. Sentry was not configured. There was no structured logging, no health-check endpoint, no error tracking of any kind. The first time a user hit a 500, the founder would learn about it from a Twitter DM. This matches the broader direction of the developer surveys and PR studies. Harness reported that 67% of developers spend more time debugging AI-generated code, and CodeRabbit found AI-co-authored PRs carried about 1.7x more issues. When the codebase grows faster than the test suite, every regression becomes archaeology. What we replaced, and what we kept The conversation with the founder was short. Two options on the table: Patch the security holes in place, tell the team this is the floor, and re-quote in a quarter when something else breaks. Keep what works, throw away what doesn't, and rebuild the data layer behind the same UI. We argued for option two and they agreed. The UI was the part of the codebase the model was good at: the components were inconsistent but they were on-brand and the founder liked them. The data layer, the auth model, and the deployment pipeline were where the rot was. Replacing those without changing the surface is a tractable three-week job. Patching them in place is an open-ended one. What we kept: The Tailwind theme, the component primitives, the page layouts, the marketing site. The Supabase project itself, plus the existing user accounts. The product's information architecture and the founder's content. What we replaced: Every RLS policy, written from auth.uid() = user_id outward, with a pgTAP test per policy that asserts a second user cannot read or write the first user's rows. The Supabase client wrapper, with a server-only admin client behind API routes that re-verify the JWT on every request. The schema, three real tables in place of the JSON blobs, foreign-key indexes added, the hallucinated users_profile either created properly or removed from the code. The list views, paginated with .range() and joined with .select('*, customers(*)') instead of the N+1. package.json, down from 110 dependencies to 34, with a committed pnpm-lock.yaml and Renovate set to weekly. A GitHub Actions pipeline: tsc --strict, ESLint, Vitest unit tests, Playwright smoke tests, and a gitleaks scan, all gating the deploy. Sentry on the front and back end, with source maps and PII filtering, plus a /healthz endpoint and structured logs piped to Logtail. Three weeks later we shipped. The founder kept the surface their users already knew. The new data layer carried the same product, just with the floor under it that should have been there from the start. The lesson, and where it leaves you Vibe-coding tools are doing something genuinely useful. The first version of a product in an afternoon is a real change in how startups can move, and we are not nostalgic for the era when you needed a four-week sprint to put a working dashboard in front of a user. The mistake is treating that first version as the production version. The public numbers are messy; the failure modes are not. That is why the audit is fast. RLS that allows any authenticated user, browser-exposed keys mistaken for authorization, broad WITH CHECK policies, hallucinated tables, missing foreign-key indexes, no tests, no CI, three icon libraries. If you are reading this and you have shipped an MVP on Lovable or Bolt that is starting to take traffic, you can run most of this checklist on yourself in an afternoon. If you would rather hand it to someone, that is what our engineering practice does. We also fold the AI work into the same engagement when the product needs it: the rebuild we just described kept a vibe-coded UI on top of a hardened backend, and that is the shape most of these projects need. If you have built on Lovable or Bolt and you are ready to scale, this is the audit we start with in week one. Book a call. --- ### When to stop vibe coding and hire engineers: six signals your AI-built app needs engineering help URL: https://appssemble.com/blog/when-to-stop-vibe-coding Six signals that an AI-built product needs real engineering ownership. The failure usually does not start with a dramatic outage. It starts with a founder spending another evening asking Lovable, Bolt, Cursor, or Claude to fix the same flow for the third time. Vibe coding is useful in the first window of a product. You can validate a workflow, show a customer a real screen, and get from idea to first demo without waiting six weeks for a team to assemble. The mistake is treating that first window as a permanent engineering strategy. We are not anti-AI. appssemble is built around AI-first workflows, but the work still needs owners, tests, deployment discipline, and a human who understands the system. Stop vibe coding when one of these six signals fires. Your rework bill crossed $300 a month The headline pricing is not the real pricing. Lovable lists $25 and $50 entry plans, but its own plans and credits docs include higher monthly credit tiers and top-ups. A small bill can become $200 to $500 a month when you are actively re-prompting the same broken screens, auth flows, or data bugs. The crossover is not "AI tool bill is higher than engineer bill." Our appssemble tripwire is narrower: if roughly $300 a month is going into retrying the same five problems, you are no longer buying speed. You are buying another loop. Senior nearshore engineers often land closer to $70 to $120 per hour, with lower rates possible for narrower or mid-level work. The point is not that $300 buys a rebuild. It buys the first diagnosis: the broken abstraction, missing test, or bad Supabase policy that your prompts keep circling. The same bug returned three times in one week Bug loops are the clearest technical signal because they fire fast. The pattern is simple: you describe a bug, the tool fixes it, the fix breaks something adjacent, and two days later the original bug comes back. Three returns of the same bug in a week means the codebase has no stable guardrail. Two unrelated regressions caused by one prompt means the tool is rewriting around the problem instead of isolating it. Imagine you're running a small B2B onboarding product with 40 trial accounts. The signup flow breaks, the AI fixes it by changing auth state, then billing starts assigning users to the wrong workspace. You do not need ten more prompts. You need one engineer to add regression tests and make the auth boundary explicit. A real customer asked for SOC 2, GDPR, or HIPAA Compliance turns this from preference into a yes-or-no decision. The first enterprise prospect who sends a vendor security questionnaire is asking whether your product has an SDLC, access logs, review gates, and data handling rules. If your honest answer is "we prompt changes and inspect the preview," you do not have the artifact the customer needs. You have a chat history. This is where AI-generated code often fails quietly. Audit logs are rarely produced by app builders unless someone asks for them, and access control is easy to make look right in the UI while staying wrong at the database layer. A senior engineering pass can turn this into a plan: permissions, logs, review flow, backup policy, and the short list of gaps that block the deal. Your slowest route crossed 2 seconds and nobody can explain why Performance cliffs rarely come from one exotic failure. They come from N+1 queries, missing indexes, unbounded list endpoints, no caching, and no connection pooling. Those are not prompt problems. They are diagnosis problems. For us, 2 seconds is an appssemble tripwire, not a public web-performance standard. If a key API route or synthetic page-load check moves from under 500ms to above 2 seconds at p95 and nobody can name the cause, stop adding features. If you are tracking Core Web Vitals instead, use LCP separately: Google's guidance treats 2.5 seconds or less at the 75th percentile as good. This does not mean you need a full rewrite at 5,000 users. Often the first fix is one afternoon of query profiling, two indexes, one pagination change, and a cache in front of the expensive endpoint. Send this to an engineer: profile the slowest route, check Supabase indexes, inspect N+1 queries, and confirm pooling before adding features. Your custom integration works 95 percent of the time Stripe checkout is easy to scaffold. Stripe webhooks are where the real product starts. The painful cases are always invisible from the preview pane: missing signing secrets, test keys in production, no idempotency keys, failed 3DS cards, dropped trial-end events, or database state drifting away from Stripe state. The same shape appears with Twilio callbacks, Slack apps, OAuth refresh flows, and SCIM provisioning. Ninety-five percent working is not good enough for money movement or account access. Five failed payments in 100 can mean angry users, support debt, and revenue you cannot reconcile. When the integration has async callbacks, retries, signatures, or rate limits, bring in an engineer before the customer support inbox becomes your monitoring system. The fix is usually not huge, but it does require someone who can test outside the preview pane with the vendor's real tooling. For Stripe, ask for verified webhook signatures, idempotency, retry handling, live/test key separation, and reconciliation between Stripe and your database. Two contractors bounced after seeing the repo The hand-off signal is easy to rationalize because it feels personal. You hire a contractor, they pull the repo, and within an hour they say they cannot tell where state lives or which of the seven auth checks is real. Then the second contractor says the same thing. That is the point where the pattern has stopped being anecdotal. At that point, the problem is not that engineers are unreliable. The problem is that no human has owned the structure long enough to make the product legible to the next person. We see this often in rescue work. The founder was prompting features, not designing a system, so the repo contains dead branches, duplicated logic, unclear data ownership, and no regression guard. The first paid engineering task is not "add feature X." It is "make this codebase possible to work on." Do not hire just because Twitter told you to There is a credible version of staying solo. Pieter Levels, Marc Lou, Tony Dinh, Damon Chen, and other solo founders have made the public case for staying small, shipping fast, and avoiding premature hiring. They are not wrong. They are operating in a product shape that fits the model: simple scope, low compliance burden, direct founder ownership, and a business where the founder can hold most of the system in their head. You should probably keep vibe coding if you have no paying users, the product changed materially in the last 30 days, your monthly tool bill is still near $50, and no recurring bug loop has appeared. Hiring an engineer to harden a product nobody wants is theatre. It raises burn before it lowers risk. The signal changes when real money, real customer data, or real procurement appears. A solo PDF delivery product with Stripe checkout is not the same as a B2B SaaS handling enterprise users, HIPAA-adjacent records, or payments that fail every Tuesday. Start fractional before you hire full-time The binary choice is wrong. Staying solo forever and hiring a full-time CTO at $250K+ compensation are not the only two options. Start with one senior engineer for 5 to 10 hours a week, aimed at the signal that hurts most. That can cost roughly $1,500 to $3,500 a month and should produce a measurable result in two weeks: the recurring bug stops, the webhook gets verified, the slow query is named, or the compliance gap becomes a checklist. If two or more signals are firing, move to a fractional CTO or embedded engineering team for a short engagement. The job is to stabilize the codebase, install review and release discipline, document the risky flows, and make the next hire cheaper to onboard. The full-time first engineer comes later, when the product is stable enough to own. Bring them into a codebase with tests, runbooks, documented auth and billing flows, and a backlog that is more than "please decode this AI-generated repo." The right time to stop is earlier than the incident Security incidents are the most expensive signal because they arrive after the damage. The public examples are already enough. Kaspersky's writeup says EnrichLead shut down after exposed keys, missing auth, and client-side controls were abused. Anton Karbanovich reported $2,500 in Stripe fees after 175 customers were charged $500 each; Stripe's own docs note that processing fees from the original transaction are not returned. Wiz found Moltbook exposed 1.5 million API authentication tokens, 35,000 emails, and private messages. Tom's Hardware reported that Replit's agent wiped 1,206 executive records and 1,196+ company records during a code freeze in the Lemkin incident. You do not need to wait for that version of clarity. The cheaper signals arrive first: the $300 rework tripwire, the third regression, the procurement questionnaire, the 2-second route tripwire, the 95 percent integration, the second contractor who walks away. Vibe coding is a strong way to validate. It is a weak way to operate a product that has customers, money, compliance, and data at stake. If two or more signals are firing, book a call. Most rescues start with one engineer, ten hours, and a diagnosis. --- ### Lovable + Supabase at 1,000 vs 10,000 users: what breaks and how to fix it without leaving URL: https://appssemble.com/blog/lovable-supabase-1000-vs-10000-users How to harden Lovable and Supabase for 10K users without migrating Your Lovable app ran fine at 1,000 monthly active users. The Supabase Pro tier felt like a steal at $25/month, the dashboard was green, latency was boring. Then you hit 10,000. The bill jumped, p95 latency went sideways, and one Tuesday at lunch the database went read-only for nine minutes while you stared at the Vercel logs. This is the most predictable scaling cliff in the modern serverless stack. We see it every month when founders ask us to audit a Lovable codebase that "stopped working without anyone changing anything." Nothing changed: the user count did. And the defaults that ship with Lovable + Supabase are tuned for the 1K-user case, not the 10K one. The good news: the fixes are mechanical, almost all of them keep you on Supabase, and the normal operating range is still small: roughly $150-$250/month for Supabase Pro, Small or Medium compute after credits, PITR, low-usage Redis, and a real job runner. That is not a ceiling, and 10K MAU is not what triggers it. It is the price of turning a 1K-user stack into a 10K-user stack without hiring a DevOps person. Pebblely scaled to 1M users in seven months on Supabase Auth without leaving the platform. You almost certainly do not need to leave either. You need to harden. This is for the CTO or technical founder sitting at the 1K-to-10K crossover. The work is straightforward: find what breaks first, fix twelve mechanical defaults, then decide whether Supabase still earns its place in the stack. What "fine for 1,000 users" actually means The default Lovable + Supabase setup is a React/Vite SPA calling the Supabase JS client directly from the browser, with row-level security as the only authorization boundary. Add Supabase Pro at $25/month, which includes $10/month in compute credits. That covers one Micro instance: 2-core shared ARM, 1 GB RAM, 60 max direct connections, 200 max pooler clients. At 1,000 MAU this works because nothing is stressed. In the simple CRUD apps we audit, Micro is usually fine until query shape breaks it: the working set fits in memory, sequential scans are cheap because the dataset is small, and your concurrent connection count rarely tops a few dozen. Supabase returns up to 1,000 rows per request by default, which looks fine because no table you own has more than that yet. Now scale to 10,000 MAU. Assume 15% DAU and roughly three sessions per daily user. That is 1,500 daily users and about 4,500-5,000 sessions per day. If a launch email, webhook burst, or AI crawler compresses that traffic into a lunch-hour spike, hundreds of concurrent requests are plausible. Your dataset crossed 100K rows in the busy tables months ago. None of the per-row math you got away with at 1K still works. What actually breaks first Five things, almost always in this order: 1. Row-level security goes quadratic. Lovable writes RLS policies that look correct and pass at 1K rows. At 100K they crawl. The reason is one specific footgun we will fix in the next section. 2. The direct connection pool saturates. A Vercel account can autoscale to 30,000 concurrent function executions. Your Supabase Micro instance has 60 direct connections. If server-side code talks to port 5432, the first real traffic spike exhausts the pool, and new requests block waiting for a connection, then time out, then look like a database outage in your logs. 3. The 1,000-row API ceiling bites without a product-level error. Lovable scaffolds select('*').eq('user_id', userId) everywhere, with no pagination. Supabase caps responses at 1,000 rows by default. Pages can render with missing data unless you paginate and ask for counts explicitly. 4. Cache hit ratio drops below 99%. Postgres starts hitting disk for queries that used to live in shared buffers. Latency doubles, then triples, with no obvious cause in the slow-query log. 5. Background work clogs the request path. Without a job runner like Trigger.dev or Inngest, every webhook, every email send, every async job tends to run inside a function tied to a user request. Long jobs stall short ones. There are more, table bloat, lock contention, user-reported connection leaks around attachDatabasePool on Vercel Fluid, but those five drive the lunchtime outage. We will fix them in order. Fixing RLS at scale This is the single biggest performance footgun in Lovable-generated code, and the fix is one line of SQL per policy. The standard Lovable policy looks like this: CREATE POLICY "Users can read own posts" ON posts FOR SELECT USING (user_id = auth.uid()); auth.uid() is a function call. Postgres evaluates it once per row during the scan. On a 100K-row table, that is 100K function invocations per query. The query planner cannot cache the result because it does not know the function is stable from its call site. Wrap the call in a SELECT and the planner inserts an initPlan node, evaluating the function exactly once and caching the result for the rest of the scan: CREATE POLICY "Users can read own posts" ON posts FOR SELECT TO authenticated USING (user_id = (SELECT auth.uid())); Supabase's own RLS troubleshooting docs show the simple auth.uid() wrapping case improving from 179ms to 9ms, and a compound function policy going from 11,000ms to 10ms. The exact win depends on policy shape, but the direction is not subtle. We have measured similar numbers on three Lovable codebases this year. Two more RLS rules to apply at the same time: Index every column used in an RLS policy, and every foreign key. Postgres does not auto-index FKs. In Supabase's 1M-row team-policy test, the unindexed version timed out past two minutes; the wrapped-and-indexed version ran in single-digit milliseconds. Use CREATE INDEX CONCURRENTLY so production stays online while it builds. Push multi-tenant join policies into a SECURITY DEFINER function. A policy that joins through a team_user membership table evaluates RLS on every joined row. Supabase's has_role() example drops from 178,000ms to 12ms once the lookup is moved into a wrapped security definer function. Add TO authenticated to every policy on authenticated endpoints so anon traffic skips evaluation entirely. Connection pooling: stop talking to port 5432 The second cliff is connection exhaustion, and this is the one that takes you offline rather than slow. Lovable's browser client is fine, it goes over PostgREST and shares one HTTP path. The trouble starts the moment you add server-rendered Next.js routes, Vercel Functions, or Drizzle/Prisma talking directly to Postgres. Each function instance can hold a connection. Vercel can autoscale to 30,000 concurrent executions. Your Micro instance has 60 direct connections. The math does not work. The fix is Supavisor in transaction mode on port 6543, not direct on 5432. Supabase's shared pooler is Supavisor; paid projects can still use a dedicated PgBouncer pooler when they need the lowest latency. The published benchmark numbers from Supabase's own engineering blog: a single 16-core Supavisor instance handles 250,000 concurrent connections; two 64-core instances clustered serve 1,003,200 simultaneous connections at 20,000 QPS, with p95 latency of 47ms at peak load. That is the pooler's benchmark, not your app's guarantee. You are nowhere near it. Transaction mode acquires a Postgres backend connection only for the duration of a single transaction, then releases it. That stops 500 short-lived function invocations from becoming 500 backend Postgres connections. It does not erase every ceiling: Micro still has 200 pooler clients, Small has 400, and slow queries can occupy the backend pool long enough to queue traffic. Transaction pooling buys concurrency, not slow-query forgiveness. The trade-off: transaction mode disables session-level features. No prepared statements, no LISTEN/NOTIFY, no advisory locks across queries. Prisma and other database clients can be configured for pooler-safe behavior, usually by disabling prepared statements. Older code may need a small rewrite. Pool sizing for a 10K-MAU app on Pro/Small (90 direct, 400 pooler clients): Direct backend pool: 30-50, leaving headroom for migrations, dashboard, and replication slots. Per-Vercel-Function client pool: 1. One client per cold invocation. Let Supavisor handle fan-in. Realtime/long-poll connections: count separately against the 500 included concurrent realtime connections on Pro. If you are on Vercel Fluid and using attachDatabasePool against the Shared Pooler, read GitHub discussion #40671 first. It is a user-reported pattern, not a confirmed vendor root cause, but the symptom is worth checking: suspended functions can make pooler-client counts climb when you thought connections were idle. Pin to a per-project pooler or aggressively lower idle timeouts. Caching: the cheapest fix with the fastest payoff Lovable apps ship with zero caching. Every page load, including the marketing-style ones nobody is logged into, hits Postgres through PostgREST. At 10K MAU this is the single highest-ROI fix on the list. Three layers, in order of payoff: HTTP/CDN cache. For anything not user-specific, marketing pages, public profiles, product catalogs, leaderboards: revalidate: 60 on a Next.js route turns repeated traffic to the same public URL into roughly one origin fetch per minute per path. If those 10,000 page loads hit ten popular product pages, the database sees about ten origin fetches per minute. If they hit 10,000 unique profile URLs, you still need Redis, denormalized tables, or a different cache key. Upstash Redis for read-through caching of expensive authenticated queries: dashboards, complex aggregations, denormalized views. The free tier covers small command volume, pay-as-you-go is priced by command count, and the fixed 250MB plan is $10/month. For small cache footprints it can stay under $10; for high-cardinality dashboards, price it before you promise it. Materialized views for analytics and dashboards. The Prince Nzanzu scaling guide reports a dashboard load dropping from 12 seconds to 200ms after moving aggregate queries into a materialized view refreshed every five minutes via pg_cron. We have replicated similar numbers: a SaaS billing dashboard that took 8.4 seconds for the founder to load went to 180ms after one materialized view and one composite index. The composite-index point is worth repeating. The same guide reports a query going from 4.2 seconds to 48ms with a composite (user_id, status) index plus a partial index WHERE status = 'published'. Both are lines of SQL, not architecture changes. CREATE INDEX CONCURRENTLY idx_posts_user_status_created ON posts (user_id, status, created_at DESC); CREATE INDEX CONCURRENTLY idx_posts_published ON posts (created_at DESC) WHERE status = 'published'; Background jobs: get them off the request path Lovable scaffolds nothing here. By 10K users you need scheduled cleanups, invoice generation, email sends, webhook fan-out, async AI inference, search indexing. None of those should sit on a user's request. Three credible paths, depending on the job shape: ToolCurrent cost shapeBest forLimit to respectSupabase Cron + pg_cron + Edge Functions$0 inside the stack, plus normal Supabase usageCleanup, refresh materialized views, low-volume webhook fan-out8 concurrent jobs recommended, 10-minute job guidance, pg_cron can use up to 32 DB connectionsTrigger.devHobby $10/mo, Pro $50/mo, plus run and compute usageTypeScript-native retries, schedules, queues, fan-outPlan concurrency, queue, rate, schedule, and retention limitsInngestHobby $0 with 50K executions and 5 concurrent steps; Pro starts at $75/moEvent-driven durable functions and AI pipelinesFree tier is tight for busy production workflows For most teams the right shape is pg_cron for the in-database hygiene jobs (refresh views, expire sessions, archive rows) and Trigger.dev or Inngest for everything that needs retries, backoff, or DAGs. Supabase Edge Functions remain a strong default for LLM proxy calls and webhook handlers that return quickly. Current hosted limits are not a "150-second CPU wall": paid projects list a 400-second worker wall-clock duration, 2 seconds of CPU time per request, and a 150-second request idle timeout. If the job needs durable retries, a queue, or minutes of CPU-bound work, use a real runner. The 12 mechanical fixes Run these in order. We have used this exact list to harden three Lovable codebases this quarter, all of which stayed on Supabase. Send this list to the engineer who owns your Supabase project and ask for a before/after slow-query screenshot. If they cannot produce one, you are still guessing. #FixWhy1Wrap every auth.uid() and auth.jwt() in (SELECT auth.uid())179ms -> 9ms in the simple case; bigger wins in compound policies2Index every RLS column and every foreign key with CREATE INDEX CONCURRENTLYPostgres does not auto-index FKs3Move all server-side DB access to Supavisor port 6543 (transaction mode)Direct backend connections stop being the first bottleneck4Replace select('*') with explicit columnsSmaller payloads, fewer disk reads5Replace .range() deep pagination with cursor-based .lt(orderCol, lastSeen).limit(N)Avoid the 1,000-row PostgREST cap and OFFSET cost6Replace N+1 client calls with relational embeds: select('id, title, author:profiles(name)')One round trip instead of fifty7Move dashboard aggregates to materialized views refreshed via pg_cronPrecompute the expensive work8Add Upstash Redis or ISR caching in front of read-heavy public endpointsRepeated public traffic hits cache per path, not Postgres9Move background work off the request path, pg_cron in-DB, Trigger.dev/Inngest off-DBRemoves the long-job-blocks-short-job pattern10Bump compute from Micro to Small or Medium (usually +$5-$50 net after compute credit)Last fix, not first, software fixes first11Turn on PITR ($100/mo)At 10K users a corrupt write is a business event12Turn on pg_stat_statements and index_advisor, review weeklyThe slow-query log is your scaling dashboard That is the entire program. Most teams complete it in 1-2 weeks of senior engineering work. Stay or leave: the honest verdict For roughly 95% of teams at 10K MAU, the right call is stay on Supabase and harden it. The math: A realistic operating range is $150-$250/month, not a ceiling: Supabase Pro, Small or Medium compute after the $10 credit, PITR, low-usage Redis, and either Trigger.dev Hobby/Pro or Inngest Pro depending on job volume. That does not include Vercel usage, SMS or phone MFA, log drains, read replicas, observability tools, AI inference, storage growth, image transformations, or paid job-runner overages. That is well under the implicit $500-$1,000/month cost of a part-time DevOps engineer maintaining a self-hosted stack. You keep Supabase Auth, Storage, Realtime, and Edge Functions. None of those are trivial to reproduce. Pebblely proves the platform can survive much more than this; your bottleneck is probably policy, query, and pooling hygiene. The migration path is mechanical, not architectural. RLS rewrites, index adds, pooler switch, caching layer. Leaving Supabase is justified when the reasons stop being about scale and start being about strategy: Your monthly bill consistently exceeds $500-$1,000 and is dominated by compute, not features. You are paying for a big instance, not for the platform. You have workloads Supabase does not do well, heavy analytical OLAP, sustained high-write workloads where the metrics point to a different architecture, regulated industries beyond what the Team tier covers, or hard lock-in concerns at the board level. You have outgrown PostgREST and want first-class GraphQL or gRPC. If you do leave, the typical destinations are AWS RDS, Neon, Crunchy Bridge, or a self-hosted Postgres on Hetzner with Coolify. Raw VM spend can look cheaper around $150-$200/month, but total cost usually does not cross over until much later because the move adds 5-10 hours per month of DevOps work to someone's plate. We have run that migration; we usually do not recommend it before $500/month. The decision tree is short. If your bill is under $250/month and your problem is latency or outages, harden. If your bill is under $500/month and your problem is feature gaps, harden and add the missing piece (Upstash, Trigger.dev, a read replica). If your bill is over $500/month and dominated by compute, or you have a strategic lock-in concern, plan a migration, and do not start by ripping out Supabase Auth. What to do this week Pick the worst-performing query in your Supabase dashboard. Wrap its auth.uid() calls in (SELECT auth.uid()). Add the missing FK index. Switch one Vercel Function to port 6543 and watch both backend connections and pooler-client counts. Measure the difference. You will probably buy yourself another six months of runway in an afternoon. If you would rather hand the audit to a team that has done this twelve times, we run a one-week scaling-readiness audit on Lovable + Supabase codebases, RLS rewrite plan, pooler config, caching plan, background-job plan, cost range, and the migration call, delivered as a PR-ready checklist. That is what our engineering practice does. Book a call and we will look at your slow-query log together. The default Lovable + Supabase stack is genuinely good. It just was not configured for the user count you have now. Fix the twelve things above and it will carry you to the next milestone. --- ### $15,000/month on Heroku to $1,000 on bare metal: how we migrated a 15M-device platform URL: https://appssemble.com/blog/15000month-on-heroku-to-1000-on-bare-metal-how-we-migrated-a-15m-device-platform In February 2026, Heroku quietly published a blog post announcing it was moving to a "sustaining engineering model." No new features. No new enterprise contracts. Security patches and maintenance only. If you've been in tech long enough, you know what that means. It's the stage before end-of-life. The product isn't dead yet, but Salesforce has stopped investing in its future.We'd already left by then. About a year earlier, we looked at our $15,000 monthly Heroku bill, looked at what we were actually getting for it, and decided to move our entire production platform to self-hosted infrastructure on Hetzner Cloud. Two engineers, two weeks, zero downtime. Our monthly bill dropped to around $1,000 and we ended up with roughly 10x the performance.This is the full story. How we made the decision, what we built to replace Heroku, what broke along the way, and what we'd tell you if you're sitting on a growing Heroku invoice right now and wondering what your options look like.Why we leftWe run a deep-linking and attribution platform that handles about 15 million devices. The backend is Rails, PostgreSQL for the database, Redis for caching and job queues, and Sidekiq for background processing. It's a standard SaaS architecture. Nothing unusual, nothing that should cost $15,000 a month to run.But on Heroku, it did. The breakdown was roughly: performance dynos for the web layer because standard dynos couldn't keep up with our traffic. A premium managed Postgres plan because we needed more connections and wanted some level of replication. A Redis add-on because Heroku doesn't include Redis. Then logging, monitoring, and a handful of smaller add-ons on top. Each one seemed reasonable when we added it. Together, they added up to a number that stopped making sense a long time before we actually did something about it.The cost was bad, but it wasn't the breaking point. The real problem was that Heroku's managed services were actively getting in our way.We wanted to set up a delayed database replica. The idea is simple: a second copy of your database that applies changes with a time lag, say two hours. If someone ships a migration that drops the wrong table or corrupts data, the replica still has the clean version. You catch it, you recover from the replica, you go on with your day. It's a basic safety net for any production database. Heroku didn't offer it at any tier.We wanted connection pooling we could actually tune. Our Rails app opens a lot of database connections, and Heroku's managed Postgres was always tight on connection limits. We knew PgBouncer would fix this, but Heroku gave us no way to configure it properly. Their connection pooling was a black box with settings we couldn't change.We wanted control over our backup schedule and retention policy. Heroku gave us automated daily snapshots with limited retention. That's fine for a side project. For a platform handling millions of devices and processing thousands of events per second, we needed point-in-time recovery. The ability to restore the database to any specific moment, not just last night's snapshot. Heroku didn't offer that.Every time we hit one of these walls, the answer was the same: upgrade to a more expensive plan that still didn't have what we needed, or accept the limitation. At $15k a month, "accept the limitation" stopped being a real option.Why Hetzner and not AWSWhen you tell people you left Heroku, the first question is always "so you went to AWS?" We didn't. Here's why.AWS pricing is famously unpredictable. You spin up some EC2 instances, add an RDS database, put an ALB in front, enable CloudWatch logging, and suddenly you're getting invoices with line items you didn't know existed. Egress fees are the classic gotcha: every byte of data that leaves AWS costs money, and for a platform serving millions of API requests per day, that adds up fast.But the bigger issue is that AWS managed services are the same model as Heroku, just with more knobs. RDS gives you a managed Postgres database. It's more configurable than Heroku's, but you still don't have full control. You still can't SSH into the box. You still pay a premium over running Postgres yourself. ElastiCache is managed Redis with the same tradeoffs. You're paying for convenience and giving up control, which is exactly what we were trying to get away from.Hetzner is a different proposition entirely. Dedicated cloud servers at a flat monthly rate. A server with 8 vCPUs and 32 GB of RAM costs a fraction of what the equivalent EC2 instance costs. No egress fees worth thinking about. No surprise bills at the end of the month. European data centers with solid connectivity. We know exactly what we'll pay every month and it's the same number whether we push 100 GB or 10 TB of traffic.For a company that just spent a year watching an infrastructure bill climb from reasonable to absurd, the predictability alone was worth the switch.What we builtThe entire infrastructure is defined in code. Terraform provisions the servers, networks, load balancers, firewalls, and DNS records on Hetzner Cloud. Ansible handles everything on top of that: installing and configuring PostgreSQL, Redis, the application servers, monitoring, backups, cron jobs. It all lives in a single git repository. Changes go through pull requests just like application code. If we needed to rebuild the entire production environment from scratch tomorrow, we could do it in under an hour.That alone was a major upgrade from Heroku. On Heroku, our infrastructure was a collection of add-ons, config vars, and settings scattered across a web dashboard. There was no way to version it, diff it, review changes, or reproduce it reliably. If something went wrong with the configuration, figuring out what changed and when was mostly guesswork.Compute layerFour application servers sit behind a Hetzner load balancer that handles HTTPS termination and distributes traffic with round-robin routing. All four servers are on a private network. The load balancer is the only component with a public-facing IP address. The database, Redis, and everything else are only accessible from inside the private network.Adding capacity is straightforward. We have an Ansible playbook that provisions a new app node, configures it, and adds it to the load balancer. If traffic spikes and we need a fifth or sixth node, we run the playbook. It takes about ten minutes.DatabaseThis is where most of the engineering effort went, and for good reason. The database is the thing you can't afford to get wrong.We run PostgreSQL 16 on a dedicated server with 8 vCPUs and 32 GB of RAM. In front of it sits PgBouncer for connection pooling. This turned out to be more important than we expected. Rails applications can be aggressive with database connections, and on Heroku we were constantly bumping into connection limits. With PgBouncer, we control the pool size, the timeout behavior, and the queuing strategy. Connection limits stopped being a problem overnight.Behind the primary sits a streaming replica on a separate server. The replica receives every write the primary makes, but applies them with a two-hour delay. This is the single most valuable thing we built that Heroku never offered us.Here's why the delay matters. Say someone ships a database migration on a Friday afternoon. The migration has a bug. It drops a column it shouldn't have, or it updates rows with the wrong values. On Heroku, you'd notice the damage, panic, and file a support ticket to restore from last night's backup, losing up to 24 hours of data. With our setup, the replica still has the clean data for up to two hours after the bad migration ran. We catch it, we promote the replica, we're back in business with minimal data loss.If the primary server goes down entirely, whether from hardware failure or something else, we have a single Ansible playbook that promotes the replica to primary and moves the application's database connection to point at it. We've tested this in staging multiple times. The failover takes about a minute, and we have a matching failback playbook to restore the original primary once the issue is resolved.Backups and disaster recoveryBackups are handled by pgBackRest, which is the gold standard for PostgreSQL backup tooling. Our schedule: one full backup per week, incremental diffs every day, and WAL (write-ahead log) files streaming continuously to Hetzner's S3-compatible object storage.What this means in practice is that we can restore the database to any point in time. Not "some time last night" but "Tuesday at 14:37:22." If something goes wrong, we pick the exact moment before it happened and restore to that point. The backups run automatically on a timer and we have monitoring that alerts us if a backup is late. If no backup has completed in 24 hours, we get a Slack warning. If it's been 36 hours, the alert escalates.Between the delayed replica and the point-in-time backups, we have two independent ways to recover from almost any failure scenario. That's more redundancy than Heroku ever gave us, and it costs a fraction of the price.Monitoring and alertingWe use two layers of monitoring.For application-level observability, we run SigNoz. It's an open-source alternative to Datadog that handles traces, metrics, and logs in a single dashboard. It does what Datadog does, except it doesn't cost us $500 a month and we own the data. We self-host it, we control the retention, and we're not sending our production telemetry to a third-party service.On top of that, we built a set of watchdog scripts. These are straightforward shell scripts that run every five minutes on every database and Redis server via cron. They check disk usage, WAL file accumulation, replication lag, backup freshness, Redis memory usage, and Sidekiq queue depth. If something crosses a warning threshold, we get a Slack message. If something crosses a critical threshold, the watchdog takes action automatically.For example, if WAL files pile up and disk usage climbs past 80%, the watchdog runs a cleanup without waiting for anyone to respond. If disk usage hits 90%, it runs a more aggressive cleanup. We built this because we got burned once (more on that below), and we decided we never wanted to be in that position again.Every morning at 8 AM, each server sends a daily health report to Slack: uptime, disk usage, backup status, replication lag. It's not fancy. It's not a beautiful dashboard. But it means we start every day knowing whether anything needs attention.Zero-downtime updatesOn Heroku, database maintenance happens during maintenance windows that Heroku controls. You hope they don't coincide with your peak traffic. On our infrastructure, we control exactly when and how updates happen.The process: update the replica first, since it's not serving traffic and is safe to reboot. Then fail over from the primary to the replica, so the replica becomes the new primary. Update the old primary. Then fail back. At no point does the application go down. At no point does a user see an error. The entire process is scripted in Ansible playbooks. No manual SSH sessions, no ad-hoc commands, no opportunities for human error.What went wrongIt wasn't all clean sailing. A few weeks after the migration, we noticed that WAL files were accumulating on the primary database faster than pgBackRest was archiving them to S3. Disk usage was climbing steadily. If we hadn't been watching, the database would have eventually filled the disk and stopped accepting writes. That's the kind of failure that takes your entire application down.On Heroku, this would've been invisible to us. Either Heroku would have handled it silently, or it would have eventually caused an outage and we would have filed a support ticket and waited. On our own infrastructure, we could see exactly what was happening, diagnose the root cause (our WAL production rate of about 16 GB per hour was overwhelming the archiving process), fix the configuration, and test the fix.More importantly, this incident is what led us to build the watchdog system. We took a problem we discovered in production and turned it into an automated check that runs every five minutes. If WAL files start piling up again, we'll know about it in five minutes, not five hours. And if it gets critical, the system will start cleaning up on its own.We also learned the hard way that rebuilding a database replica from S3 backups is too slow for our workload. With 16 GB of WAL per hour, restoring from S3 couldn't keep up. The replica would never catch up because the primary was producing new data faster than the replica could download and apply the old data. We switched to pg_basebackup over the private network instead, which transfers data directly between the two servers. A full replica sync now takes about 20 minutes instead of hours. It's a small operational detail, but it would have been a serious problem if we'd needed to rebuild the replica during an emergency and found out then that it didn't work.These weren't catastrophic failures. They were things we discovered, fixed, and then automated against so they couldn't happen again. Each incident left the system more resilient than it was before. That's the fundamental tradeoff with self-hosting: you encounter problems that a managed platform would've hidden from you, but you also get to actually solve them permanently instead of hoping that someone else will.The resultsInvoice to invoice, the numbers are straightforward:Heroku: $15,000/month.Hetzner: ~$1,000/month.That's a 93% reduction. Same application. Same traffic. Same number of users. And for that $1,000 a month on Hetzner, we're running roughly 10x the compute and memory that Heroku gave us at $15,000. The application is faster because we have more resources and better connection pooling. Response times improved across the board without any application code changes.The migration itself took two weeks of engineering time for two people. At $14,000 in monthly savings, it paid for itself before the first new invoice showed up. Over a full year, that's $168,000 in savings. Over two years, $336,000. For two weeks of work.But the money is almost beside the point. What we gained that matters more:Our disaster recovery is real. A delayed replica that protects against bad deployments, point-in-time backup recovery to any second, automated failover that takes a minute. Heroku gave us nightly snapshots and a support form.Our monitoring catches problems before users do. Automated watchdogs, daily health reports, self-healing for critical issues. On Heroku, we waited for support to tell us what was going on with our own database.Our infrastructure is reproducible. The entire stack is in a git repo. We can rebuild it, review changes, and understand exactly what's running where. On Heroku, our infrastructure was a web dashboard and a prayer.We understand our own system. When something goes wrong at 2 AM, we don't open a support ticket and wait until business hours. We know where to look and what to do about it. That's not a small thing.Should you leave Heroku?It depends on where you are.If you're early-stage, small team, Heroku bill under $500 a month: stay. Heroku still works fine for small applications. The convenience is worth the premium when your entire focus should be on building the product and finding users. You don't need to think about servers right now.If your bill is between $500 and $2,000 a month: start paying attention. Run the numbers. Look at what equivalent servers would cost on Hetzner, or even on a simple VPS provider. You might find the gap is already large enough to justify a move, or you might find it's not worth the effort yet. Either way, you should know.If your bill is above $2,000 a month and climbing: seriously consider your options. At that level, you're almost certainly overpaying for what you're getting. The savings from self-hosting are significant and the migration is less scary than you think.And now there's a new factor to consider. Heroku has officially moved to sustaining engineering mode. No new features. No new enterprise sales. Salesforce is keeping the lights on, but they've stopped investing in the platform's future. Nobody has announced a shutdown date, and Heroku could run in this mode for years. But if you're making infrastructure decisions for the next two to five years, that uncertainty is worth factoring in. Betting your production infrastructure on a platform that has publicly stopped evolving is a risk, and it's a risk that grows with time.The migration itself is not as intimidating as it sounds. For a typical SaaS application with a web server, database, cache, and background workers, you're looking at two to four weeks of focused engineering work. That includes provisioning servers, configuring the database, building the deployment pipeline, setting up monitoring, and testing everything. After that, ongoing maintenance is a few hours a month. Most of it is reviewing alerts and doing periodic updates.If you're thinking about it and want to talk to someone who's been through it, we're happy to help. We've done this migration ourselves and we've helped other teams do it too. No pitch, just a conversation about whether it makes sense for your situation. --- ### Beyond Generic AI: The Power of Custom AI Solutions for Startups URL: https://appssemble.com/blog/beyond-generic-ai-the-power-of-custom-ai-solutions-for-startups With proprietary AI, startups can streamline operations, enhance customer experiences, and safeguard sensitive data within their own ecosystem. Just as the launch of the iPhone in 2007 transformed the tech landscape by making mobile apps a staple of everyday life, we're now witnessing a similar revolution with AI technology. Startups and established enterprises alike are eager to harness AI's power to automate tasks, enhance decision-making, and uncover new revenue opportunities. However, achieving success in this new era of AI is akin to the early days of mobile apps—while many will try, only a few will truly thrive. The key to standing out lies in building your own specialized AI solutions rather than relying on generic third-party APIs.The Smart Approach: Ownership and SpecializationAt appssemble, we champion the development of bespoke, in-house AI models tailored specifically to your company's needs. Why is this approach so effective? Let’s break it down:Tailored Performance: Imagine you're running a customer support chatbot for a highly specialized industry, like legal services. A generic AI might answer general questions but struggle with complex legal queries. By developing a custom AI model trained on your specific data, you ensure that it understands the nuances of legal jargon and provides accurate, context-aware responses. This bespoke model performs far better than a one-size-fits-all solution.Cost Efficiency: Using generic AI models often means paying for processing power that isn’t always used. For instance, if you're using a broad AI model for tasks like simple data entry, it might waste resources on complex features it doesn’t need. A specialized model focused solely on data entry tasks will be more efficient, saving on computational costs and reducing overhead.Full Ownership and Intellectual Property: When you create an AI model in-house, you retain complete control over the technology and its development. This ownership not only strengthens your IP portfolio but also makes your company more attractive to investors who value unique, proprietary technologies.Data Security: Handling sensitive data? A custom AI model ensures that your data stays within your own system, minimizing risks associated with data breaches or compliance issues. For example, if you're working with patient data in the healthcare sector, having a specialized AI that processes this information internally avoids potential privacy concerns associated with third-party services.The Current Trend: The Allure and Risks of AI APIsMany startups opt for popular AI APIs like OpenAI’s GPT or Google’s Gemini because they offer powerful capabilities right out of the box. These APIs provide a quick way to integrate AI features without needing an extensive in-house team. However, there are notable risks to this approach:Lack of Customization: Third-party APIs are designed for general purposes. If your startup needs an AI to perform a unique task, such as detecting fraudulent transactions in financial data, a generic API might not meet your specific requirements. The result? Less effective solutions that may not fully address your problem.Pricing Volatility: API costs can be unpredictable. As your user base grows, so does the cost of API usage. This can lead to escalating expenses that impact your bottom line. For example, a startup using an API for real-time language translation might face significant cost increases as their volume of translations rises.Limited IP Ownership: When building on someone else’s API, a large portion of your product's intellectual property isn’t yours. This can be a drawback when seeking investment or building a long-term strategy. Investors often prefer companies with proprietary technologies that differentiate them in the market.Data Privacy Concerns: Using third-party APIs means sending your data to external servers. In regulated industries like healthcare or finance, this can pose compliance challenges. If a third-party API handles sensitive customer data, you might face legal repercussions if there’s a data breach or non-compliance issue.Additionally, tech giants can alter or discontinue APIs without notice, potentially disrupting your business. Imagine relying on a key API for your startup’s core functionality, only to find it suddenly unavailable or changed in a way that impacts your product's performance.Why Hyper-Specialized AI Models Are the FutureBuilding a hyper-specialized AI model offers distinct advantages:Enhanced Performance: Custom models trained on your data excel at solving specific problems. For instance, if your business involves complex supply chain management, a tailored AI model can optimize routes and predict disruptions better than a generic model designed for broader applications.Operational Efficiency: Specialized models are optimized for specific tasks, requiring fewer resources and resulting in lower operational costs. This efficiency translates to more cost-effective AI solutions that align with your budget.Stronger IP Position: Developing in-house models adds to your company's IP portfolio, reinforcing your competitive edge and attractiveness to investors.Improved Data Security: With full control over your AI, you can ensure data privacy and compliance, crucial for industries dealing with sensitive information.At appssemble, we leverage small, highly-skilled teams to build these specialized AI models efficiently. Our approach ensures that every aspect of development—from design to implementation—is handled seamlessly, delivering high-quality results without unnecessary delays or handovers.In conclusion, while the allure of third-party AI APIs is strong, the future of AI development for startups lies in owning and specializing in your AI models. This approach not only enhances performance and efficiency but also strengthens your market position and safeguards your data. As we continue to innovate and refine our strategies, remember that building your own tailored AI solutions might just be the key to unlocking your startup’s full potential. --- ### Reimagining Software Development Services for SMEs: Breaking Free from Broken Models URL: https://appssemble.com/blog/reimagining-software-development-services-for-smes-breaking-free-from-broken-models Outsourcing challenges with inflated headcount costs find resolution in a software-based payment model. In today's business landscape, companies, regardless of size or industry, often turn to external assistance to develop their software products. This typically involves engaging software outsourcing companies. The motivations for seeking such help vary, ranging from a lack of in-house technical expertise to cost reduction, the need for rapid delivery, or a desire to avoid coordinating with multiple entities for different project components (design, development, testing, etc.).In a significant number of cases, these providers don't charge for the end product, instead, they bill based on headcounts or hours worked. This billing model is driven by the complexity of projects or undefined requirements.This leads to negative outcomes for the client, especially for small and medium-sized companies.Why typical software outsourcing is broken?Opposing Interests: Provider vs. ClientWhen working on a time and material basis, the interests of the provider are not in sync with the interests of the client.The client's interests are:Develop a product, that fulfills all the functional and non-functional requirements as fast as possible;Do it as cheaply as possible (without hindering the quality)Have someone being accountable for the good functioning of the developed solution;Implement the easiest, most efficient solution (cost, time, and complexity wise);Spend the minimum amount of time managing the project;While the outsourcing agency (provider) interests are:Have a long-term contract with the client, that spans many months or years;Implement complex solutions that require more staff to build and maintain;Increase the headcount as much as possible to get more revenue (and complexity);Be as less accountable as possible for the overall success of the project;Working under this model essentially means renting people for the job. The provider has little incentive to ensure the right fit for the client's needs or implement the most efficient solution. Consequently, proposed solutions are often complex, requiring more time, personnel, and maintenance. This strategy justifies increasing the headcounts and extending the deadlines.Furthermore, clients handle project management, being accountable for any shortcomings. Additionally, software agencies tend to "borrow" more expensive personnel. Coordonation and communicationIn this model, clients actively participate in daily aspects of product development, including team communication, task assignments, and progress tracking.While this hands-on approach can make clients feel more in control, it comes with a significant drawback. In software outsourcing, working in 2-week Agile sprints is the norm. In this way of working only 6 out of 10 days are dedicated to actual product development. The remaining time is eaten up by synchronization meetings and fragmented intervals. This means the client, despite being deeply involved daily, is only getting a 60% return on their investment.When considering the time needed to manage the outsourcing team, the overall results are less than optimal. Despite the apparent advantages of frequent interaction, the model's efficiency takes a hit due to the substantial time spent on constant coordination. Why is the time and materials model popular in software outsourcing?This approach and work methodology may find a fit within larger enterprises. Their projects typically involve revamping existing systems, making enhancements, or frequently maintaining running legacy products.Even in new product development scenarios, their processes and slow decision-making significantly deter delivery speed.Choosing a time and materials approach gives these enterprises a false sense of project control. This leads them to deeper involvement in day-to-day development operations.Here's the catch — software outsourcing companies often replicate this approach across the board, catering to clients of all sizes, whether big or small. By doing this, they transform from technology-focused entities to resembling human resource agencies. Their primary objective shifts from delivering outstanding software products to maximizing headcount sales.This paradigm may align with the needs of large enterprises, but it becomes counterproductive for the agility required by small and medium-sized companies and for building products in general.What is the solution?Let's step back and recognize what clients truly want: fast delivery of products meeting both functional and non-functional requirements, that avoid unnecessary complexity, and are aligned with their roadmap.Instead of compensating outsourcing companies based on headcounts and billable hours, a more effective approach is to pay for the actual software products delivered. This shift tackles many of the previous challenges.By using this strategy, the product costs are clearly stated and delivery dates are adhered to. Additionally, it motivates the software agency to deliver more efficient, and less complex solutions, quicker.Benefits of this approachThe burden of project accountability shifts from the client to the provider. Clients are tasked only with specifying requirements and validating the result. They are no longer burdened with staffing issues, day-to-day project management, or decisions regarding the team's size to meet agreed deadlines.A frequently overlooked benefit of this approach is that software agencies are motivated to deploy their most experienced personnel, usually seniors, to expedite project delivery and move on swiftly to the next challenge. This results in a better-architectured product, fewer bugs, and an overall better, more stable product.Now a sensible thing to think and to worry about, is: what if you don't have all the requirements of the product? What happens then, can this approach still be implemented?The best thing to do is start small (some part of the product -- for instance a login flow, something that's clear) and expand from there. The selected software development partner should understand the product roadmap, its goals, and key functional and non-functional requirements. This ensures the built solution is flexible and extensible to meet these needs.This approach prompts clients to consider budget allocations for specific features. This enables better decisions on how much they want to invest in a particular feature and whether it is truly necessary. Additionally, it offers a cost-effective way to evaluate a provider's working style and service quality before committing to a long-term partnership. This principle holds even, when the product is fully specified with all requirements defined. To understand how we build better software faster and with less hassle for our clients, explore more about our process and approach. --- ### All about Software As A Service Development URL: https://appssemble.com/blog/all-about-software-as-a-service-development Everything you need to know (From Planning To Design, Building, Testing, Deploying and Managing) about Software-as-a-Service (SaaS) Development. What is SaaS App Development?Software-as-a-Service (SaaS) is a software licensing and delivery strategy that has largely replaced the old software method of providing a software product or service just once. SaaS is a popular model since it provides ongoing revenue in the form of monthly or annual subscription payments.Major corporations are pouring money into their SaaS platform development teams in order to reap the benefits of SaaS-based platforms. Many new issues arise with SaaS development, such as a need to comprehend cloud technology and how to provide a quality service at scale to consumers without requiring significant downtime to offer fixes and upgrades.Why SaaS?Because of the numerous benefits it provides, the popularity of SaaS-based software is steadily growing. If your company is considering building software, creating a SaaS solution may be the best alternative. An established software firm may be changed to a SaaS model in some cases without disturbing your existing client base.As you may be aware, SaaS apps are hosted in the cloud and do not require installation, with the software firm handling upgrades and maintenance. The SaaS product is not offered with a perpetual license, it is rather given to consumers through a subscription approach.When comparing SaaS vs. online apps, there are sometimes miscommunications. Software as a service (SaaS) is a more precise idea and approach for software licensing and delivery. Using cloud-based technology and storage, anybody may create SaaS apps on a shoestring budget.TrendsSoftware-led growth: Product-led SaaS firms often provide a free trial, or freemium revenue model, that allows users to test their product with the goal of keeping these customers after their trial period expires. Customers will gladly upgrade to the premium version if they believe the service is valuable enough.Micro SaaS: Micro SaaS is becoming more popular. Companies find a particular problem in a specialized market and address it with little resources.Tools for low-code development: Low code platforms provide customers with a development environment in which they may create software and new components using a graphical user interface (such as drag-and-drop functionality). This is the polar opposite of the typical approach to building sophisticated code.SaaS collaboration tools: As remote work has become the norm, the usage of collaboration tools has increased dramatically. Slack, Zoom, and Confluence have become indispensable for firms that conduct their operations online. This trend is expected to continue as more businesses adopt remote employment.Advantages and Disadvantages of SaaS AppsAdvantagesCost efficiency: Because SaaS is fully cloud-based, it can give significant cost reductions. This means you simply pay for the amount of data and bandwidth consumed, and you don't have to invest in your own costly server network.Accessibility and speed: Application deployment has never been easier in terms of speed and accessibility. Cloud applications can be deployed more quickly, shortening the time to market for your product or service. And your consumers may use any internet-connected device to access your service.Flexibility: A SaaS business model allows you to create, alter, and update code with ease, whether you're adding new features or boosting security.DisadvantagesSecurity: Strong endpoint security is required for SaaS authentication. Businesses are required to secure consumer data and, as a result, they must keep their SaaS product up to date with the most recent security procedures.Competitors face a low barrier to entry: A rival may be able to mimic your SaaS service. Because most SaaS transactions are subscription-based, you must continue to give greater value than your rivals while also up-selling to the next subscription level once clients are aboard. If a client is unsatisfied with the services or support, they may simply switch on to a rival with a comparable price structure without having to make a greater upfront commitment as with other software sales. One illustration of this circumstance is the enormous number of SaaS firms that provide VPN services.Converting and retaining customers: Depending on your SaaS service offering, it might take anything from a few minutes to many months to convert a prospect into a client. Effective SaaS account management involves both minimizing the conversion process, and increasing the length of time a customer is a paying customer.SaaS Development Stages1. PlanningThe first stage of the SaaS software development life cycle is conceptualization. This is when you do your research and collect all of the project's requirements, as well as define the project's objective, result, and related goals.Controls for these operations are often built on a mix of security, confidentiality, availability, processing integrity, and privacy principles. You must determine who your service's intended audience is. What interaction will they have with your SaaS product? You must create a service that meets the specific demands of this audience.A company may simply integrate SaaS platforms, marketing solutions, eCommerce platforms, CRMs, and social apps that are vital to business operations by using connectors. Connectors adhere to all API regulations, approvals, and data processing settings, and once established, you may reap several SaaS application connection perks.Even if the technology and idea are strong, choosing the wrong SaaS operating costs might be the death of the firm. Finally, you must choose the most appropriate SaaS pricing methods for your platform.2. Design & PrototypeThis is the stage of your SaaS design. Investigate how to create the software as a service and best practices for SaaS application architecture. There, for instance, you may choose between single-tenant and multi-tenant architecture.A single instance of the program and its associated architecture is dedicated to a single client. Each customer will have their own separate database and instance of the program with the single tenancy. The term "multi-tenancy" refers to the fact that a single instance of the program and its supporting infrastructure serves numerous clients.At this time, you should consider generating a SaaS architectural diagram to assist others to comprehend your design more readily. Along with being concerned about SaaS application security, you should also be concerned about the SaaS cloud security provided by your cloud service provider. Examine their security policies carefully to determine which service is right for you.At the end of this step, you may begin assembling a tiny prototype to confirm that your connectors, database choices, and cloud provider all operate as expected and result in a viable prototype SaaS implementation. This is how a SaaS application is designed.3. Building & DevelopmentNow it's time to build your service and write some SaaS code!Before you start writing code, make sure you have the essential components in place:You should be familiar with the SaaS database architecture that you want to use.You should identify which SaaS cloud providers you'll be using and how much they'll bill you for your anticipated consumption.You should have a software team set up, ideally one that specializes in SaaS development.And lastly, at this point in the SaaS development life cycle you should have a prototype in place.With everything organised, your team can produce the product or service to your precise specifications and requirements. Use your preferred project management software to guarantee that the project stays on schedule and that developers follow SaaS best practices.Creating SaaS apps may take a long time and is an ongoing effort. The time necessary to accomplish this stage is heavily dependent on the experience of your developers and whether they have a prior understanding of how to create SaaS apps.4. TestingMany of the key ideas of software testing apply to SaaS application testing as well. SaaS testing is a software testing procedure that involves evaluating a software application designed in a Software-as-a-Service paradigm for both functional and non-functional criteria.SaaS testing ensures the quality of the SaaS-based application by assessing data security, integrity, performance, interoperability, and scalability. This includes testing your cloud-based architecture and ensuring you have a framework for measuring SaaS performance metrics.The goal of cloud study is to check software for both functional and non-functional criteria utilizing cloud computing, which offers quicker accessibility as well as scalability and flexibility to save time and money on software testing.5. DeployingYou have created and fully tested your solution at this point in the SaaS product development lifecycle. It is ready to go!Major cloud service providers such Microsoft Azure, AWS, Alibaba Cloud, Google Cloud, IBM Cloud, and Oracle have SaaS solutions. You may easily join up for your favourite provider if you have a hot new infrastructure and system.When it comes to developing a SaaS platform, one of the most difficult challenges is migrating current IT/application infrastructure from on-premise to cloud, or cloud to cloud. You will need to move to these cloud services, and there are several sorts of migrations to be aware of because any of them might apply to your existing situation:Physical-to-virtual (P2V): This means disconnecting and transferring a physical server's operating system, programs, and data to a virtual server guest hosted on a virtualized platform.Physical-to-cloud (P2C): This refers to the process of migrating tools and data from traditional infrastructure or on-premises data centres to the cloud.Virtual-to-virtual (V2V): This migration involves copying a current virtual machine operating on a virtualization platform to another virtual machine running on another virtualization platform.Virtual-to-cloud (V2C): This is the point at which you transition from a virtual machine to a club-based solution.6. MaintainingDuring the maintenance phase, developers look for flaws or problems in the program. If they discover one, they file a bug report. It is critical to explore opportunities for when the development cycle begins again.When developers can swiftly discover and handle problems, it indicates that this phase is going well. Your attention should also be drawn to gathering customer input and developing ways to improve your present service. This is a must for SaaS since competitors can imitate your product and take market share.Optimize your SaaS application development platform gradually to minimize time to ship and improve release flow. You must always seek to improve your offering.7. OptimizingThis is the final step of the SaaS development process, and it entails upgrading and optimizing your service and SaaS application design to maintain a competitive advantage. Evaluate your present procedures and compare them to best practices for SaaS development.You will discover that optimization may occur at several levels, including code, technology, SaaS architecture, people, knowledge, and so on. These factors may be optimized to improve the outcomes of your SaaS-based application development process and, eventually, your business.To preserve a competitive advantage, you must continue to innovate in your own sector or business.SaaS Development TeamAfter you’ve decided to build a SaaS app and your SaaS app development framework is already in order, you might find yourself in a place of uncertainty and ask yourself, “Who exactly do I need to build this app with?”. We are here to explain what talents your team needs and at what stage you should consider hiring them:Project ManagerWhen it comes to day-to-day management of the project, you need a competent Project Manager. He should be quick to handle all aspects of the plan, from the schedule, finance, risk, quality, to resources.They need to be one of the first hires and be informed of the detail on the background, context and scope of your project. appssemble supports your journey from the Consulting stage to Design and Engineering.Business AnalystThrough data analysis, business analysts assist firms in enhancing processes, goods, services, and software. Business analysts work as a bridge to the gap between IT and the business in order to enhance productivity.Business analysts may assist in the initial planning stage of SaaS applications by generating requirements. They can also be highly beneficial throughout the optimization process. They should be proficient at turning user feedback into improvements.UI/UX DesignerUX (User Experience) and UI (User Interface) design are distinct components of a single user experience. A UX designer ensures that a product makes sense to the user by developing a route that flows logically from one step to another. A UI designer ensures that each page graphically conveys that path.UI/UX designers are often hired at the design phase of the software development life cycle (SDLC). So listen to your users to uncover opportunities and turn your target market into customers and customers into fans by hiring the ones that are good for your project.Backend DeveloperThe term "backend development" relates to server-side development. Databases, scripting, website architecture, and then ideally, all SaaS-based application architecture are covered. It describes the processes that take place behind the scenes when a user performs an activity on a website. It may be logging into an account or making a purchase from an online business.Backend engineers provide code that allows browsers to interface with your data warehouse and cloud provider. Backend developers should be employed early on in the design process since they will need to be advised on the design of your backend.Frontend DeveloperA frontend developer connects the worlds of design and technology, packaging up the usefulness of the backend in an appealing way for people to engage with, web or mobile (Android and iOS).QA EngineerA quality assurance engineer is responsible for enhancing software development processes and preventing production faults. They develop test strategies, track defects, and find opportunities for improvement in your program.During the SDLC testing step, you should recruit a QA engineer. Even if you are developing SaaS quickly, you should budget time and money to engage with a skilled QA engineer to identify the most susceptible sections of your service.Apart from these, make sure you go through our advice guidebook for all startupsbefore you start your own journey, and build something that you’re sure will be successful.In-House, Outsourcing or Remote Development?In-HouseWithin your own workplace, state, or nation, you may hire or assemble a team of developers (either as full-time employees or as contractors). Due to the time-consuming nature of interviews, onboarding processes, and coaching, having an in-house development team may necessitate extra time and money. However, it has certain distinct advantages over outsourcing and remote choices.OutsourcingOutsourcing is another option for developing a SaaS application. This is the stage at which you employ an outsourcing business to manage the full SaaS delivery process, from idea to development to maintenance. But how do you make sure to avoid bad mobile development agencies for your app? See here.Remote DevelopersYou may hire and manage a remote team of app developers (full-time or part-time) to construct your SaaS application.With certain firms committed to assisting you in building a team of remote developers, finding remote developers has never been easier. Let's go over the benefits and drawbacks of utilizing remote developers to construct SaaS services.Do you have a project for us?We assist startups all over the world in fulfilling their mobile app ambitions. With strong, agile teams in Startup Consulting, User-Centric Design, Experienced Engineering and focused QA Procedures, we deliver consistent, high-quality and cost-effective products. Our professional staff can assist you with accurately identifying your requirements, selecting the technology and framework required to construct your app, customizing the app to meet your needs, updating and maintaining it regularly.We're here to help if you're not sure where to begin your startup or your mobile app, therefore make sure to contact appssemble www.appssemble.com. Let’s build your desired app. Get in touch to share your idea or to request a free consultation. --- ### How to come up with good startup ideas URL: https://appssemble.com/blog/how-to-come-up-with-good-startup-ideas Generating a startup idea is difficult, and it requires many standards. Here’s how to find the right idea or measure it. This is tricky since startup ideas are subtle and nobody knows which will be successful. Certain types of ideas are far more likely to succeed than others. As a result, this article's purpose is to steer you in the right direction.This is how it will go. First, we'll show the most common mistakes founders make when coming up with startup ideas. Then, we're going to talk about how to check startup ideas. Then we're going to discuss some recipes for generating startup ideas. And finally, we're going to talk about the 6 principles of creating new things.The most common mistakes founders make when coming up with startup ideas.1. The first and most typical mistake is assuming that you must have a brilliant concept to get started. A lot of people feel that the secret to launching a successful startup is to begin with a fantastic idea. So they're waiting for a breakthrough idea before getting started.2. The second mistake is plunging into the first idea that comes to mind without stopping to think if it's a good idea. And, it's incredible how frequently this happens. Here's the deal. If your business succeeds, you will devote years of your life to it. If so, wouldn't it make sense to spend at least a couple of weeks determining what to focus on first? Consider your first concept a solid starting point. Startup concepts evolve, take, for example, Airbnb. It began as a website for renting air beds in other people's homes. Over time, it evolved into all holiday rentals.So the first thing you should do is choose a decent beginning place. If you do, even if your original concept isn't outstanding, it only has to be improved to become amazing. If you choose a horrible beginning point, there may be no way to evolve into a good one. You'll have to start from scratch.3. The third mistake is, to begin with, a solution rather than a problem. For example, let's say you come up with the business concept "WhatsApp for teachers". It's an app, you press a button, and WhatsApp opens for teachers. This is a workable solution. What problem is this supposed to solve? I'm not sure. The point is that if you come up with a concept like this, you've already started with a solution. It's referred to as a "Solution In Search of a Problem" or SISP. And these are typically bad since you never locate the problem. It's far better to start with a problem and then search for answers.4. The last mistake is assuming that startup ideas are difficult to come by. They're simple to locate, since the planet still has a lot of serious issues to be solved. Remember to find the problem first, not the solution. If you're having difficulty discovering the ideas, it's because you haven't yet learned how to do so. You'll notice fantastic startup ideas all over the place once you understand how to spot them.Evaluating startup ideas1. The first measure is the size of the concept. Looking for current big firms that do something similar is the best approach to test this. You may be working in a market that's tiny now but has the potential to be large in the future. That's a good sign that your concept may perform well here.2. The second measure is how certain are you that you are solving a major problem. You might need to have firsthand knowledge of the issue. Then you should have any fresh, significant insights about this concept.3. To be an excellent one, you need to create something you'd want to have. For the third measure, you start with yourself as the first user. Then, when you're designing for yourself, you can trust your instincts about what to build. In the end, you have to estimate what other people want when you're developing for them.4. The fourth measure is that the idea was recently made workable by another company. If some new technology or a new product in the world has turned towards that subject, it is a good opportunity.5. Our final measures for evaluating company ideas are "filters". These filters are almost universal. One important thing you should do to develop startup ideas is to understand them and how to turn them off.The most dangerous aspect of them is that they might force you to reject your finest ideas. Even before they ever reach your conscious mind. Here are the most common filters:Reject ideas that seem hard to get started. If the idea is in a dull or too competitive space.If the idea seems too ambitious.Founders instinctively shy away from spaces where there are existing competitors. You should consider the side of doing things with existing competitors. When founders go into spaces with no existing competitors, they soon find out the reason. Because there are no competitors and nobody wants the product. The ideal situation is a market where there are existing competitors. But your advantage is that you noticed something that they all seem to have missed.The 6 tips for generating startup ideas.It is possible to sit down and think about startups. It's, unfortunately, not the ideal technique to develop business ideas.The best way to do so is to watch them develop spontaneously. There are wonderful business ideas all around you, and if you have an open mind, you will notice them. The problem is that when people sit down to brainstorm company ideas, they usually come up with bad ones. So, startup ideas that come to you easily have a higher chance of becoming good.First, let's discuss how to generate business ideas organically. Learn how to spot good startup ideas and then let them come to you. To generate them, you must first understand what a good startup idea looks like. This way you can recognize them when you come across them. Then you should keep an eye out for elements that appear to be missing in the world, and continue from there.If you want to create a business in the future, being an expert on anything useful is beneficial. The best way to do so is to get a job at the vanguard of some industry or try a workshop for startups. If you work at the cutting edge of any subject, you will notice strong business ideas before others.Okay, let's go over the actual 6 tips for coming up with startup ideas. The first is one of the best since it’s most likely to result in solid ideas. You begin with what your team excels at. Consider ideas that you have an unfair advantage in executing. Then, you're essentially coming up with all the ideas that have a solid founder/market fit.For the second piece of advice, consider what you would like someone else to build for you.The third one is, what would you be enthusiastic to work on for the next ten years, even if it failed? What are you truly enthusiastic about?Number four, seek recent changes in the world and consider ideas that now have potential.Number five, seek firms that have been successful lately. You can think of fresh interpretations of them.Sixth, talk to individuals you know and ask them what problems they want to solve. The disadvantage of this formula is that most of them are not good at recognising business ideas.Startup conceptsWanting to develop a business that expands very quick is normal. You're building a small startup, and there's nothing wrong with that.The startup idea is made out of three concepts. The first is the problem, as it is the initial condition. You must describe what the territory is like for this firm that allows it to develop. The solution is the second. What are you performing inside those parameters that allow it to expand so quickly? And the third is, what is your argument? What is your justification for why the product you're about to launch, will be successful?1. The problemHere's a suggestion for discussing and determining whether your problem & conditions are correct. Know that the right problems are in demand and affect numerous people. You want to avoid the ones that a few individuals have.You should like problems that are growing. You should like situations that are urgent and must be addressed as soon as possible. You should like challenges that are difficult to solve because if you can sort them, you can make a lot of money. Then you should like common problems. The ones that individuals will experience again and again, and often in a short period. You must have a lot of motivation, capability, and trigger because they must all emerge at the same moment.2. The solutionThe only advice we have for the solution is the best advice you can ever receive from anyone. And that is, as we've said before, do not start with the solution. Don't begin with a solution before you have an actual problem. When you want to create something new, you might search for some new technology. After that, you can stop and ask yourself, "What problem can I fit into this solution?". Otherwise, you'll realize you went the wrong way and your product is not working or selling.That ends up being a far more challenging approach to expanding the firm. While businesses can develop in this manner, it is inefficient. It's far better to say, "Let me see what difficulties people have, and then I'll take whatever I need to remedy them." As a result, you are much more likely to expand.Look at what you're building right now or look at the reason why you're trying to do this startup. Do you only care about the technology and building something, or have you started with a problem? You need to do whatever it takes to solve users' real issues, not hypothetical ones.3. What’s your insight?You need one, it can't be like, "I have a problem I'm solving" and then have no explanation why. What is the reason why your solution will work and how exactly will you make it work? Here is where a lot of businesses are tricked. Because it's always about how you profit from your company's advantage, right?Why are you going to triumph over everyone else? Why are you going to be the first to expand? Because that insight is what the investor needs to pick you over everyone else. And it must be tied to growth, you must have an unfair advantage that explains why you will develop fast.Principles of creating new thingsTry to find simple solutions, to overlooked problems that need to be solved. Deliver them as informally as possible, and start with a very rudimentary version. Then iterate them rapidly.Some people can’t recognize new ideas in the beginning. Others who follow this method will almost always do things that appear to be wrong to others. And that is the point. And why is this strategy successful in the long run? Because it gives you all the benefits that other individuals hold back. They do this so they appear legitimate, and they end up losing.There is less competition while working on solving overlooked problems. You are also more likely to discover new things.When you deliver solutions informally, you:Save all of the work that would have been required to make them appear spectacular.Drop the risk of deceiving yourself and your audience.This technique's use extends beyond companies, computer languages, and essays. It will apply to any type of creative effort.New ideas are constantly beneath your nose. So search for basic things that others have overlooked. Things that people will later claim as "obvious". Don't be fooled by norms and the need to be remarkable. Determine the root cause of the problem and work your way up to resolve it. Don't worry, the product will prevail in the end if you follow all the advice. And start as soon as possible so you have time to learn from people what you should improve.Do you need to build a mobile startup and don’t know where to start?Talk with our experts and develop a solution that will provide your company with a competitive advantage. Until the next one, do your research, be confident, consistent, and don’t give up. --- ### What types of authentication to use in your mobile app? URL: https://appssemble.com/blog/what-types-of-authentication-to-use-in-your-mobile-app Your users expect to access your mobile app securely and easy, here are the types of authentication you can use The need for various forms of user authentication systems is increasing. Organizations must recognize that passwords are not the exclusive means of authenticating users. There are several authentication technologies and even more activities that need authentication mechanisms.What Is Authentication?Authentication refers to an electronic technique that allows a person to be identified. It may be used to certify the origin and integrity of data in electronic forms. One example could be the issue of a digital certificate to verify the legitimacy of a website. The general goal of authentication is to decrease the possibility of fraud, particularly when someone misrepresents their identity or uses another person's credentials without authorization.Mobile login flows typesWeb-based or native login processes can be used in mobile apps. It is vital to distinguish between the two:Users submit their credentials into the app when using the native login flow.Users are sent to a web login screen. That's where they submit their credentials when using the web-based login flow.For a better user experience, we suggest adopting the native login flow.Authentication factorsWhen authenticating an internet user, three types of factors may be employed. The reason is to ensure that the user is who they claim to be. These are the factor categories:Knowledge factors include a user's password, passcode, and personal identification number (pin). Here, the user must answer a pre-selected security question.Ownership factors are items in the user's possession. They could be a bank card, a hardware or software one-time password (OTP) token, or a mobile phone.Inherence factors. They are factors that relate to what a user is or does, and they include biometric identifiers. It can be the face, fingerprint, or retinal pattern recognition. Other personal attribute identifiers can be used as well.Types of AuthenticationThe following classification contains the most common kinds of online user authentication. The increasing level of security organizes them:Email & password combinationPasswords were used as a simple means to safeguard information for a long time, almost 50 years. We've been using them to access computers, IT systems, gadgets, and internet services. Passwords were unsafe from the start, and that hasn't changed. We are told to use stronger passwords, to make them unique, to not reuse them, and to change them regularly.Nowadays, most passwords are easy and general. They are based on information that is easily obtained through social engineering. This is why many service providers are abandoning passwords. Many firms expect that they will soon be password-less.SMS two-factor authenticationSMS-based two-factor authentication is old authentication technology. It's not secure enough for storing sensitive information. For a long time, it was thought to be an increased security mechanism, but, that is no longer the case.SMS authentication however can be a viable alternative for startups that don't require a lot of protection on their services, as a rule of thumb, if your app doesn't require storing sensitive data -- such as cards, addresses, etc. SMS authentication is good to go.Third-party authentication appsAnother alternative is to use third-party authentication software. And there are many of them. Some applications provide enough security as long as the user has control of the device. They are pretty horrible from an user experience point of view. Users must switch applications to get the code. Then they return to input it, thus most will avoid doing so and instead opt for lesser security settings.Biometric AuthenticationBiometric authentication is the technique of verifying an individual's identification. It uses a unique bodily trait. For each authentication, the user delivers biometric data. Then the biometric data is compared to the input. This approach was designed to be safe, and it continues to be, as long as it functions well.Although the user experience is positive, biometrics fall short in terms of privacy. Not everyone is ready to use their bodily traits for verification, even if the biometric data does not leave their device.So, what to choose?As a general answer, it depends, sometimes SMS or user/password authentication is enough, and sometimes an extra layer of security needs to be added. Depending on the app, the data is manipulated and stored, and different authentication methods are required.If you're not sure what should you pick for your mobile app, get in touch and our team of experts will offer you the best alternatives for your use case. --- ### Why startups fail: 10 of the most common reasons URL: https://appssemble.com/blog/why-startups-fail-10-of-the-most-common-reasons Here are 10 common reasons why startups fail and how to avoid getting there as a startup founder. We keep on saying that starting a business is a lot harder than most people think. A business is rarely so in tune with its niche that it can fly along with little effort. According to Harvard Business Review, “More than two-thirds of startups never deliver a positive return to investors”. But why do so many startups fail? There are many reasons for this, so here is what you should know before starting your own business. If you ask former business owners, you will get a wide variety of reasons on why their businesses failed. Here are the 5 most common ones:1. Founders didn’t make something people wantNothing is as important as making something that people want. You may be the best at advocating, fundraising, or the best programmer the world has seen. If you don’t come up with a product that people need, you will fail.We have an ongoing piece of advice for those searching for inspiration or startup ideas. (link to ‘Startup ideas’ article). Try and fix an issue that they already have. This way, you can be sure that you're building something that other people need as well. How do you know this will work? Because you are already a part of the targeted market and you will have lots of insights on that subject.Next, if you want to understand what others want, you need to understand your users first. Do they like what you’ve created this far? Why? Or why not? You should spend a lot of time talking to your users. Watch them, observe them, and learn what kind of products they want you to build.As a startup founder, you’re a doctor and the users are your patients. You should always go and talk to your patients. Listen to what they say their symptoms are and what they’re complaining about. So make sure you talk to your users and build things that people want. This way, you’ll avoid the most common way that other startups fail.Not to forget, be willing to change your mind if it’s the right thing to do. Most good ideas change over time. You can even figure more out while having a one-day workshop for startups. But your users are your guiding point and the best way to stay on track. So again, the best way to succeed in the early stages of a startup is to build things and talk to users.2. Founders can’t stay focusedWe follow the first reason with another one about focusing on the product and users. Might sound redundant and self-evident, right? But founders should focus on their product and users to the point of being fanatics. The best entrepreneurs don’t have time to get caught up in other distracting things.Here are a few things that distract founders by thinking they are big priorities:“Grabbing coffee” with investorsChatting with potential acquirersNetworkingRecruiting boards of advisorsDoing a partnership thinking it will generate more usersSpending time on PR before creating a product desired by usersArguing on social media 3. Founders don’t measure their worthIf you build something people want and then stay focused, growth is a natural result. This means you can use growth as a measure to check if your startup is going in the right direction. If your growth rate is at least 10% per month, you’re on the right track. If you’re not, you’re probably missing one of the first 2 elements mentioned before. You’re either building the wrong thing or you’re not focused enough.The guys at Y Combinator taught us a good lesson: “You make what you measure”. Pick a goal number and focus on that. One good metric for measuring your growth is good old revenue. We don’t think there’s another better test to check if you’re making it in or not.Do you know the saying “ignorance is bliss”? Well, it should only apply to your fashion choices. You should not be in denial when it comes to your business, because it might kill your startup fast. Focusing on growth prevents you from living in the denial. A lot of problems you face in your startup might provoke this. Yes, founders tend to make mistakes and then live in denial about it. Founders may waste a lot of valuable time doing inessential stuff and be in denial about it, too. Denial is the silent killer of startups. That’s why you should have growth targets, to get yourself out of this denial. The numbers stare you right in your face this way. You can’t pretend you didn’t know about the difficulties you were having. Look at it this way, numbers may be also good in the end. What other motivation hits better than this?We understand that some issues are hard, and you may be tired. Sometimes you feel like you’ve had enough, or you consider that focusing on growth is not a priority right now. This is the moment that denial sets in. This is also the perfect moment to not let your guard down. Set the goals, stay focused on them, and measure your growth constantly. If you feel like crawling down to cry, then do so for 2 and a half minutes and then get back to work. In the long run, you don’t want this minor setback to be the reason your startup failed.4. Startups ran out of moneyThis is another major reason startups fail. Why does it happen, tho, why do startups run out of money? Simple, because they spend more than they earn. But how can a startup spend so much to run out of funds? Well, a big expense in any business is salaries. So, spending too much money = having too many employees.Making a product nobody wants is the biggest mistake in the early phase of a startup. Overhiring is the second-biggest mistake but in the next phase of a startup. It gives you less margin for error. The amount of time you have to generate a profit decreases when you use up your cash reserves more. Yet, startups are the kind of thing that takes longer to get right than you expect. This is because they are (generally) managed by inexperienced founders. They are also building something novel and that's a lethal mix. If you start to run low on cash at this point, you will need extra funds while in the "ugly duckling" stage. You don't look good right now, even if you are on the right track. Investors generally dislike those kinds of businesses.So, be very conservative with your money expenses. Be somehow pessimistic and assume it will take longer than you think to get things moving. It’s better to be prepared for unforeseen problems than take unnecessary risks. You don't want to gamble on your startup’s future.Now that we saw how fast you can lose money, let’s see how hard it is to gain money.5. Fundraising gets harderHope you didn't think the drama ends when you hit the “ugly duckling” phase. Startups get slammed when they have to raise money from this phase. All because the following rounds of fund raising get so much harder. This is where founders usually try to raise a series A.Series A funding is the first round after the seed funding stage. In this round, it’s important to have a plan that will generate long-term profit. Seed investors are mostly looking for a promise of success. Series A investors on the other hand are looking for performance. They will only invest in you know if they can assess that you’re clear on the path to being a big winner. They are willing to invest a lot if they think so. But will this “ugly duckling” phase make them think you are a big winner? Probably not, so they won’t invest at all. If they don’t see progress, they don’t waste their money.These were 5 major reasons why startups fail. Now let’s see 5 secondary reasons that you should keep an eye on at all times.6. Being in the wrong marketToo many people try to start a business targeting everyone as their demographic. This doesn’t work out well. Next, they try to target everyone in their town. Again, too broad. The more defined your niche is, the easier it will be to market to the right audience.7. A bad co-founder or the lack of oneThis is indeed an issue. It might be a bit too hard for one person to tackle all the challenges alone. Even investors might treat you differently if you’re all alone in this process. But the solution is very simple, get a co-founder. Having a partner is necessary when starting a business. You each have particular knowledge in different fields, with one of you being an expert in each. If your ideas for the business collide, and if there is no clear solution, inner conflict develops. The majority of disagreements can be avoided before they even start. How to do so? Create a detailed company strategy that outlines each partner's responsibilities.8. Bad marketingMarketing and bookkeeping are also two essential components of any startup. What you are offering or selling won't matter if you are not excellent at both. The sad reality is that most business owners are only good at their job, at that's it. If you have the funds for another salary, hire an expert. If you don’t, read more and learn about how to promote your product.9. Not being aware of the competitorsAltough competition is bad for your startup, once an idea gets hot or market validation, others may try to capitalize on the opportunity. And while obsessing over the competition is not healthy, ignoring it is also a recipe for failure.10. Ignoring the “burnout”Startup founders rarely experience work-life balance. Thus, there is a higher chance of burnout and 5% of the time, failure was attributed to burnout. To succeed and avoid burnout, it is necessary to have a strong, varied, and driven team. Founders also need to redirect their focus when discovering a dead-end.Are you ready to become a founder? We can help you succeed!When it comes to managing a startup, we have plenty of experience at this point. That's why we conduct one-day workshops to help founders validate their idea, pick the right feature set, and define the user flows based on timelines, budgets, and goals.The suitable choice of what you require will aid in the efficient use of resources, time, and effort. In turn, appssemble is prepared to maintain and upgrade your app in addition to building it. It’s simple, contact us for further information on how to fine-tune your application with no worries. Tell us what are your ideas, and let’s see how we can help you! --- ### Content creator economy in mobile apps URL: https://appssemble.com/blog/content-creator-economy-in-mobile-apps Learn what the content creator economy in mobile apps is all about. The power dynamics of the creative economy are quickly shifting. Creators are now in the driver's seat, with greater independence than ever before. Examples of content creators are YouTubers and TikTokers. They produce material for their audiences constantly. Today, creator platforms take too many profits away from the creator. They don't allow artists to be discovered through their algorithms.Also, few provide direct ownership where all stakeholders have a financial advantage. All depending on their contributions. Creators are not only the product; they are the new economy.What is the creator economy?Long ago, there was a small number of people who created material and a larger group that 'consumed' it. As new platforms and technology evolved, content took on a variety of shapes and forms.The creative economy is rather vast. It's composed of side hustles, independent companies, social media influencers, bloggers, and videographers. Over 50 million people globally consider themselves independent producers, according to Signalfire.The creative economy also includes a diverse range of businesses providing creators services. Such as content development, online analytics systems, and website hosting.The creator economy refers to the 50 million+ independent content creators and community builders. They create free or paid material, then distribute it to their followers via apps. A combination of factors has resulted in a shift in the ecosystem. Resulting in what is now known as the creator economy.Common app channels for the creator economy include:Twitch for live video streamingYouTube for on-demand video contentInstagram for images and short videosTikTok for short videosFacebook for multi-media contentHow does the creator economy work?The creator economy fosters a network of creators, consumers, advertisers, and other stakeholders. This ecosystem has far-reaching ramifications. From the creation, distribution, consumption, and monetization of material.There are majorly five stakeholders:CreatorsConsumersPlatformBusinessesToolsCreatorsCreators are infopreneurs who generate content that their audiences consume. The material might be educational, entertaining, or motivating. These content makers use their knowledge to generate content. To also grow audiences, and monetize their work.There are four kinds of creatorsBloggers/Vloggers who give guidance or advice on issues for which they are well-known. Fashion bloggers, for example, on what's new in the fashion world.Entertainers who generate content through writing, music, or any other type of art. As an example, consider an artist who shares songs on Soundcloud.Experts and guides who offer their expertise on products, services, and other issues.Existing celebrities use their fame to generate content.ConsumersConsumers are those who consume content. They are the creators' intended audience. Consumers interact with expert-created material. They financially support them or follow their opinion leaders for knowledge and enjoyment.PlatformsPlatforms are third-party services. They assist in the development, distribution, consumption, and monetization of content. Platforms are utilized by both stakeholders to communicate with one another.Platforms deliver value-added services. They generate money through adverts or membership fees. Some well-known examples are YouTube, Instagram, TikTok, and other platforms.BusinessesBusinesses are organizations that want to promote their products and services. This happens through the use of content creators. They target the creators' audience by collaborating with influencers. This generates content around their offering, then delivered it through the influencer's networks.Influencers and corporations work together to create effective brand awareness campaigns. This new business model benefits both stakeholders. Influencers can monetize their influence by charging a premium. And then companies that can effectively market their brand.What’s the state of the creator economy?There is now a huge shift in the way material is consumed and created. Many internet businesses are building sustainable plans to monetize their platform. Thus the creator economy is growing in strength.YouTube, Instagram, and TikTok are deciding how content is made nowadays. They also decide how the content is delivered, consumed, and monetized.What are the creator economy business plans?How do users make money out of these apps? The creator economy has brought creative business models. These are transforming into long-term jobs by allowing them to focus on what they love most. Creating, interacting with followers, and monetizing their influence. Here are some examples of business models:Platform revenue sharing planAffiliate marketing planProduct placement planBrand sponsorship planSubscription-based planSelf-brandingDonationsPlatform revenue sharing planThis is the most common plan with the lowest barrier to entry. It's for creators that use platforms such as YouTube, Facebook, and others. Creators may monetize their work by receiving a part of the ad income. Ad income that is earned by their channel and posts.Affiliate marketing planAffiliate marketing is a commission-based strategy. Influencers are compensated for each consumer referred to a partner brand. Creators not only monetize their impact but also assist companies in creating leads. Through their content, they can position themselves as industry authorities.Product placement planProducers are compensated for using or featuring brands in their material. Advertisers or corporations pay influencers in exchange for product/service mentions.Brand sponsorship planA business or advertiser pays an influencer to promote their brand. They do this by promoting it in their content. This strategy requires artists to sign a contract. This states the exclusivity of specific products and services but it's more expensive.Subscription-based planVarious sites offer subscription-based content, such as OnlyFans, Instagram, Patreon, and Twitch. Here viewers may subscribe to a creator's channel for a charge of their choice. Fans may then view unique content. Live broadcasts, and videos that are not available anywhere else on these channels.Self-brandingSeveral creators even develop their products and services. It could be clothing lines, accessories, and so on. They make more cash and position themselves as a figure with authority in their field. This concept is better suited to artists who want to build a long-term business.DonationsDonations are another common type of monetization in the creative economy. This model has existed for more than a decade, yet, it is less common nowadays. You can't rely on contributions because people will either forget or won't be able to pay them. This is why most influencers choose subscriptions, brand sponsorship, and affiliate marketing.The common content creator economy types in mobile appsText This might contain everything from short articles to long-form content and newsletters. The simple premise of Substack, is to be "the home for exceptional writing". While most of its newsletters are free, Substack has over 500,000 paid members. According to The Guardian, “Substack takes 10% of subscription earnings, and payment company Stripe takes a further 3% with writers taking the rest. Writers charge around $5 a month (£3.66) or $50 a year for access to their newsletters, although the platform’s many free newsletters also have a big following.” Another fun fact is that the top ten Substack publishers make a combined $7 million each year.Video content Short-form videos appeal to smartphone users looking for casual entertainment. Following TikTok's breakthrough, other clones appeared in various countries. Many people find it simple to create videos thanks to Instagram Reels and YouTube Shorts. The main advantage of such apps is that they do need expensive shooting equipment. Only a competent smartphone, and an app.Audio content Podcasts had a large fan base even before the COVID-19 epidemic. The extended stay-at-home period increased the use of audio and video streaming content. Content providers had it well during that period. Not to mention Apple Podcasts, Spotify, and other regional platforms. Content makers could record and share their material across major platforms using tools. What tools you might ask? Anchor, Podbean, and others.Apps that help the creator content processCanva This is a free graphic design tool for those of you who are unfamiliar with design. Many creators need one, yet they are not always affordable. For example, Canva can help you create lots of graphics. Graphics for social media, blog posts, YouTube thumbnails, and much more.Even the free version of Canva provides plenty of tools. Including free pictures, and components to help you design your designs. As a result, this app might be a viable answer.Trello is a free project management application that lets you build many boards. here, you can keep track of everything you generate for your content. In a nutshell, it's a significant productivity increase.Trello is especially useful if you're not a big lover of excel sheets. Especially if you want to keep track of different materials or projects. For example, you might make one board for each channel you own. Such as an Instagram board, a YouTube board, a blogging board, and so on.Grammarly Bloggers and freelance writers will appreciate this tool! Grammarly is a free browser plugin that you may install. It will highlight any errors or misspellings in your content. It will identify problems in your blog posts, emails, or drafts once you download it.You may use it to verify if your blog entries are grammatically proper. So, before pressing "publish," always use the greatest wording you can think of.Pexels is a great resource for finding interesting royalty-free photos and videos. Artists and makers from all around the world may contribute their work.The nicest thing about Pexels is that you don't have to pay for a license to use the stock photographs. Nor do you need a subscription to access the website and download the images and videos.Hootsuite is a social media management and scheduling application. It allows you to connect many accounts, schedule and prepare posts in advance. You may book up to 30 posts in a single session, and you can arrange material for the following ten days. We feel that this is rather decent for a beginning.Tailwind: Planner & Schedule This is an excellent tool for all Pinterest designers. Tailwind is a Pinterest scheduling service. What does it do? It allows you to plan your pins to various groups, boards, and profiles in advance. This means you don't have to log into your Pinterest account every day to generate and submit new pins.It's a great solution for content creators that create a lot of material and want to manage it all in one spot.What other apps are popular nowadays? Probably the ones that Millenials love and are determined to not let go of just yet.Why is the creator economy a big deal?The creator economy exploded during the pandemic for obvious reasons. There are no signs of slowing down in the present either. This industry might reach $100 billion+ this year. And it makes sense. With more and more people engaging in online life, many of them create full-time jobs out of it. And of course, even more following the content.Marketing is being focused on social media platforms nowadays. So what will businesses do? It's only natural to seek out social media influencers to promote their brands.For example, when famous rapper Snoop Dogg paired with Corona in August of 2020, they played "go big or go home". So, Snoop Dogg did go big with this endorsement. He earned a neat $10 million for the deal. Not too shabby for one commercial. Snoop Dogg absolutely made even more of a name for both himself and Corona with this one.Do you need a content creator economy mobile app?As usual, if you have a strategy in mind or are seeking new ideas, it is worthwhile talking with our experts. Let's develop a solution that will provide your company with a competitive advantage. --- ### Why use Ruby on Rails as a backend technology for your mobile app? URL: https://appssemble.com/blog/why-use-ruby-on-rails-as-a-backend-technology-for-your-mobile-app You may be wondering why use Ruby on Rails. Truth be told, RoR is a better fit for many use cases than any other tool. Read why. Every year, we see publications announcing the death of this framework gem. And, despite being nearly 15 years old, Ruby on Rails (RoR) is far from extinct in the programming industry.You may be wondering why Ruby on Rails is used since RoR is a better fit for many use cases than any other tool.What is Ruby on Rails?Ruby on Rails (or "Rails") is a free and open-source development framework written in Ruby. Ruby is an object-oriented program (OOP). Modern online apps may be pretty complicated, with several levels. Rails simplify web development by providing a pre-built development structure. It also adds everything you need to create a web project.There is one big distinction between Ruby on Rails and other development frameworks. Its speed and simplicity. Changes to applications are being implemented immediately. So it avoids the time-consuming procedures of the mobile development cycle.Rails is being built up of various components, including:Active record, an object-relational mapping layerAction pack, a manager of controller and view functionsAction mailer, a handler of emailAction web servicesPrototype, an implementer of drag and drop and Ajax functionalityHere is a list of Ruby on Rails empowered websites that stands as an inspiration in many ways:GitHub – A platform that brings together the developers' community to discover, share and develop better softwareAirbnb - Online marketplace and accommodation sharing siteBasecamp – Company that hosts project management and team communication softwareCafePress – Online gift shop specialized in user-customized, on-demand productsCrunchbase – A leading destination for finding business details about public and private companies.What is Ruby on Rails used for?How to understand what Ruby may be used for? Keep in mind that it is a dynamic and general-purpose programming language. It is also adaptable and mature.The list of products you can develop with Ruby is rather long. All because of the vast (and still growing) number of gems and libraries. They serve as building blocks for various sorts of apps.The following are the most popular sorts of Ruby applications:MVPs Ruby is frequently selected for the low-cost and quick creation of MVPs. Before developing completely working apps, this language is used for prototyping. It also offers updates and testing for many versions of products.Apps for Social Networking Ruby's ability to sustain traffic-heavy apps makes it ideal for social networking sites. One example could be Twitter.Apps for Apartment Sharing and Booking It's also utilized for apartment sharing and booking apps like Airbnb and Couchsurfing. All because it can handle a large volume of daily transactions and property bookings.Platforms for e-commerce Ruby is a popular programming language for eCommerce platforms like Spree and Shopify. The speed of development, flexibility, and cost-effectiveness make it ideal for the job. That's because it allows the managing of many transactions at onceComplex database support platforms Two excellent examples of such systems are GitHub and Bloomberg. GitHub is the largest Git repository hosting platform for developers. While Bloomberg is a multi-platform financial news and analytics center. Because of its speed, efficiency, and flexibility, Ruby is also used for:automation, backupDevOps toolsAPI Clientsreport generatorsserversstatic website generatorscommand-line media players.The framework is still used by over a million developers worldwide. This includes many prominent companies like Dribbble and Hulu.Ruby on Rails’ recent updatesAlongside PHP and Python, Ruby makes the list of the 20 most used programming languages in 2022.There is considerable growth in the number of Ruby on Rails apps created in the "API only" manner. As a result, it is possible to create an API as an MVP, while still developing the application's frontend in any JS framework.Back to roots - Hotwire in 2022In 2022, we can also see Hotwire returning to its roots in the Ruby on Rails world. All these in a very short period, and with no development expertise. The strange thing is that we've used comparable tactics before. But never in such an orderly, unified manner.Strada is the finishing touch to this entire technical stack. Rails will go to the top as a Web application solution. And that's because of the capabilities for constructing mobile hybrid apps.Performance boost!Ruby on Rails has had performance concerns for years but with genuine progress. We see a major focus on addressing this issue and fixing the framework and language itself.Ruby 3.0 proved three times quicker than Ruby 2.0. Now, version 3.1 takes another step toward better performance. One of the phases was to construct the so-called "Fiber Scheduler". This enables asynchronous Ruby operations with no side effects or tiresome developer effort.Ruby examines well-known issues and alters the framework's behavior, pushing it toward asynchrony. As a matter of fact, a new version of the PG gem got published in early 2022. This allows asynchronous database requests and it demonstrates the Ruby community's development direction.Encrypt everything with RailsWe now see one fantastic feature in Rails 7 that has been long expected. By default, our databases were never encrypted. In general, this does not imply that it is compromised. But if we can, we should encrypt even simple data in the database.Parallel Execution in RubyNot all updates in Ruby on Rails are planned ahead of time. Some of them remind us of an experiment. An experiment that demonstrates RoR's willingness to explore new ideas. Ractor, a Ruby Actor Model is one of these features.It functions similarly to JavaScript service workers. It is allowing the establishment of correct threading between processes. It's also improving safety through fewer deadlocks and livelocks. Their communication is based on message passing, which differs significantly from conceptual threads.Why do people think Ruby on Rails is dead?The idea of RoR's collapse has almost become an urban legend by now. That is the result of many misconceptions formed around the framework. Now it's time to dissect them:1. Slow performanceRails has slower runtime times than Node.js or Golang. This becomes obvious for great products with high traffic. If this isn't a large project with a lot of users and requests, Rails is not to blame for the poor speeds. The server design or databases are at fault.Rails apps could be faster with a well-thought-out design and infrastructure. (a must in any large-scale projects, regardless of programming language). Basecamp, Airbnb, and GitHub are examples of large-scale RoR software. So where does all that lousy rep come from?Rails offer so much for the developer. Novice developers make foolish choices while writing code. Performance suffers significantly when faulty code is used. The underlying performance concerns of Ruby and RoR are being worked on. See examples:In 2018, Ruby 2.6.1 was released, which brought speed enhancements and new features. The creators of Ruby 3 wanted to speed up the language three times faster than Ruby 2.Rails 6.0, released in 2019, has solutions that make creating Web apps easier. Rails began demanding Ruby 2.5+ from then on, bringing the most up-to-date Ruby features aboard.Rails 7.0, which was published in 2021, contained jsbundling-rails integration. It also has asynchronous query encrypted attributes to Active Record and other features.2. Scalability issuesLet’s see why it's incorrect to blame the framework for difficulties and limitations. To serve requests rapidly, you need to take care of the following. Each component of the server system architecture must be set accurately and performant. When Twitter switched from Rails to Scala, Ruby was criticized for being unscalable. The change is most likely what ignited the debate over RoR's scalability difficulties.Available scaling options with Rails:code optimizationservice-oriented architecturehorizontal scalability3. It’s mature, hence boringWhenever a new framework arises, it quickly becomes popular. Especially the ones that ass something novel to the table. Hundreds of users and contributors appear all over the world. Then, after a few years, the buzz fades. What was once cutting-edge becomes far less thrilling, engaging, and demanding.It's growing, yet, maturity does not have to be dull. Maturity implies reliable, improved code. Following technological trends is not always a wise idea. Switching to something more popular might have the opposite effect and raise expenses. But, digital transformation is always a good idea.Why Ruby?Ruby is popular among developers because of its concise, clean syntax. It doesn't need a lot of unnecessary punctuation. It’s an object-oriented language. It's a clean language, flexible and predictable, that is simple to understand and write. It also uses less code to generate fundamental structures.Why Rails?Rails is popular because its conventions are both universal and intelligent. Rails is a repository of pre-written code. It implements the framework and many common tasks of a database-driven site. Thus avoiding wasteful labor in the early stages of the project.So, why should you choose Ruby on Rails as a backend technology for your mobile app development?Because it is a mature technology that has been around for a decade nowBecause it is all about writing less code that does moreBecause it allows easy modification of existing codeBecause it follows Agile development principlesBecause it has a super-active, collaborative & vibrant communityBecause it has plenty of free plugins called ‘gems’Because it’s free to useAnd last but not least because it allows you to build a prototype in a rather short timeBuilding apps in RoR is quick and straightforward. All thanks to coding by convention—an ideal solution if you're on a small budget and have a tight deadline.Finding competent RoR developers should not be difficult due to the large skill pool. Rails will never be a good solution for advanced and complicated projects. Especially in the hands of novice developers. It can cause future problems with maintenance, performance, security, and stability. All of them mean major expenditures that could be avoided.Ruby on Rails provides mobile solutions for Android and iOS a competitive advantage. Therefore, Rails is popular because its conventions are both universal and intelligent.Do you need a brilliant Ruby on Rails developer for your mobile app?If you need a great developer for your mobile app, let our talented team create something unique and limitless for you and your startup. Until the next one, stay awesome! --- ### A definite guide on Seed fundraising for startups URL: https://appssemble.com/blog/a-definite-guide-on-seed-fundraising-for-startups Unless you’re lucky and don’t need capital to grow, then you need to go through this article, learn what seed fundraising is and successfully get outside finance. The most difficult element in managing a business is creating something that people want, that’s why most businesses fail because they do not achieve this. However, the second most difficult aspect of launching a business is raising funds. This is a hard process.What is Seed Funding?Here's a quick explanation: Seed funding is a type of early-stage investment that startups get from investors in exchange for a stake in the firm. Following pre-seed financing, the first official funding round is seed funding. The fundamental objective and purpose of seed investment are to get the business up and going. It must encompass the early stages of product development, significant market research, and other early-stage operations.In other words, seed capital is a component of the first investment in new businesses. The monies are then utilized to fuel the company's expansion. There must be some form of return value to the investors as part of the seed funding for the startup process.What is Bootstrapping?Bootstrapping = a situation in which an entrepreneur starts a company with little capital, relying on money other than outside investments. An individual is said to be bootstrapping when they attempt to found and build a company from personal finances or the operating revenues of the new company.Bootstrapping seems fantastic in theory, but few firms make it out alive from this seemingly lush land. The fact that bootstrapped firms are well-known for this should raise red flags. It would be the norm if it worked so well.Bootstrapping may become easier if the cost of launching a business decreases. But I doubt we'll ever get to the stage where most businesses can survive without outside capital. Technology is becoming increasingly affordable, but living expenditures are not.Why raise funds?Startup businesses must buy equipment, rent offices, and hire employees. More significantly, they must develop. To execute these tasks, they will almost always need outside cash. Some would-be founders may be wondering why they should interact with investors at all. Why bother soliciting funds if it's so difficult?One simple reason is that you need money to survive. In theory, funding your firm with its earnings is a good concept, but you can't manufacture immediate consumers. To break even, you must sell a particular amount of your product. It will take time to increase your sales to that level, and it is difficult to anticipate how long it will take unless you attempt.The great majority of businesses will fail if they do not receive startup capital. The amount of money required to get a business to profitability is frequently well above the founders' and their friends and family's abilities to fund. A startup is a firm that is designed to expand quickly 12. To continue their expansion, high-growth enterprises nearly always need to burn cash before reaching profitability. A few startups successfully bootstrap (finance themselves), but they are the exception. Of course, many excellent businesses are not startups. Managing capital requirements for such businesses is not discussed in this document.A war chest not only helps companies to survive and develop, but it is nearly always a competitive edge in all areas that matter: employing key personnel, public relations, marketing, and sales. As a result, most businesses will almost likely wish to raise capital. The good news is that many investors are looking to invest in the right business. The bad news is that "fundraising is cruel." 1. The process of raising such money is frequently long, laborious, complex, and deflating to one's ego. Nonetheless, it is a route that practically all businesses and entrepreneurs must take, but when is the ideal moment to seek capital?When to raise funds?Investors send cheques when they are convinced that the concept is attractive, that the founders' team can accomplish their vision, and that the potential outlined is genuine and significant enough. When the founders are ready to tell their tale, they will be able to gather funds. And, in most cases, you should raise funds.For some entrepreneurs, having a narrative and a reputation is sufficient. However, for most, it will take a concept, a product, and some level of client acceptance, often known as traction. Fortunately, today's software development environment allows a complex online or mobile application to be produced and deployed in a surprisingly short amount of time and at a very cheap cost.However, investors must be persuaded as well. A product that people can see, use, or touch is usually insufficient. They will want to know if there is a product-market fit and that the product is growing.As a result, entrepreneurs should solicit funds only after they have determined the market opportunity and who the client is, and after they have developed a product that meets their demands and is being adopted at an unusually quick rate. How fast is it interesting? This varies, but a weekly rate of 10% for several weeks is outstanding. And to obtain funds, entrepreneurs must wow. Congratulations to founders who can persuade investors without these items. For everyone else, focus on your product and communicate with your customers.How much to raiseIdeally, you should raise as much money as is required to attain profitability, so that you never need to solicit funds again. If you succeed, you will not only find it simpler to raise funds in the future, but you will also be able to survive without fresh financing if the funding situation becomes tight. Their objective should be to generate enough money to reach their next "fundable" milestone, which is normally 12 to 18 months later.When deciding how much to raise, you must weigh numerous factors, including how much advancement that amount of money will buy, credibility with investors, and dilution. If you can give up as little as 10% of your firm in your seed round, that is fantastic; but, most rounds will need up to 20% dilution, and you should attempt to avoid more than 25%. In any case, the amount you are requesting must be linked to a credible strategy. That strategy will provide you with the credibility you need to persuade investors that their money will have a chance to grow.You need to bear in mind numerous factors, such as: How far can you take the business with the money raised?How much of your company are you willing to share at this stage (you should avoid giving up more than a quarter of your shares)?How keen investors are on your pitch?It is always a good idea to construct various plans based on different amounts raised and to thoroughly communicate your opinion that the firm will be successful whether you raise the whole amount or anything less. The difference is how quickly you can grow.Consider how many months of operation you intend to support when determining the appropriate amount to raise in your first round.Financing options1. Convertible DebtWhat is convertible debt? Convertible debt is also referred to as convertible loans or convertible notes. Convertible debt occurs when a corporation borrows money from an investor or group of investors to convert the debt to equity at a later point. Typically, the method for converting debt to equity is established at the time the loan is made. Sometimes compensation is provided in the form of a discount or a warrant. Sometimes there is, and sometimes there isn't. Sometimes the valuation at which the debt will convert is limited. Sometimes there is, and sometimes there isn't.There are several reasons why investors and/or the firm may want to issue debt rather than stock and convert the debt to equity later. The reasons are evident for the corporation. If the corporation feels its equity will be worth more in the future, it will dilute less by borrowing debt and eventually converting it. It is also true that the transaction expenses, mostly legal fees, are typically lower when issuing debt rather than stock.For investors, the choice between debt and equity is less straightforward. Sometimes investors are so anxious to participate in a firm that they will put their money into a convertible debt and allow the next round of investors to choose the price. Finally, debt is senior to equity in liquidation, so holding a debt position in a corporation rather than an equity position provides some additional security. However, this is not very useful for early-stage firms. When a startup fails, it frequently has little or no liquidation value.How does convertible debt work?Convertible debt is frequently used for friend and family rounds. It stands to reason that friends and relatives would prefer not to engage in a hardball bargain with a founder, preferring to wait until professional investors join the picture.Warrants or Discounts are common kinds of remuneration for making a convertible debt.The Warrant in a normal convertible note will be an option for whatever security is sold in the future round. The Warrant is commonly represented as a "warrant coverage percentage."A Discount is easier to understand but frequently more difficult to implement. A discount will be presented as a percentage as well. The most commonly used discounts are 20% and 25%. The discount is the amount of money that convertible loan holders will save if they convert in the following cycle.Why use a convertible debt?Typically, startups consider obtaining financing through convertible debt early in their life cycle. They want to move quickly, keep transaction costs low, and a convertible note makes it easier to close the investment. While these are all valid reasons to contemplate convertible debt, we are not fans of it at this stage in the life of a firm. I feel it is best practice to establish the equity value early on and begin the process of growing it round after round after round. On the other hand, convertible debt can make a lot of sense later in a company's existence.2. SAFEWhat is this?A simple agreement for future equity (SAFE) is a fundraising mechanism developed in 2013 by the well-known Silicon Valley startup accelerator, Y Combinator. Originally designed to assist entrepreneurs in raising seed finance, SAFEs have subsequently evolved into a common pre-seed and seed-stage alternative to the convertible note.How does a SAFE work?A SAFE, unlike a convertible note, is not a debt instrument. A SAFE is a convertible equity instrument that gives investors the ability to acquire stock at a later period and under certain conditions. They are often substantially shorter in length than convertible notes.Why use a SAFE?SAFEs have several important benefits over debt-based alternatives. Because it is not a loan, the startup does not incur debt as a result of the investment. This feature assists in preventing a startup from going bankrupt if it is unable to develop momentum, shift to a different business plan, or accrue interest over time.Another significant advantage of SAFEs is their simplicity. SAFEs were intended to be basic so that entrepreneurs could save legal expenses and reuse them. Only the value capital will need to be discussed for a conventional SAFE (if at all). Because the agreement is not a debt, there is no need for startups and investors to negotiate maturity dates, extensions, or interest rates. They also do not have to haggle with other investors.However, the concept of SAFEs is not universally welcomed. One particular source of concern is that a business may fail before investors can execute their stock options. In that circumstance, the investors have few options because the firm owes them nothing.3. EquityWhat is this?Setting a valuation for your company (generally, the cap on the safes or notes is considered as a company's notional valuation, though notes and safes can also be uncapped) and thus a per-share price, followed by issuing and selling new shares of the company to investors, is what an equity round entails. This is usually more difficult, costly, and time-consuming than a safe or convertible debt, which explains their appeal inHow does equity work?When your firm conducts a pricing round, you must be aware of numerous critical components of an equity round, such as equity incentive schemes (option pools), liquidation advantages, anti-dilution rights, protective covenants, and more. These elements are all negotiable, but if you have agreed on a valuation with your investors, then you are typically not too far off, and there is a deal to be done. I won't go into detail on equity rounds because they are so infrequent for seed rounds.Friendly advice1. Have low expectationsRaising capital damages the morale of many businesses not because it is difficult, but because it is far more difficult than they anticipated. Disappointment is what kills you. And the smaller your expectations are, the more difficult it is to be let down.2. Keep working on your startupIt may appear clear that you should continue to work on your company while soliciting funds. This is a difficult task, and most startups fail to do so. Raising funds has an uncanny ability to absorb all of your focus, even if you just have one meeting with investors each day, that one meeting will consume your whole day.3. Be conservativeAs the situation worsens, the best strategy becomes more conservative. When things are going well, you can take risks; when things are going poorly, you want to play it safe. I recommend treating fundraising as though everything was always going wrong. What we advise most to the firms, is that if a trustworthy source gives you financing on acceptable terms, you should take it.4. Be flexibleYou should avoid answering the following two questions: "Who else are you talking to?" and "How much money are you attempting to raise?" While they don't anticipate you answering the first question, and ask it just in case, they appear to be expecting an answer to the second one. We advise entrepreneurs to inform investors that based on the amount raised, they have many options. A year's worth of food and housing for the founders might be paid for with as little as $50,000.5. Be independentA startup can have expenditures so low that they might be profitable on as little as $2000 per month. When you just make enough to cover your living bills, everything changes. You may still require investment to make it large, but not this month. Investors like it when you are self-sufficient. It demonstrates that you've considered producing money rather than merely working on technical challenges; it demonstrates that you have the discipline to keep your costs minimal and most importantly, it demonstrates that you don't need them.6. Don’t take rejection personallyWhen you are rejected by investors, you may begin to doubt yourself. They are after all more experienced than you. Aren't they probably correct if they believe your startup is lame? Perhaps, perhaps not. If the design is the problem, here’s the solution. Precision is required when dealing with rejection. You should not just disregard rejection. It might imply something. But you should also avoid being demoralized.7. Being able to downshift into consultingConsulting is a risky approach to funding a firm. Not the best long-term answer, but it can rescue you from an urgent hazard. Some startups benefit more from this than others. As long as you don't get drawn into consulting full-time, this may even be beneficial. If you are using the program for them, you would have a good understanding of their needs.8. Avoid inexperienced investorsThough beginner investors appear unthreatening, they might be the most hazardous type because of their nervousness, especially in relation to the amount invested. Their attorneys are also unskilled. Of course, someone needs to make money from new investors; otherwise, there would be no experienced ones. However, if you do, either lead the process yourself, including providing the paperwork or utilize them just to supplement a larger round conducted by someone else.9. Know where you standThe most harmful aspect of investors is their indecision. The lengthy no or the rejection that arrives after months of meetings are the worst-case scenarios. Investor rejections are similar to design flaws: they are unavoidable, but considerably less costly if discovered early.So, while you speak with investors, keep an eye out for clues as to where you stand. How probable is it that they will offer you a term sheet? What do they need to be persuaded of first? Collect information about them, but be disciplined, otherwise, their desire to lead you on will mix with your want to be led on, resulting in utterly false perceptions. Here is some extra advice for mobile startup founders.Even in a conservative business like venture capital, opportunities like this don’t sit around for long. As a result, either existing investors will start making decisions faster, or new investors will arise who do.In the meantime, creators must view fundraising as a risky endeavor. The greatest risk is being caught off guard. It's that startups will underestimate the difficulties of getting money, that they'll breeze through all of the first processes, but when it comes to raising money, they'll find it extremely tough, demoralize themselves, and quit. So we warn you ahead of time: obtaining funds is difficult.Before meeting with any investor, make sure you know what drives them. Every investor is unique, and as we've seen, angel investors are motivated differently than VCs and corporate seed funders. Do your research.Your personality is equally as crucial as your stats. Investors will want to know that you are capable of succeeding and making them money. They are not just investing in your goods, but also in you as a person. Keep it in mind, and simply be yourself.appssemble helps companies implement digital transformations through knowledge and experienceAs usual, if you have a strategy in mind or are seeking new ideas, it is worthwhile talking with our experts and developing a solution that will provide your company with a competitive advantage. Until the next one, do your research, be confident, consistent, and don’t give up after one rejection. --- ### How to design your startup (mobile applications) URL: https://appssemble.com/blog/how-to-design-your-startup-mobile-applications Learn more about product design and how to make this an advantage as you’re building something people want in your startup. Designing may be extremely intricate and time-consuming. Still, we hope that we will be able to put everything that we thought founders would get wrong or run into issues within this post. These are general and essential principles that you should be aware of.Why are you starting a startup?Since everything around you that you currently experience was made up by people no smarter than you, and you have the power to alter it, you can have an impact on it as well, and you can create something that others can use. So, once you discover it, you will never be the same.What about design?Design is about developing and building things that other people can utilize, and removing one word from that phrase, causes it to fail. So, in this article, we're going to look at what design is. What difference does it make? We will go deeply into the ideas of product design, interface design, and visual design. We'll also look at how to do it strategically, even if you have no design expertise and don’t know the design trends, it only takes to be a human being, smart, and put yourself in the shoes of others, in fact, as founder, you definitely need to.What goes into a great product?Great product managementGreat designGreat engineeringGreat customer supportWhat is design and why does it matter?In a nutshell, it is just these two very simple things, creating things for users that work well and delight them. Those are two, sometimes disparate things as we'll see. There will be times in your startup like perhaps now, perhaps tomorrow that you'll want to start applying these things, well Google's, your friend. Everything in the world that you need to know, it's out there and so the computer is truly just a bicycle for the mind to train and learn.The other thing that I want to underscore is that we talk about design as the singular thing on its own, but it truly is deeply integrated with this broader picture of how to create great products. It's not just designed on its own, it's how the design interfaces with all the other pieces of the pie. So it takes great product management, in addition to that great design, then engineering, and customer support.It's all of these things and especially at your stage, don't box yourself in. You have to know that you are the shepherd of your product, and you're going to have to do every single one of these things. The first common misconception is that design is how it looks. It truly is not only about how it looks, but also how it works.The key thing here is how to create things that are not burdened with non-essentials. It really is about purity, about simplicity, this is a guiding force and everything that we see in the marketplace today. History doesn't repeat, it rhymes, and there's very little ‘totally new’ under the sun. In fact, as designers, you probably shouldn't be spending too much time trying to be extremely novel, because novelty is the opposite of functionality.So what do I mean by that? Earlier, we talked about form versus function. These were the two Yin and Yang, the opposing forces when you're trying to put together a design. We always want something to be beautiful, to make you feel good, and make the user feel good too, but at the same time, delight is also a part of the novelty. It's that "Hey this is new. I've never seen this before, this is interesting. I want to see more of this. Let me turn the page, let me click next."At the same time, the function is the thing that’s the stake. If delight is the sizzle and works well as a steak, that's why we're here. We're trying to get something done. Let’s call out Apple for its iPhone notch, that is the definition of form over function, and certainly, it's incredibly novel.Certainly, it serves the purpose of a marketer to be able to have this very novel, unalike thing and differentiate it from all of these other smartphones out there. In terms of function when I'm watching a video, this is categorically worse.So if you take a moment and try to think through, why is it that we see form over function so much in the things we use, the products we use around in our daily lives. Why does this happen? Clearly, this should not happen and so that form should follow function. Then you should emphasize the sympathy directed to your users. Ask yourself, what are your users thinking? What are they feeling? Why are they here? How do they perceive this UI for the first time? You must become genuinely interested in other people, you have to see their point of view. You want to be able to be sympathetic, and understand what their ideas are, what they understand, and what they want.One of the things that are interesting about building highly technological products is that we often think about them as incredibly complicated machinery. The most useful mental model for us is actually to not think of it as building a car, or even building a website, or writing software, or anything like that. It's somehow like throwing the best possible party you can. That politeness, that inviting welcome nature, that thoughtfulness, that's something that you have to keep in mind as you do your work as not just a designer, but as a founder. The key piece here is knowing what problem you're solving. Here is some extra advice for mobile app startup founders.This is the main belief of design thinking as well. So apart from not knowing your problem, is also the lack of empathy, and going back to form over function is that, if you don't know who the users are, what their problems are, then you are in danger of creating something faulty.Product designI know this isn't formally a part of the design, I just don't know how you could do design without doing this part too. Every single one of these things has fairly specific deliverables. One is a product requirement document (PRD) where you start with a problem statement, and once you have it then you can think about who are these very specific people that have this problem.Let’s walk through user personas. So personas are just a tool for designers to figure out who are these very specific people. You name these personas and think of them as specific human beings with, sometimes, a backstory. So that will help you a lot when you're making decisions about, well what are you trying to do, and about the features that matter.Being able to write down specific personas, means figuring out the type of users we want to deliver our product to and being as crisp as possible around what their needs are. We call that user research and it happens before you even start thinking about what problems to solve at some level. So when you see that term out there, if you end up trying to hire people for that role, this is where it fits. Once you know what these requirements are, the next step is prioritization.So prioritizing and being able to be very firm about these requirements are two of the most fundamental ways that you can make sure you release a product successfully, and you know that the product's going in the right direction. That's product management 101 but if you do this, you will be far ahead of your peers. A lot of people don't even do this very basic step of writing down what these features are, who they are for, what are the problems they're trying to solve, and then what are their respective priorities.Next are scope, quality, and time. So how much you do, that's part of the prioritization. Quality, its reality is not encompassed by your PRD, it's just purely in how people use your products, in how many bugs there are, in the things that don't work, and these are always an issue. Finally, time. You can always do all the features you want with the highest possible quality, but you might have to slip your date by two or three weeks if not longer. If you don't cut scope likewise, well you might be able to hit your time but users are going to run into 1,000 bugs and you're not going to like that. So if we work backward from that, then this is precisely the process you use to fight that.Interaction designAll of these things are incredibly important for this very first part, which is just pure product design. Interaction design is here so you know who the user is, what the problem is, and how to translate that into something that you can start working on. The questions you ask are, how will they do it, what are their goals, and how do they achieve them? At the end of the day, what you're trying to get is either a prototype or a wireframe.There are quite a few prototyping wireframing tools that are out there, and what you want to do is figure out the text, the call to action, and the screen-to-screen flow. You don't want to care about color, how it looks or what font you use. You don't even really have to worry about layout too much either, you should rather start thinking about the layout as a part of this process.Interaction design is about commands and about telling people what to do because people are incredibly suggestible. An interaction designer is not only the person who figures out where the buttons go, what the layout might be, or what the flow is. They're also the writers, they are trying to influence people directly by using direct command language. Don’t use passive voice, you're not showing, you're telling, you're just describing something about what you're doing in this third-party disembodied voice.A big company might get away with it because of its immense salesforce, but you as a startup cannot afford that. So everything that you write needs to be direct, and also a direct personal voice. You need the ‘call to action’ to be incredibly obvious, use command language. When they go to that mobile app they should know what they need to do.The other important part of interaction design is trying to figure out how to get people to do things. We generally think about this in two ways. One is how do you implement actions, for example, you shouldn’t optimize the product for a strange case that doesn’t often happen, like asking users to confirm their password by inserting it twice. The login should be done easily by email and if they forget it, allow them to use “forgot password” instead of typing the password twice.These are a couple of patterns that you can use. Another big misconception that beginning designers run into all the time is that they're always trying to do something incredibly novel at the interaction design stage. We recommend that you just steal what works, and so don't try to reinvent the wheel. For instance, the motion of ‘pull to refresh’ is something that works incredibly well, also the ‘swiping from left to right’, so try to work with these instead of searching for new ones. A lot of apps do it, but it's become a convention these days because they are easy and natural to use.That's actually what is desirable for most of your designs. You don't want to be novel, you want to be something that gets people to the right place as quickly as possible.One other interesting thing I want to call out and it's the danger zone of using design patterns. Some of the most common ones we’ve seen are using the wrong kind of pagination. We’ve seen people design for the web and they use these little dots to represent where you are and also the swiping navigation but sometimes that makes no sense at all. So you have to be incredibly careful with mixing modalities, and even with these design patterns, as you implement them you should think like the user, why am I here? What is the user trying to do? Does this make sense for my modality?Visual designVisual design is about blending these things. It's the interaction design and visual design super linked. It is how you tell the user what is important at the visual level. What emotions do you want to evoke, and how do you want them to feel?Another major misconception that people start to have around visual design is about not expressing themselves. The secret thing is to express what you are trying to and what information you are trying to get across. One of the principles you can apply is to look at any design that you're doing, and just try to figure out if it can be removed without taking away any meaning. That includes texts, lines, borders, and anything else.We found three very simple principles that you can use in visual design. The first and most important is contrast, for example, the most basic type of contrast that you can give is bold versus not bold, more important, less important, or incredibly simple. Bold is not the only way you can denote what is important versus not. You can use color, and that's an incredibly valuable tool. You can also use size where you can immediately see as a visual designer, just pay attention to when, what is more, and less important.When users come to your app/site, they try to figure out why they are there, what they are trying to do, and if your app experience is what they want. They will immediately be drawn to the highest contrast things. Then if they care about any of the page’s or app’s parts, they will immediately dive deeper into exactly that part that they enjoy.So visual hierarchy is your best tool for giving your users the guideposts, this is the way to go. After you’re done with the visual hierarchy, you start learning how to use colors and do your layout. Figure out what you need to put on the page, and then first try to use padding and margin to the extent that you can use a grid, you can put related things close to each other.So 90% of the time you can probably get away with just using a proper grid with enough spacing, putting related things together with good headings, and using the contrast. Then, using a box is a very important thing. It draws a lot of attention, so that's why you'll see it so commonly on websites around a ‘call to action’ button.It really is a high contrast thing, but be very careful when you use it so you avoid ending up with this blend of boxes where the user has no idea what's important and what they should be doing. Whereas if you use the grid and that visual hierarchy, it is very straightforward.Another aspect that's rather important is you don't have to fill every single design, margin to margin. A white space can be incredibly useful, sometimes even helping direct the end-user, helping them understand what's going on. Having a space on the side just gives you a place to put relevant things or to just allow users to be more focused.All of these bits of advice are incredibly simple things, the use of contrast, a grid, lines, boxes, and the use of color can do a lot for your page or app. In the end, it’s not that complicated, just remember to have empathy, think like a user, what do they look for in your page, and how do your layout, motions, and the rest of the design, impact their experience to make the dive more into that specific thing they’re looking for in your app or site. So there you have it, the most important tips and tricks on how to design the right way your startup, now you don’t have a reason to make the same mistakes.We understand what a challenge it is to be a first-time tech founder. It’s pretty difficult to pitch, design, develop and market your idea. Not to mention how hard it is to prove you’ll succeed in a very competitive industry.appssemble is here to be your bold digital product development partner! This service is the cheapest way to start your startup. What will we do? We'll help you define your product, understand its technical feasibility and costs, then validate it. You’ll receive all the tools and information you need to pitch to investors or develop your next products. Come up with the idea and we’ll help you with the rest! --- ### The future of non-fungible tokens (NFTs) and mobile apps URL: https://appssemble.com/blog/the-future-of-non-fungible-tokens-nfts-and-mobile-apps A quick catch up into what NFTs are, what’s the difference between them and cryptocurrencies, how to create, buy & sell them, and whether or not you should invest in them through the following apps. Non-fungible tokens (NFTs) appear to be all the latest craze. From art and music to tacos and toilet paper, digital assets are selling like 17th-century exotic Dutch tulips, fetching millions of dollars in certain cases.However, are NFTs worth the money—or the hype? Some analysts believe they are a bubble that will burst. Others feel that NFTs are here to stay and will permanently revolutionize investment.What exactly is an NFT?According to Forbes advisor, an NFT is a digital asset that symbolizes physical objects such as art, music, in-game goods, and films. They are purchased and traded online, usually using cryptocurrency, and are typically encoded with the same underlying software as many cryptos.Even though they have been present since 2014, NFTs are gaining popularity as a popular means to buy and sell digital artwork, and maybe they’ll become the new app on the block that millennials love. The market for NFTs alone was approximately $41 billion in 2021, which is approaching the whole value of the worldwide fine art industry.Individual images—or perhaps the full collage of images—can be seen online for free by anybody. So why are individuals prepared to pay millions of dollars on something that they can easily capture or download?Because an NFT permits the buyer to retain ownership of the original item. Furthermore, it includes built-in authentication, which acts as evidence of ownership. Collectors appreciate "digital bragging rights" nearly as much as the thing itself.What is the difference between an NFT and Cryptocurrency?NFTs reside on a blockchain, which is a distributed public ledger that keeps track of transactions. You've definitely heard of blockchain as the fundamental technology that allows cryptocurrencies to exist.NFTs are commonly kept on the Ethereum blockchain however they can also be held on other blockchains.An NFT is formed, or "minted," using digital objects representing both tangible and intangible elements, such as:Graphic artGIFsVideos and sports highlightsCollectiblesVirtual avatars and video game skinsDesigner sneakersMusicNFTs are essentially digital collector's items, similar to actual collector's items. Instead of receiving a physical oil painting to put on the wall, the customer receives a digital file.What is the purpose of NFTs?Blockchain technology and NFTs provide artists and content providers with a one-of-a-kind possibility to monetize their work. Artists, for example, no longer have to rely on galleries or auction houses to sell their work. Instead, the artist may sell it straight to the buyer as an NFT, allowing them to keep a larger portion of the revenues.Furthermore, artists may automate royalties so that they get a percentage of revenues anytime their artwork is sold to a new owner. This is an appealing feature because most artists do not earn future revenue after their work is sold.How to buy NFTs?If you want to build your NFT collection, you'll need the following items:To begin, you must obtain a digital wallet that allows you to store NFTs and cryptocurrencies. Depending on the currencies accepted by your NFT provider, you may need to acquire some cryptocurrency, such as Ether.You may now buy cryptocurrency with a credit card on platforms such as Coinbase, Kraken, eToro, and even PayPal and Robinhood. You'll then be able to transfer it from the exchange to your preferred wallet.As you study your alternatives, keep costs in mind. When you acquire cryptocurrency, most exchanges charge at least a portion of your transaction.Should you buy NFTs?Does the fact that you may purchase NFTs imply that you should? Investing in NFTs is mostly a personal choice. If you have some extra cash, it's worth thinking about, especially if the artwork has sentimental value to you.However, keep in mind that the value of an NFT is entirely determined by what someone else is prepared to pay for it. As a result, demand will drive the price rather than fundamental, technical, or economic factors, which often impact stock prices and, at the very least, serve as the basis for investor demand.All of this means that an NFT may be resold for less than what you paid for it. If no one wants it, you might not be able to resell it at all. It’s risky because the future is uncertain and there isn’t a lot of their performance so you can never be too sure.The use cases of NFTs1. NFT gaming will add valueLet's start with the most important. In gaming, NFTs may unlock and add value to previously experienced gameplay. As Chris Clarke of KokoSwap explains: “In the gaming industry, it's something where if the gamer is putting their value into the game, it just makes complete sense they can take this value out of the game.”This is Ubisoft's point of view, as evidenced by the deployment of its platform, Quartz, and its in-game NFT, Digits. Quartz was launched by the publisher at the end of 2021, and it has remained on course. This is critical because NFTs can effectively establish a second-hand market for digital games and things.2. Play-to-earn games will be hugeA healthy internal market and economy might be beneficial. The emergence of Play-to-Earn games like Axie Infinity is signaling the way forward. Some gamers may even make a living off of these games. Play-to-Earn games like Axie Infinity, which have 3 million daily active users, aren't going away.While many Play-to-Earn games resemble non-NFT titles such as Pokémon and Stardew Valley, there are claims that some are simply backdoor blockchains, with the gameplay coming second to buying and trading cryptocurrency disguised as collectible items. Aleksander Leonard Larsen, the co-founder of Axie Infinity, stated that 50% of its users had never utilized bitcoin before playing the game during a panel discussion on the metaverse at Token2049. This demonstrates how NFT games may aid in the development of UX design and the accessibility of blockchains.Even successful Play-to-Earn games, such as Axie Infinity, maybe a challenge to negotiate crypto wallets, buy-in fees, hidden expenses, and more before you can begin earning a prized Axie. There is an opportunity for improvement, maybe by combining the greatest concepts and UX designs from Play-to-Earn and Free-to-Play.However, the concept of Play-to-Earn games is comparable to Free-to-Play games, so the roots are still there for gamers to connect with, as long as 'Play' is always prioritized above 'Earn' and they aren't money-grab trade applications disguised as cuddly animals.3. One-of-a-kind in-game inventory itemsThough many mainstream games create one-of-a-kind items with various rolls, one-of-a-kind items for usage within a gaming world have not been viable since skilled players can nearly always exploit a local or even server-based database to either edit, duplicate, or remove these items.A blockchain-based inventory system might keep track of each instance of a certain item, ensuring that there is only a limited amount in circulation throughout a game's ecosystem.As seen above, NFTs are employed by the game Gods Unchained, which was created by a former director of Magic: The Gathering. True scarcity generates value in the real world based on elements such as the item's in-game utility and, of course, the popularity of the game.It's similar to collecting rare, tangible Magic: The Gathering cards, or any collector's item. This implies that NFTs will bring a whole new level of realism to trade when rare items are unique and limited throughout the whole gaming ecosystem.Mobile apps to create, buy & sell NFTsSome of the greatest NFT applications for iPhone allow you to create, mint, and trade artwork. The process of minting — registering an NFT on a blockchain – is becoming more straightforward. More applications and platforms are now providing user-friendly UX design for those new to the world of cryptocurrency. Other applications just allow you to search for and collect your favorite NFTs.1. SketcharSketchar is an NFT app for those who believe NFT art to be overly simplistic. It will teach you how to draw and will allow you to create your own art, mint it as an NFT, and then sell it on the app’s marketplace. AR training is used in the app, you just need to hold your phone over a piece of paper and look at the screen to see the line art that needs to be followed.Platforms: iOS, Android Reasons to buy:Learn to draw using ARCreate NFT art in-appHas its own NFT marketplaceReasons to avoid:Doesn’t link to other marketplaces2. PixlPixl’s concept is that you can mint NFTs inside the app by using photographs from your own photo album or images from Instagram, this also being the reason why this app stands out. Pixl has features for creating a profile and joining the NFT communities, which, along with the Instagram connectivity, makes the app a social NFT app worth trying out. If you want to learn more about NFTs but despise the language, this is the app for you.Platforms: iOS Reasons to buy:Create NFTs in-appSell NFTs on multiple marketplaces, including OpenSeaIntegrated with InstagramReasons to avoid:Has limited NFT creation uses3. NFT GoWhile some of the applications on this list allow you to produce art, mint NFTs, and access markets, NFT Go only allows you to perform two of the three. This program allows you to mint pre-made art as NFTs and then publish it to different NFT markets, as well as explore marketplaces and make, buy, and sell NFTs all within the app. However, while the UI is sleek and straightforward, making things appear simple, the program might be sluggish and have hidden fees.Platforms: iOS Reasons to buy:Share NFTs to multiple marketplacesCan be expensive to useReasons to avoid:Can be confusingHidden costs4. OpenSea: NFT MarketplaceAs the largest and oldest NFT marketplace, OpenSea provides every type of art and NFT you could want — art, games, music, and more. The software serves as a portal to OpenSea's market, allowing you to explore and tag art to purchase later from your PC. It's a convenient method to keep track of NFT dips and pricing while you're out and about. Aside from the lack of a wallet connection, the OpenSea app includes a variety of functions to get you started with NFTs. You may search by collections, save things for later, link to blog articles, and connect your OpenSea profile to the app to see whether someone has bid on your collection while you're on the road.Platforms: iOS, Android Reasons to buy:Browse the world's largest NFT marketplace on your iPhoneReasons to avoid:You can't send NFTs to OpenSeaAlthough mobile applications aren't the most popular means at the moment to purchase and sell digital assets, NFT trading apps are expected to enter the app ecosystem in the same manner that cryptocurrencies did.In the end, treat NFTs in the same way you would any other investment: complete your research, recognize the dangers, including the possibility of losing all of your investment money, and continue with care if you decide to take the leap.If you’re looking for more information and directions for your NFT mobile app idea or looking to hire the best iOS or Android app development team, then you should meet our professionals and give them an insight into your project’s idea. Appssemble always keeps up with clients’ requirements and builds something professionally unique by understanding the culture of their business. Until the next article, do your research before investing, and after that, do it with faith and reliability. --- ### Mobile infotainment applications for smart cars URL: https://appssemble.com/blog/mobile-infotainment-applications-for-smart-cars The days of collecting maps, memory sticks, and music gadgets are gone. As long as you have a rather new car with a dashboard capable of connecting to an Android or iOS smartphone, apps come to save the day. How many cars are there in the world?Short answer? Many. Way too many.There are so many that if they were all parked nose-to-tail, the line would extend from Sydney to London, back to Sydney, back to London, and back to Sydney. At least, that's what our basic calculations tell us.So, yeah, there are plenty. You were hoping for a bit more information, weren't you? So, continue reading.So how many are there really?The particular figures are a bit difficult to find, but Hedges Company says “There are 1.446 billion cars in the world in 2022. Most are in Asia, followed by Europe and North America. 19% of all vehicles are in the United States”, so we have to believe them.Do people use mobile apps on cars’ dashboards?When it comes to automobiles, phone applications appear to be a point of conflict for nearly everyone. According to a J.D.Power survey, drivers are still dissatisfied with the performance of their smartphone apps.The annoyance with phone apps comes from the fact that software has become an essential aspect of the new automobile experience. In 2020, 45% of consumers did not utilize the app that came with their automobile. By 2021, that proportion would have decreased to only 25%. People prefer a mobile app connected to a car rather than an already installed one because they lack the functionality owners want.What are apps for cars?Cars are becoming more intelligent and businesses have a strong need for mobile apps. The classic radio in most automobiles has evolved into an interactive dashboard, and data in your vehicle is now more accessible than it has ever been. But the use of mobile apps is winning grounds in cars’ dashboards. If you thought creating mobile applications for Android, iOS, and others was difficult, prepare for the next major platform: developing apps for use in automobiles. Four businesses are driving the effort to create a smart car using their OS:GoogleAppleBlackBerryFordGoogle created the Android Auto auto operating system, whereas Apple has CarPlay. They'll function similarly, you connect your Android or iOS device to your car's USB port, and the device will power the screen.Car operating systems are not perfect clones of iOS and Android since they must account for the particular environment and hardware of an automobile, including keeping distractions to a minimum, but it’s a perfect niche to invest in the future years because the market is growing and the demand for car interfaced apps are increasing too.One day in the coming future, all mobile developers will be required to design or alter their apps for automobiles. However, developing a mobile app for automobiles entails much more than simply coding it for the operating system used by the vehicle. Apps for automobiles have certain restrictions, notably in terms of safety and distraction, and you can check the guidelines for iOS hereand for Android here.However, here are 6 general guidelines of the department regarding distractions:Reduce the device's complexity and task length;Limit gadget usage to one hand (the other hand should stay on the steering wheel (to operate the car);Individual off-road glances necessary for device functioning should not last longer than two seconds.Limit the duration of each off-road look necessary for gadget functioning to no more than two seconds.Reduce the amount of visual information in the driver's field of vision that is unneeded.Reduce the number of manual inputs needed for gadget functioning.What do they do?Smartphones aren't the only devices on which apps will reign supreme. Apps will certainly become a larger part of our driving experience as our cars get smarter. We will be able to track charge levels and operate various car features using smartphone apps connected to automobiles.In terms of the in-car experience, thanks to built-in software and applications, our vehicles will be able to successfully interface with our mobile devices.What most people don't realize is that many developers working in a mobile app development firm have also built mobile applications that improve the driving experience, giving your smartphone strength, and turning it into a tool that fights distracted driving rather than causes it. Distracted driving apps encourage safe driving or even prohibit you from using your phone while driving to keep your focus off your phone and on the road.Even while distracted driving is not a new problem, it is real and growing by the day. People are injured, and some are killed, as a result of traffic accidents caused by distracted driving. It is no secret that our cell phones contribute significantly to the rise in distracted driving accidents. So, follow the guidelines and create the best app to support the driver's experience.There’s an app for every driving experienceCar apps were made to ease people’s lives, I’m sure of it. We went crazy with creating mobile apps for our mobile devices like food delivery apps , social networking apps, or even car selling apps, and now it’s time to let the car app grow and shine. As we’ve said before, a car is no longer a privilege, but an important part of our lives and comfort. The world moves at a quicker pace, the destinations are moving further and further away, so we do need a vehicle to move around these days.Once you own a car, you check that box and start having other needs from it, needs that are usually satisfied by consulting an app. Now let’s take the next step and upgrade to the next logical thing, and start using the apps on the car’s dashboard, it’s easier, more convenient, and gets the job done just as well.With that in mind, we’ve pulled 20+ app categories, covering a wide category that any mobile app startup can embrace in their business, to suit the user’s needs. Here they are:1. GPS appsToday's market is seeing an increase in the number of location-based apps that make users' daily life more pleasurable and easy. Because of their particular usage, such mobile apps have a prominent role in the mobile app business. Position monitoring, GPS data, and map integration are important elements of such an app.2. Gas & fuel appsGas & fuel apps are relying on crowdsourced data and they are designed to help the user find the gas stations and the places with the cheapest gas near them. Users can participate in reporting the price and easily access the data when they’re on the road. That sounds like a good app idea for a car app, right?3. Parking appsIt is a unique mobile app idea for startups as the number of vehicle owners increases day by day and finding a parking place for your vehicle becomes difficult whether you reside in a large location or visit large cities, malls, shopping centers, theme parks, or other regions. Parking place finder apps are nowhere to assist you in finding a free parking space. They employ cameras, GPS, parking information, and real-time location to provide the customer with open space whenever he needs it.4. Music streaming appsToday, there are several Online Music Streaming Apps on the market that have received a large number of downloads. Users may now listen to any song online without having to download it using such apps. Furthermore, the user may construct playlists of his favorite music based on his mood. It is the ideal app concept for attracting music fans.5. Video streaming appsUsers of video streaming applications may download any video material while watching it. It saves time on buffering and allows users to watch information online rapidly without storing it on another device. Some apps also allow users to watch videos while they are not connected to the internet.6. Bus booking appsWhat if you’ll need to travel by bus once or twice, or the path to work or school requires a bus driver? Well, there are options of bus booking apps ideas to solve quickly in the car before departing. A bus booking app, which is an online bus ticketing platform, provides its customers with a ticket booking service. Gone are the days when we used to book tickets from the ticket window. A bus booking mobile app is automated and controls the conventional database, bus ticket booking, and bus tracking.7. Car maintenance & service appsCar servicing applications are now in great demand in the industry. We generally utilize offline vehicle services, which are extremely inconvenient for us because we have to pick up and drop off our car at the service facility. This procedure takes a long time. However, with a car service app, we no longer need to worry since the car service companies listed on the car service mobile app will even pick up your vehicle.8. Dashboard cam appsYou may never need a dashcam. You'll be glad you spent the money if the scenario arises. Believe it or not, dash cameras are more helpful than you think! While the initial cost may appear to be high, dash cameras have been shown to assist drivers to save money in the long term by keeping them out of hit-and-runs, car accidents, and other mishaps. The peace of mind that comes from knowing your car is being secured by your silent witness is priceless.9. Hotel & restaurant booking appsWe don't enjoy having to wait for a long period in a restaurant or hotel these days. We just want rapid hotel and table reservations with excellent service. As a result, a Hotel & Restaurant booking app might be a practical solution for providing such a service. This type of app benefits both hotel and restaurant owners and customers. It allows customers to choose their favorite hotel and restaurant using AI and then provides them a wonderful online discount in exchange for their trust and loyalty.10. Rental & booking appsPeople nowadays go on lengthy vacations when they need to find a place to stay. As a result, the rental booking software makes it easier for them to discover a rental house. The app contains a list of all available properties, whether they are for rent or sale. The user may choose any home based on their geographical preferences and budget.11. Price comparison appsWe tend to compare the pricing of the same thing everywhere we can, whether we are shopping online or in person. This practice allows you to save a lot of money. So, why select a time-consuming method when you may compare rates most simply and conveniently? It may be a stressful chore at times. As a result of technological improvement, several Price Comparison Apps on the market will provide you with the same service.12. Packers & Movers appsPackers & Movers App is a user-friendly platform that allows users to book any packing and moving firm featured on the app based on their location and price choices. In addition, the chosen organization is responsible for the following tasks. As a result, the on-demand packers and movers app provides a simple and hassle-free service.13. Taxi booking appsYou may quickly order a cab using your cell phone from anywhere at any time, why not be able to do it from your car’s dashboard? A cab booking smartphone app has different features that allow you to book a cab based on your needs, such as how many seats you want, any color choice, any kind, or you can pool if you're riding with other people, and much more.14. Cleaning Services appsUsing such applications, the user may explore and search for cleaning services by filtering them based on their budget, reviews, and other factors. They may book the cleaning service for their automobile at a time that is convenient for them. Customers may also track the whereabouts of the service provider using the app's real-time location function. Finally, after using the cleaning services, the consumer should be able to pay securely using the app's numerous payment choices.15. News appsYeah, you have the radio for this one, but how do you filter between all the music and ads? Easier to use an app on the topic, category, and filter exactly what you want to listen to. Mobile applications for News are developing in the market to help with this. First, they provide their users with the news and information they desire to read. Then, they provide the facts in an easily accessible way that effectively guides consumers to the items of their choosing.16. Healthcare appsSuch smartphone apps aid in linking people with healthcare professionals to address health-related topics such as choosing the doctor from the list according to the available budget, scheduling an appointment, sharing reports and other medical details, and paying for the treatment, prescription, and other invoices.17. Mental Health appsUnfortunately, mental health is not taken as seriously as it needs to be, but here is why any startup could develop these ideas to help anybody in need. Such smartphone apps provide users with the professional abilities required to assist someone in need from anywhere on the planet. Furthermore, many applications include questions concerning suicide and self-harm. Following that, the app determines the safety issue based on the responses it gets.18. Weather appsWhy not learn the weather before it starts raining? It might make a difference between the two. An app of this type should have features such as local weather, a weather map, and weather widgets. For example, it should inform the user of the current weather conditions in their area. Furthermore, such applications must include information on air pressure, visibility distance, meteorological conditions, relative humidity, dew point, and other factors.19. To-do list appsWe all have lists of things we need to do or buy or so. I think it comes with age when you start forgetting things, but I like to say that it’s an effective method of systematization. To-do list applications allow you to arrange your chores and meet your deadlines. Furthermore, such applications may be used to manage everything from grocery lists to work-related activities and much more. As a result, this is the ideal strategy to make your life easy when it comes to getting things done.20. Auto call answer appsSuch apps enable users to answer an incoming call without even touching the smartphone's screen. This software is designed for self-use and works well without the need for a Bluetooth headset. It instantly switches the user to speakerphone so that he can hear the caller. The user can toggle it on and off as needed.21. Real-time voice to text messaging appsThis app is designed to convert audio to text in real-time for taking notes. These are useful for professionals who are often on the go and driving. If you think faster than you write, such applications will help you enhance productivity while also safely storing your sound and recordings in the cloud. Furthermore, these apps should have shortcuts, accuracy, and language support.22. Email appsEmail applications have been a popular online communication tool for both personal and professional uses in recent years. These applications allow users to easily read, send, and receive emails on their devices. These tools save you time while also keeping your emails secure. Push notifications can even provide you with information about your emails without you having to open them.23. Blockchain appsBlockchain mobile apps have the potential to improve all major sectors. That is why Bitcoin is ideal for mobile app concepts. A blockchain tax and invoicing tool, for example, would be ideal for determining the amount of tax that users must pay depending on their income. Now move everything on the car’s dashboard for people on the go.24. eCommerce appsIt’s the best, easy, and most convenient way to shop without actually going shopping. The user can search for any product, of any range, of any type, etc. The eCommerce app list varies from products of wide ranges. The payment method is also easy; the user can pay online or choose cash on delivery option.appssemble helps companies implement digital transformations through knowledge and experienceIf you have a trendy app concept, you should contact appssemble, an experienced and professional app development firm. We will assist you with obtaining finance for your app, determining the best strategies to make your app a success, and many other important parts of beginning your company adventure. These app ideas for beginners might help individuals earn money while also solving issues. --- ### What are great car sell-buy apps made of? URL: https://appssemble.com/blog/what-are-great-car-sell-buy-apps-made-of There are so many options when it comes to choosing a car sell-buy app, here’s what to keep in mind in order to make yours different, if not the best on the market. We are back with another article of the series What are great apps made of, where we talk about various types of apps, how their business work, who’s their target, and what it takes to build a great app in that field. Today we chose the car-selling/buying apps. You know, those spots that everybody visited at least once, to see if they could find the car they wish they have or to just browse for new cars on the market.Whether it's a first-time purchaser searching for their first secondhand car or a classic car collector hunting for that beautiful vintage model, used car sites simplify the buying experience with thorough searchable listings, automobile reviews, buyers' recommendations, and more. However, used vehicle websites are more than just a resource for purchasers; they are also a wonderful resource for sellers to locate a buyer (sometimes many purchasers) for their used automobile.ProblemDriving a new car is thrilling, but performing the research that goes before buying a new car might be intimidating if you have to visit car parks. Buying cars online offers several advantages over in-person dealerships. You have to travel to different locations where the vehicles you're interested in are, analyze them on the spot in a short span of time, with possibly little-to-no knowledge because, let’s be honest, not everyone knows what to look for when buying a car, its perks and flaw, and you can't always drag an engineer or auto service employee with you to check it, therefore leaving you with limited expertise on what you're buying. Not to mention that before you can take your new automobile home, you must negotiate a fair price.So it can be a complex process that requires a lot of energy, time and knowledge. I ask you know, why should you do all of that anxious and pressing process when you can simply just lay relaxed on the couch and scroll through the app’s posts where you have at reach all the information about the car you're interested in, you can even send a simple link or a screenshot of the product description to a specialized friend wherever he is on this big beautiful planet, and ask if you're investing in something qualitative and if it's worth it, and once you’ve decided and chosen the perfect one, you can simply just go see it and check if you feel comfortable in the driver's seat.SolutionIt used to be difficult to sell your car in the past, you needed to take it to a dealer or to a car park. The dealers would give as low a price as possible to secure a high profit, or if you’d have sold it yourself, you probably would have ended up being one of those who sat in a car park on a Saturday and Sunday morning and presented the vehicle to interested buyers and then allow them to drive it around for a bit so they can check it. Time-consuming and tragic, I know.Fortunately, the internet has altered all of that. Today there are plenty of options to sell your automobile online, all of which promote it to a far broader audience than the conventional techniques ever could because you were quite limited back then.You may also be as active in the transaction as you like thanks to the different internet choices. If you're up for the task, you can interact with customers directly and handle everything yourself, or if you have other things to do with your time, you may now spend a few minutes inputting your car's data on the app’s page, then accept money from a specialized auto buying business and have them pick up the car from your home. Some sort of dealership but you can control the process tidier.There are applications for the die-hard car aficionado hunting for that obscure contemporary classic. There are also applications available for those seeking a simple means of transportation to get from point A to point B. There are several applications available that alleviate the stress of acquiring a vehicle. These are our top picks: AutoScout24, Autovit & AutoTrader.DemographicsAccording to Google’s statistics, 95% of vehicles buyers use digital as a source of information. Twice as many chose online research instead of a dealership.V12 says that “52% of car shoppers feel anxious or uncomfortable at dealerships. Millennials lead the pack in their dislike, with 56% saying they’d rather clean their homes than negotiate with a car dealer”, and I find that beautiful, cuz I’m one of those anxious Millennials who prefer mobile apps versus face-to-face negotiations.Business ModelThe success of an on-demand online buy and sell used automobile mobile app is partly dependent on the sort of business strategy you adopt for your firm. So, before you begin the process of hiring a mobile app developer, it is always a good idea to understand your company's needs, who you want to target, what sort of services you want to offer, and compare rivals, and understand the workflow.Dedicated Car Buying and Selling AppThis is a business strategy that is typically explored by organizations with many operational offices in various places. A specialized automobile sale and buy app business model will give a specific platform to company owners and automate their sell and purchase procedure. Additionally, business owners can promote available autos for sale, and consumers can submit a direct enquiry and proceed with the transaction. Furthermore, the app's owner has complete control over updating, deleting, and removing the listed automobiles from the app.Model for an Aggregator Car Sell and Buy AppThis is a sort of app concept that serves as a platform for buyers and sellers to sell and purchase vehicles. The app owner's primary purpose is to provide a platform for sellers and dealers to publish adverts, display automobiles of various models, and allow buyers to seek better options that meet their demands. As an app owner, you may profit from every transaction done using this app model.RevenuesCustomers' buying habits and requirements have shifted as a result of technological advancements. The growing use of mobile applications has altered the way consumers shop for little and large purchases. And purchasing or selling an automobile is no exception.Classified firms provide consumers with the ease of checking the availability of used automobiles on the platform, their specs, the number of years it has been used, and the price by releasing an app. Furthermore, before making a final decision to purchase an automobile, customers may look at other parameters such as a model, average mileage, speed, and more.While the world is rapidly moving toward digital solutions, businesses are rapidly shifting from conventional to digital platforms.However, vehicle investors are in a quandary regarding how to produce prospective money from the business investment in establishing a buy and sell car mobile app. If you're in the same boat, we've compiled a list of the finest revenue-generating policies for your on-demand online vehicle purchase and sell mobile app.commission fees on purchase - This form of monetization scheme is ideal for vehicle investors since it allows them to charge sellers a commission fee on each transaction done on the app. You may either specify a fixed sum for the purchase or a percentage based on multiple amount scales.listing fees - If you are establishing an aggregator model and offering a platform for your user base, it will be a perfect chance for you to charge sellers a listing fee. You may establish a preset amount for the number of listings so that your app generates more cash.in-app ads - It will be a wonderful choice to provide third-party vehicle firms advertising space in your app in exchange for a price to run an advertisement on your app. When selecting this form of income source, be sure you include relevant adverts to promote client engagement.MarketingThe following are some important strategies and key factors to consider while advertising your auto and vehicle apps. These suggestions will boost the exposure and rating of your auto and vehicles app.Don't dismiss the power of social mediaSuch options include Facebook, Instagram, Twitter, YouTube, Quora, Reddit, and many more. You may use these channels to spread the news about your mobile app and assist users in achieving their objectives. This strategy works even if your mobile app was designed just to assist consumers when they are on the go.EventsTalking about your app with others or spreading the word about it at an event may be incredibly beneficial. It is excellent for you to interact with people in your vocation whether you are attending an event, delivering a presentation about your app, or simply visiting to observe the new applications or technologies offered in the event.InnovationThe Internet provides several advantages to app creators and owners who understand how to exploit this new technology. We recognize that developing this sort of software is not easy, but the benefits it provides urge developers to continue along this path and help drivers who wish to enhance their driving abilities or car performance.Local MarketsIf you invest in a plan to acquire new customers only to have them delete your mobile app, you've squandered your money. There, you will understand the significance of having a focused audience. It would be beneficial if you targeted customers who are interested in your mobile app and have a high value.Enhance your Google SERPsDo you know that the majority of people use Google to find a new car? According to a recent Kenshoo poll, over 70% of consumers utilize Google or other search engines when looking for new automobiles. Visitors and clicks are always concentrated in the first few or top rankings. That is why it is crucial to keep your app in the top place since it is critical to the success of your automobile marketing strategy.Competitor keyword biddingWhile we're discussing how to advertise your auto and vehicle applications through search engine marketing, it's critical that you don't only bid on obvious keywords. Instead, you must budget for your competitors' keywords before you can launch an effective automobile marketing campaign. Remember that car marketing or promotion is very competitive, therefore you are constantly at odds with your opponent. A great ad copy, which is your key to success, is another item that requires your undivided attention.Deal with one user at a timeThis is especially critical in the early stages. Your major focus should be user retention rather than user acquisition at first. By delivering the greatest services, you may try to turn them into devoted clients. Ask them questions regularly, listen to and comprehend their criticisms, give your assistance, and make every effort to keep them pleased. There is no greater marketing approach than word-of-mouth promotion.Offer a helping handNot all of your gestures and activities result in the appearance of an app download button. Find users who are having issues, and if you can help them, give answers, and the app downloads will come later as a result!Build a community This is true for all mobile apps and enterprises. Building a community is crucial nowadays, and social media platforms are an excellent location to do so. Finally, surround yourself with people who share your goals and care about the same things you do.ProductWhen you are unsure of what to put in your app and what features and capabilities you want to offer, developing an on-demand automobile selling and purchasing an app is a difficult task. Before you begin, you should have an idea of the functionality you will require in your app. However, in order to assist you in developing a successful mobile app, we have prioritized the following features and functionaBuyer’s profile panel: Signup screen: Like all other applications, this one asked consumers to fill up basic information such as their name, contact information, email address, and so on. With social network integration, users can sign up for an account with a single click, and all of their information is instantly updated in the app's backend.Search box: Allow consumers to filter automobile alternatives using numerous criteria such as car model, price range, color, brand, and more using this functionality. Allow purchasers to use different filters to narrow down the best-suited features. Search options may improve the user experience.Compare cars: Since the main reason for using this app is to find cars at the most competitive rates in the user car market, this function in your app will not only allow users to compare the costs of the cars accessible on the app, but also identify variances in mileage, characteristics, and more.Vehicle exchange: Include an automobile swap function to help consumers understand how much value they would receive if they exchange their cars. All they need to do is provide information on the automobiles, such as specs, models, and so on.Contact dealers: It is critical to integrate this functionality in the aggregator business model and allow buyers to directly contact dealers for final negotiations.Message request: Allow buyers to send direct messages to dealers for any reason, such as pricing quotations, automobile specs, and so on.Schedule an appointment: Using this in-app tool, buyers may schedule an appointment and meet the sellers at a public location for a final discussion. They may also organize a test drive at the meeting to ensure that the automobile is in good working order before finalizing a purchase.Loyalty programs: To enhance customer loyalty and extend the client base, it is worthwhile to provide customer loyalty points on every transaction that can be redeemed against the real bill amount.Multi-payment option: in this day and age, individuals employ a variety of payment ways. implement this functionality and allow buyers to pay using a variety of payment options such as credit cards, debit cards, PayPal, and others.In-app chat and call: it is recommended to have an in-app call and chat option to discuss any type of inquiry such as vehicle models, discounts, negotiations, and more to ensure seamless communication between clients and dealers.Seller’s profile panel:Signup screen: Just like the buyer's panel, provide a signup method for the sellers' profile. Allow the seller to sign up for an account using an email address, contact information, or credentials permitted by the administrator.Car Listing: Allow vendors to display different car models under different categories so that customers may simply sift the possibilities based on their needs.Specifications: Allow vendors to provide all automobile model characteristics, such as price, mileage, average speed, and more, to improve the customer experience.Messages and Inquiries: Add a function to the seller's panel that allows them to read messages and enquiries sent by users, as well as respond to all of them.Multi-payment: This is one of your app's most significant features. You can make it function flawlessly by hiring an app developer and implementing a multi-payment interface that allows retailers to move money via numerous payment channels.Offers & Discounts: All sellers should publish discount offers, discounts, or promo codes on various automobile models in order to attract more clients to this platform.Service Center Specifications: Handle any buyer inquiries about secondhand automobiles and roadside assistance services.FeaturesIt is crucial to acknowledge that a mobile app should not be confined to a simple catalog. To be competitive in the automobile business, the application must be as beneficial as feasible.Must-have FeaturesBeing able to create a user profileA uniform customer baseViewing locationGeoforcingAdvanced searchCar pagePush notificationsBookingChatAuto serviceCommentsContactNice-to-have FeaturesThe ability to sell parts onlineSettlement of accounts with suppliers and car ownersAutomation of all computer processesIntegration of the dealer's mobile application with their website and emailPrinting the necessary documents from templatesReports on managers, sales, cars and other parametersImplementation of newsletters via SMS and emailStatic advertisingAuto inventory servicesCollection of information on consumer preferencesTo conclude this article, it is correct to state that creating an online used vehicle sell and purchase software is a difficult undertaking. While it is interesting, dependable, user-friendly, and informative, you must keep certain factors in mind to ensure that your app works on the same pitch. If you intend to create a mobile app similar to AutoScout24, Autovit, or AutoTrade, it is worthwhile to hire a mobile app development company that can provide better leads to sellers from the comfort of their own homes.If you have a strategy in mind or are seeking new ideas, it is worthwhile to talk with our professionals to develop a solution that will provide your company with a competitive advantage. appssemble’s specialists will incorporate the latest technologies and methods in app development to ensure that your app works properly, resulting in an unrivaled quality solution. We’ll be waiting for the next best car buy/sell app idea from you. Until the next article, purchase carefully. --- ### Short guide to developing apps for Android Auto URL: https://appssemble.com/blog/short-guide-to-developing-apps-for-android-auto Apps for Android Auto, focus on actions tailored for in-car use, such as navigating and listening to media or messages. Learn how to create apps for Android Auto in various ways, depending on the app type. As we’ve previously stated in the Short Guide to developing iOS apps for CarPlay, smartphones, the apps and the need for all of them are quite obvious, just imagine how much they ease your life. The growth of systems such as Android Auto, Android Automotive OS and CarPlay is now on the rise, and it's easy to see why when you look at their features and how they function.Android Auto and CarPlay rely on phones to power the entire car-optimized experience and considering that everyone has a smartphone in their pocket, it's easy to see why so many people find it quite handy to reflect the interface on the larger screen in the cabin. While Android Auto appears to be a success, Google has been investing in a far more complex automobile experience driven by Android Automotive.What exactly is Android Auto?The Android Auto system works by connecting a phone to a compatible car and allowing drivers to interact with their phone's apps through the car screen and voice commands. It makes it simple to explore, listen to media and communications, and do other things.Android Auto offers a driver-optimized app experience to consumers who have an Android phone and the Android Auto app but do not own a car that runs the Android Automotive OS. If a user's automobile sound system supports Android Auto, they may connect their phone and utilize your app directly on their car's display.You, as a developer can create services that Android Auto can use to display to the driver. These services are reused for your Android Automotive OS software, but consumers do not install your phone app on their automobiles.How does Android Auto work?1. On the phone's screenIf your car does not have a suitable HU, you may use the solo Android Auto App on your smartphone or tablet. Following app startup, a car-friendly UI appears and is ready for usage. The app is easy to browse owing to somewhat bigger UI components that reduce the number of misclicks.On the main screen, you'll see the currently playing music or podcast, recommended driving destinations, and alerts as they arrive. There is also a button for configuring Android Auto settings, such as Google Assistant, so that you may perform voice commands.2. On car displayYou may also utilize an Android Auto compatible automobile entertainment system (currently over 500 models are supported and even more should come soon). It is simple to run Android Auto on a vehicle display; simply connect your smartphone via USB connection (some phones also enable wireless connectivity) and your applications will mirror on it.What type of apps can be developed for Android Auto?1. Messaging appsVoice-based messaging allows drivers to communicate while keeping their eyes on the road. The messaging app template in Android Auto has a common navigation mechanism for all messaging applications. Apps that use this template only receive and reply to text-based messages, converting text such as SMS and email to audio.2. Media appsThe media template is intended for apps that need little input and provide a constant stream of audio information. The media template in Android Auto has a common navigation paradigm for all audio apps. Users traverse browsing views in this paradigm to discover and pick playable content.3. Navigation, Parking & Charging appsThe Android for Cars App Library includes vehicle-optimized templates for app developers to use when creating three types of Android Auto apps: navigation, parking, and charging apps. App developers may alter both the templates and the order in which they appear to construct user flows inside their apps. Android Auto adjusts the UI to all supported vehicles automatically.4. Custom appsAndroid Auto is presently developing custom applications in collaboration with a number of partners. Android Auto apps should have a clean, flat structure so that drivers do not have to remember where they are in the app. Designing a flat hierarchy entails displaying the core app features on the primary app screen and navigating to supplemental information via the drawer.General design guidanceThe central aspect of Android for Cars is "design for driving." The driver's primary job is to drive safely, so this priority must be reflected in every design by automakers and app developers.The app's information and interactions should complement the driving experience while reducing driver distraction. To keep the driver's eyes on the road and hands on the wheel, the user interface must be concise. Here is what you need to learn about designing interfaces for cars:1. Interaction principles2. Visual principles3. Style foundations4. System UI1. Interaction principlesInteractions between a driver and a screen must be straightforward, non-distracting, and readily interrupted in order for the driver's focus to return to the road.2. Visual principlesContent created for a vehicle screen must be clear and glanceable, with a consistent user interface and big touch targets that drivers can distinguish in all lighting circumstances.3. Style foundationsThe Android Auto style is based on the same interaction design and visual design principles. However, due to the unique context, the style and layout details for these systems differ in some ways.4. System UIThe Android Auto UI comprises a navbar that allows you to access important functions, a primary app content area, and a status bar that shows system information. The status bar provides information about the time, weather, and system status. The app content section below it displays either the app launcher or content from the main app presently in use.The navigation bar gives you access to the following:The application launcherA widget that contains controls for a second, running appThe Notification CenterThe Assistant, for voice-based interactionsAndroid Auto design systemThe UI for Android Auto, covers colour, typography and visual elements that are built strategically to improve the visual clarity on car screens. Therefore, Google Developers offers quite visual examples for their guidelines.There you have it, a short guide to developing apps for Android Auto, apps that focus on in-car functions such as navigation and listening to media or messaging. If you're planning to create an app compatible with Android Auto from start or modify an existing app, you must consider all of the requirements and restrictions imposed by Google on such apps. Depending on the app type, you as a developer may create apps for Android Auto in a variety of methods. See Android Developer for more information.As we’ve said before, building an Android app is quite accessible and easy for an experienced Android developer, and even if you’re a beginner, give it a try and test your boundaries. And if you ever feel overwhelmed, then we are here to take this issue out of your hand. Contact us and let our professionals build the project you desire. Until the next one, keep your hands on the wheel and drive safe! --- ### Short guide to developing iOS apps for CarPlay URL: https://appssemble.com/blog/short-guide-to-developing-ios-apps-for-carplay CarPlay is a more intelligent and secure way to use your iPhone in the car. Learn how CarPlay works and how to configure your car's infotainment system to function in tandem with your iPhone. I’m pretty sure not everybody will approve, but nowadays, a smartphone and a car are pretty indispensable. Just stop for a few seconds and imagine what would you do if you would have to “survive” for a week without a smartphone or even without a car. Now, I’m not saying it would be impossible, but you’ll have to agree, it would be a pain in the back having to figure out pretty much everything without a search, calling/texting a friend, or an app telling you the answer.We build our routine based on electronic devices and we need comfortable transportation to commute to our jobs or go shopping for a full list of groceries or even travel. Now more than ever, since the pandemic made us go remote and rely on technology and individual transportation, we made use of inclusive platforms and systems that serve multiple purposes, like CarPlay, to ease our life and make everything more accessible and easy to use.What exactly is CarPlay?Apple introduced around 2014, “The ultimate copilot” - CarPlay. Now, what exactly is this and what does it do? CarPlay is an extension of iOS that enables a car’s infotainment system (aka the built-in entertainment and information system) to display and control a range of apps. Streaming music, dialing into a meeting, finding a car park, and ordering food, are just some of the apps you might consider enhancing to take advantage of the maturing CarPlay platform.CarPlay allows any iPhone (from iPhone 5, all the way to iPhone 13 Pro Max) to interface with the car’s infotainment system (mainly with the built-in dashboard screen that controls the radio, making calls and navigation).Once more, convenience prevails and this time, the distraction of a phone is replaced with the infotainment display that contains users' commonly used apps that are necessary and useful while driving. By doing so, CarPlay minimizes the need to handle your iPhone while driving. You can dive into more details on Alexi Schreier’s article A Developer’s Intro to CarPlay.What are CarPlay apps?Fortunately, Apple allows app developers many possibilities to build something that might be perfect for CarPlay, but before you jump to conclusions, you must also know that Apple restricts quite a lot of apps that CarPlay can enable, so the type of apps that you can develop are:Audio apps (Music, Podcasts, News)Communication apps (Messages, Calls)Navigation appsEV charging appsParking appsFood ordering appsCarPlay allows developers to make their products for safer use in cars so that there will be fewer accidents caused by distracted drivers using their mobile phones. As good as that sounds, there’s still a shortage of information on how to develop an actual CarPlay enabled app.What niches should you pay attention to when developing?Traffic safetySafety and liability insuranceFuel-saving applicationsHealth and ergonomicsCan I integrate CarPlay into my existing app?You could do so, but it is recommended to create a new one that complies with all CarPlay legal criteria. CarPlay apps are meant to appear and feel similar to your iPhone app, but with UI features comparable to built-in CarPlay apps. It must be in accordance with certain dimensions.If the application's purpose is to send and receive messages, you must utilize SiriKit's Messaging, especially for speech interactions. The user flows must be acceptable for use while driving and must be feasible without the use of an iPhone.At appssemble we’ve learned the process of developing iOS CarPlay apps and what it takes to shift a music player app or a phone call into a CarPlay experience.How to develop a CarPlay app?1. CarPlay app entitlementA CarPlay app entitlement is required for all CarPlay apps. Go to the Apple's site and put information regarding your app, along with the CarPlay app category. In addition, you must agree to the CarPlay Entitlement Addendum. Apple will look into your request. If your app passes the CarPlay app eligibility criteria, Apple will generate a CarPlay app entitlement and inform you.2. Assess your entitlementAfter receiving a CarPlay app entitlement, log in to your Apple Developer account and create a new Provisioning Profile that contains the entitlement. Once that is done, import it to Xcode. E.g. app Entitlement key: com.apple.developer.carplay-navigation (depending on the type of app you’re requesting an entitlement for)3. Add the new key to Entitlements.plist file4. Add the below key in info.plistThe example given contains an app that declares 2 scenes - for iPhone screen and one for CarPlay screen. The name of the class that serves as the scene delegate is defined in the manifest by UISceneDelegateClassName. Your delegate must conform to CPTemplateApplicationSceneDelegate.Once your app is launched, you’ll be notified with a CPInterfaceController that manages all the templates on the CarPlay screen. Hold onto the controller since you’ll need it to manage templates, such as showing a now playing screen or an alert. On launch, you must also specify a root template.6. Write the codeSince CarPlay apps are made using templates, here are the types of templates which can be used in the CarPlay app:Action Sheet templateAlert templateContact templateGrid templateInformation templateList templateMap templateNow Playing templatePoint of Interest templateSearch templateTab bar templateVoice Control template7. Test it on SimulatorThe Simulator may be used to test CarPlay applications, but while Simulator is useful during development, many CarPlay features are not available in it, and you should not rely on it as your main means of app development. To start, select I/O, External Displays, and CarPlay to bring up the CarPlay screen.It is strongly advised to create and test CarPlay apps on a vehicle or aftermarket system that supports wireless CarPlay. This allows you to use CarPlay wirelessly when your iPhone is connected to Xcode on your Mac via a Lightning to USB cord.How much UI does CarPlay accept?Well...not much to be honest.For example, music player or podcasts apps are pretty restricted by Apple, and the UI displayed in the car’s dashboard screen is very strict and allows no customization of the provided template. Looking at the bright side, it all means less development work and easier to implement.On the other side, to the navigation apps, CarPlay gives more freedom of expression, to customize the UI and how the details are structured and displayed to the user. It’s good on one side and a little bad on the other because this whole thing means that it requires more development work compared to the music player app.The biggest policy is given to the car producers, who are free to customize the CarPlay UI as they please.In the table below, you can view each of the different CarPlay UI templates as well as the app categories that are accepted by each:As we’ve said before, building a CarPlay enabled app is quite accessible and easy for an experienced iOS developer, but even if you’re a beginner, you should give it a try, test your boundaries. And if you ever feel overwhelmed, then we are here to take this issue out of your hand. Contact us and let our professionals build the project you desire. Until the next one, keep your hands on the wheel and drive safe! --- ### How to choose the right mobile app development team structure URL: https://appssemble.com/blog/how-to-choose-the-right-mobile-app-development-team-structure A good grasp of the mobile app development team structure can assist you in selecting the best partner and effectively building your project. Why is it important to have the right development team structure?People are the key to your product's success. Even though the absence of some professionals appears to be normal during the development process, it may have an impact at the end of the day.A good grasp of the mobile app development team structure can assist you in effectively building your project and finding market success. This is true regardless of whether you are outsourcing or developing your app in-house.Modern app development is far more complicated than the old "man in a garage" style of the past. Depending on the size of the app, dozens of people may be required to make it a reality and a success.For instance, if you recruit a high-end designer but your team lacks UX experience, you'll wind up with a fantastic app with amazing visual effects but no one will be able to grasp it, because they will be puzzled or disoriented within it. Without such professionals on the team, you will have finely developed apps with second-to-none capabilities of fulfilling the demands of consumers.What type works at appssemble?Each workgroup is a complex and dynamic microorganism with its own set of employees and regulations.appssemble’s company goal for mobile app development team members is to have diverse team members who fully reflect our expertise. We have both universal troops and profound specialists on staff that are dedicated and thorough while also being adaptable. We've managed to establish quick and clear communication inside the organization over time, and we're happy to collaborate on any project, no matter how big or small.Key roles in the mobile app development team structureAs I previously stated, a mobile app development team is a living creature that works on numerous tasks through collaborative efforts. What counts most are the talents and abilities of each member of your project's crew. It is now critical that you understand the duties and responsibilities of each member of your application development team. The traditional plan is as follows:Project manager / Product managerUI/UX designersiOS/Android developersBackend developersQA engineersProject manager / Product managerWhen you bring your app concept to a mobile app development business, you'll be assigned a project manager who will act as your assistant and link with developers. A project manager is in charge of a project from inception to end, according to the agreed-upon budget, timeline, and quality. A project manager is primarily concerned with the performance of the app development process, deadline adherence, and quality standards based on the product manager's visionA product manager is frequently used interchangeably with the project manager. However, while each of these professionals are managers, they do separate duties and have different obligations. The distinction is in what they are managing - a project versus a product. A project is defined by a precise plan of activities and start and finish dates. A product must provide continual value to users and has no temporal constraints.Project manager’s responsibilities:Assigning tasks to the development team, establishing sprint periods, and prioritizing tasks;Calculating your project's cost and remaining inside your budget;Increasing communication between you, the client, and the developers;Making modifications to the app development strategy;Managing issues and risks;Maintaining quality, meeting deadlines, and keeping expenses under control.Product manager’s responsibilities:Analyzes the market, specify the advantages, values, and essential features of your app, and investigate your target audience;Identify consumers' critical issues and provide best answers;Create an app development business strategy;Prioritizes useful app features;Extracts a distinct value proposition and assists you in developing a strong call to action.UI/UX designersBefore anything else, you should be aware that User Experience (UX) and User Interface (UI) are distinct yet related concepts. To clarify, UX refers to how a user interacts with a product, whereas UI refers to the aesthetic aspect of the product. The primary responsibility of the UI/UX designer is to provide a satisfactory user experience by designing an app that is simple, intuitive, intriguing, and engaging.Designer’s responsibilities:Make a user personas;Consider the user flow and create app wireframes;Make app prototypes;Create a user-friendly app UI;Changes should be made in response to user input and testing data;Working knowledge of UI/UX design tools such as Figma, InVision, and Sketch;Knowledge of UX research, wireframing, UI prototyping, UX authoring, and interaction design is required;Coding knowledge can be required in order to communicate effectively with programmers;iOS/Android developersThe iOS and Android operating systems have different development languages and requirements. That is why each platform requires its own set of developers. Your intended audience and budget will determine whether you should design your app for one or both platforms. Android and iOS developers, in general, are in charge of the technical aspects of mobile app development.Developers' responsibilities:Creating high-quality code from drawings, mockups, and wireframes;Developing and sustaining reusable, dependable, and high-performance code;Providing the highest quality, performance, and responsiveness in mobile apps;Addressing app flaws and resolving issues.Required skills for iOS developers:Mastery of Objective-C and Swift for the creation of native apps;Understanding of the Xcode IDE – the primary development environment for macOS, iOS, and iPadOS apps — is required;Understanding of how to create apps for the most recent iterations of iOS.Required skills for Android developers:Knowledge of the Kotlin and Java programming languages is required;Proven expertise with Android Studio, the Android app development environment;Capability to create an app that works with a wide range of Android versions, devices, and screen sizes;Backend developersWhen the backend developer comes into action with its advanced logic and algorithms, all the magic happens beneath one roof. The backend developer is in charge of keeping a server up and running, as well as cloud storage and operational logic.Backend developers’ responsibilities:Data storage, security, and presentation to the appropriate user;Managing payment systems that can access and securely store data in order for users to make payments in-app;Application programming interfaces (APIs) are used to communicate between the server and devices;Creating device-specific operating logic;Framework development and app architecture;Using databases, integrated development environments (IDEs), and collaborative tools;They should have hands-on expertise with a programming language such as Java,.Net, Python, PHP, or Ruby is required;QA engineersA quality assurance (QA) engineer's major responsibility is to monitor every stage of mobile app development to ensure that the design and software satisfy all requirements, uncover app faults and bugs on time, and assist you to reach project release dates and stay under budget.QA responsibilities:Conduct both automated and manual testing;Maintain a record of test progress and test cases;Throughout testing, keep track of bugs;Identify probable issues that users may encounter;Create stringent testing guidelines to determine app quality and release readiness;Strong knowledge of QA testing technologies such as TestComplete, Robotium, and Selenium;Understanding of feature and bug tracking systems such as Jira, Trello, etc..Stages of a mobile app development teamThe app development process involves more than just coding and designing. Turning an app concept into a real app involves a lot of expertise, effort, and money obviously, as well as tech support throughout the app's existence.To make it easier to identify the software development team members who participate in each step, we've separated the app development process into five major stages.DiscoveryAt this stage, you must describe the app's goals, values, and features, assess competitors, determine the target audience, and create mockups to envision your app. You must produce a low-fidelity app prototype at the conclusion of the discovery cycle to ensure that you and your development team are on the same page.You should include a project manager as the essential person in controlling the whole app development process throughout the discovery stage. You may also enlist the assistance of a product manager to delve further into your target consumers' ideas, requirements, expectations, and motivations for using your app and making in-app purchases. You should also include a UI/UX designer in the brainstorming phase, create a business idea, and turn the outcomes of the discovery stage into visual mockups of the initial app prototype.Idea validationAt this point, you should concentrate on establishing your active and paying customers as well as validating the relevancy of your app by inviting a group of individuals to test your app prototype. Based on beta tester comments, you may begin to create a medium-fidelity app prototype that depicts your app's UX design and flow.When you begin to validate the app idea, you will need to pitch in all of the team members, including a project manager, a product manager, and a UI/UX designer, as well as a QA engineer for testing, an iOS developer, an Android developer, and a backend developer to create a medium-fidelity app prototype.UI/UX strategyThis is the stage at which you begin to develop a user interface in depth. You should design a high-fidelity app prototype that is interactive so that your testers can test the app's navigation and provide input on its usability.When it comes to validating the app idea, you'll need to bring in all of the team members, including a project manager, a product manager, and a UI/UX designer, as well as a QA engineer for testing, an iOS developer, an Android developer, and a backend developer to create a medium-fidelity app prototype.Design and developmentAt this point, your app development team begins coding and developing a minimal viable product (MVP), which is a feature-oriented product with an appealing design and a user-friendly interface but is not yet a fully-fledged mobile app.The UI/UX designer, iOS and Android developers along with backend developers bear the majority of the load during the design and development stage. They report to the project manager and interact with the product manager on a regular basis.Testing and improvingThis step presumes to examine the user experience in order to resolve any crashes or issues and make any changes necessary to make your software the best it can be. You may add new app features on a regular basis and assess their usefulness. This will result in the creation of a fully working and successful app.If your objective is to get your app to market as soon as possible and you have a large enough budget, you may engage more IT expertise to help you construct your app faster. If you're starting on a tight budget, you may minimize your app's features, begin implementing your app on a single platform or engage only a few professionals.If you are having trouble evaluating your app development expenses and determining the ideal development team size, you can contact us for a free consultation.Types of a mobile app development teamNow that you understand the mobile development team structure, the distribution of app development team duties and responsibilities, and the right app development team size for your project, it's time to work out the best strategy to acquire mobile application development expertise for your project. We've identified five approaches for hiring experts to create your app:1. In-house developersThey are professionals that work solely on your project and are based in your workplace. You may handle the app development process and hire team members on your own if you have an in-house development team.2. FreelancersThey are beneficial when you need to engage specialized individuals with a high degree of competence to complete one-time jobs. You may contact freelancers directly, and they would most likely assist you in cutting costs. You may find freelancers by looking through their portfolios on freelance platforms.3. A dedicated teamThey are a group of remote IT professionals that you may employ from a third-party service provider. This team will include designers, developers, and QA engineers who will report to a project manager. While retaining employees of the third-party service provider, they will work on your project and interact with your in-house developers.4. OutstaffingThis means that a third-party development business will give you one or more professionals to supplement your team and provide vital skills in order to construct an app. Outstaffing specialists are third-party personnel that work as part of your development team and do tasks that you give to them.5. OutsourcingThis is ideal for delegating your whole project implementation from start to finish. Outsourcing is totally entrusting your app's execution to a third-party development business and abdicating responsibility for the end outcome.There you have it, the most important tips on how to create a successful mobile app development team. By now you should have a clear vision of each development team’s role and responsibilities. Employing a firm that already has a team of developers in place is typically the most efficient technique of an app development company.If you’re looking for more information, directions for your development team structure or looking to hire the best iOS or Android app development team, then you should meet our professionals and give them an insight into your project’s idea. Appssemble always keeps up with clients’ requirements and builds something professionally unique by understanding the culture of their business. --- ### Mobile startup trends on environmental awareness apps URL: https://appssemble.com/blog/mobile-startup-trends-on-environmental-awareness-apps Whether it's an app for measuring air quality, pollution, or water use, smartphone technology enables everyone to contribute to the planet's survival As the planet continues to warm, entrepreneurs start being more and more interested in startup concepts that address global warming. Startups may not be the answer to all of our problems, but with the right funding, support, and education, some raw ideas may blossom into world-changing businesses.For mankind to limit global warming, drastic and unprecedented adjustments are necessary. Global politics are important in achieving the goal, but private firms also play an important role. Many businesses work hard to decrease their carbon footprint, but few are willing to pivot and shift their attention to slowing global warming. Fortunately, an increasing number of companies are responding to the challenge and developing new, inventive solutions for a more sustainable future.Millennials are more concerned than previous generations with the social and environmental consequences of their purchasing and investing decisions. It's only logical that the number of sustainability-focused companies is growing as they become older and enter the workforce.Ecological innovationEcological innovation is an unavoidable trend for organizations seeking to increase their competitiveness and function responsibly in the framework of the green economy. Ecological innovation and green technology are quickly evolving throughout Europe. As the scope of the eco-industry grows, the output of the eco-industry is approaching EUR 2 trillion, which encourages economic growth and job creation in the European Union.This year has seen a greater emphasis on the environmental, social, and governance implications of enterprises. It implies that firms will have to place a greater emphasis on climate sustainability, raw material sourcing, production, and the global effect of their activities.Entrepreneurs throughout the world are addressing climate change issues front on by pioneering goods, services, and climate action tools through eco-friendly enterprises ranging from algae micro-farms to solar panelling design software (see source).Being environmentally conscious entails more than just taking care of the environment. It is a matter of taking the required actions as well as making a conscious effort to adjust your lifestyle to preserve resources. From using recycled or renewable materials to lowering energy usage and trash, it appears that organizations and startups are making a concerted effort to safeguard our planet and live a sustainable lifestyle.Why are environmental mobile apps important?Raising awareness may be accomplished through a variety of strategies and media. With the rapid advancement of technology, mobile applications may be the ideal tool for the job. Before we get into the apps that might assist raise environmental consciousness among the general public, it's crucial to understand why such apps are necessary. Many people dismiss these applications as unimportant, yet their importance is more than they realize. So, why are they important?Fast and easy reachWhen it comes to important concerns like the environment, issues need to be addressed as soon as possible and among a larger community. This may be accomplished through the use of media that practically everyone has access to. What greater tool is there than a mobile phone?In this digital age, most, if not all, of us carry a cell phone with us everywhere we go. As a result, a mobile phone application is bound to reach a larger audience than a TV commercial or a newspaper advertisement, both of which are frequently disregarded.Easy access for those on the goEnvironmental awareness may also be fostered via various blogs and webpages on the internet and yet have a large reach. That is an excellent strategy, but it is not as practical for individuals who are not in the comfort of their own homes.Mobile phone applications may be quite useful for folks who want to help save the environment but are always on the go. These applications are extremely beneficial since they offer users the information they want when they require it, without requiring them to conduct extensive research.ConvenienceMany of us want comfort and ease in all we do. And if we don't receive that, we're not going to do it. Increasing one's consciousness is no different. When it comes to individuals having the convenience of a mobile phone application at the tip of their fingers and being available anytime they want it, the odds of them learning from these applications simply increase. As a result, these mobile applications can be more effective than any other source in raising environmental consciousness, making them a significant development in the modern-day.Types of mobile app feature to help with environmental and climate changeCarbon dioxide levels are at their highest in 650,000 years, according to NASA, reaching a number of almost 8.000.000.000 tons of CO2 emitted into the atmosphere. The recycling rate dropped from 34.7% in 2015 to 32.1% in 2022, not to mention the 10 billion tons of freshwater waste worldwide daily. Our planet is covered 75% with water, but 97.5% of that water is saltwater, with only 2.5% fresh water to drink. Check this cool live-count of water usability by The World Counts.These figures are frightening, especially since climate change increases year after year. Fortunately, smartphone applications can aid in environmental awareness and the battle against global warming if you follow the guidelines. Smartphone technology, whether it's an app for measuring air quality, pollution, or water use, enables everyone to play a role in helping to save the world.Tell us your environmental awareness app idea, and let’s build one that includes features such as promoting greener lives, recommendations for reducing CO2 emissions, and other actions to help people be more eco-friendly.Monitoring carbon footprintsIncorporating carbon footprint calculators to discover how daily acts affect climate change.Giving people the option to track the development of their carbon impact.Questionnaires to calculate a user's personal and unique carbon score to assess how much CO2 they emit. Users may then adjust their lifestyle accordingly, such as reducing their power use or increasing their use of public transportation.An environmental awareness app can give users individualized suggestions on how to reduce their environmental effects and use resources more efficiently.Localized content can assist people in discovering sustainable projects near them.Users can compete in competitions to discover who can be the most environmentally friendly and sustainable.Yayzy is one app that helps anyone measure and reduce our impact on the planet. It fights climate change and can be used as our personal carbon footprint calculator.How Yayzy worksTrack your footprint on the go - From your online orders to your Uber trips, your itemised spending highlights the CO2 emitted from each activityUnderstand your carbon footprint - Uncover important insights in-app to help you monitor how your expenditure is impacting the planet.Embrace your growth - Keep an eye on your Yayzy tracker daily to reveal patterns, set goals & monitor monthly progress.Waste and recyclingA search engine that provides information on how to categorize various objects, such as plastics, glass, and cardboard;Providing timetables for trash and recycling pickup;Providing information about nearby depots where individuals may securely dispose of hazardous garbage;Providing a map of places and donation centers where individuals may donate goods such as clothing or furniture;It helps people live in harmony with the planet;It helps build a world that generates next to zero waste.ReCollect is a technology company that combines deep expertise in solid waste and recycling with technology that works for government and business organizations. Their team is composed of leaders in public policy, recycling and solid waste communications, behaviour change and technologyTheir mobile app, helps humans live in harmony with our planet, their vision is a world that generates zero waste and the mission is to arm organizations with recycling tools necessary to make a measurable impact on our planet.How ReCollect worksIt helps people stay connected - since people are digitally connected nowadays, their custom made mobile app allows anyone to receive information that they need, at the right time. There are notifications about updates to collection schedules, revealing places where to properly dispose of or recycle any material collections. It lets people access the app in real-time - if you have changes you need to communicate right away, the app allows you to stay connected to people in real-time. Whether anyone needs to make changes to proper recycling or disposal instructions, or update delays in the collection schedule due to weather, the changes are communicated quickly.It helps people self-serve - if people are being provided with reliable and accessible ways to self-serve, they take care of themselves and the world around them. The call volumes and customer support costs are reduced if the engagement between people is increased. Tracking water usageTracking and regulating personal water use.Alerts for leaks to help you reduce waste and expensive water costs.The ability to compare use to that of other neighbors.The ability to define and achieve water objectives, as well as track progress.Dropcountr connects people and their water utilities on the mobile devices they use every day.How Dropcountr worksYou can use it to understand and manage your personal water useYou can compare usage to similar neighborsYou can set and reach water use goalsYou can access valuable rebates and utility announcementsCommunity awarenessWe sometimes feel as if we have no control over the environment or how to make our earth a better, safer, and healthier place. But the fact is that any change begins with an individual, and you must begin with yourself. It's never been easier to live a greener lifestyle and make little adjustments to benefit the environment. There are eco-friendly applications available that can help you achieve tiny successes every day.OneSave/Day is an app built around environmental awareness by appssemble. Their mission is to become a crucial part of the overall climate change solution by turning millions of lifestyles into more sustainable ones.The Daily Saves facilitate the adoption of a responsible lifestyle and make it accessible to everyone through features that allow you to monitor your water usage carefully or warn you about leaving the lights on in the house, and so on. As a non-profit organization, they are fully committed to their values and act for the common good, so by using an app like theirs, you’ll be a part of a huge environmentalist family and learn about the best ways to cooperate to solve the climate crisis and save the Earth.Top fundings in environmental awareness appsCurrently, according to the hub, there are over 700 startups on Energy & Greentech in Denmark, Finland, Norway and Sweeden alone. European Commission started “Boosting Europe's green transition: Commission invests €1.5 billion in innovative cleantech projects” through Innovation Funds, one of the world's largest programmes for the demonstration of innovative low-carbon technologies, financed by the EU's Emissions Trading System. Throughout Europe, Village Capital and Visa Foundation are two other big investors that financed Startups with the Greentech Europe 2022 initiative.In Asia, four research projects led by scholars at the City University of Hong Kong receive grants worth HK$20.26 million, offered by the Green Tech Fund under the Environmental Protection Department of the Hong Kong SAR Government, to build startups that can help save the planet.In Jan 2022, CNBC published an article stating that “Bill Gates climate fund plans to mobilize $15 billion into cleantech” across the U.S., the U.K. and European Union, with a private-public fund named Breakthrough Energy Catalyst. Jonah Goldman, Breakthrough Energy managing director describes BEC as a “program to demonstrate how we can finance, produce and buy the new solutions that will underpin a low carbon economy”. BEC will initially focus on direct air capture, green hydrogen, long-duration energy storage, and then sustainable aviation fuel.Is using an app enough?While these mobile apps can be quite helpful in raising environmental awareness, the question remains: are they sufficient? Is utilizing these apps all we need to do to stop the detrimental changes in the environment and save our planet's quickly deteriorating state?No, it does not. But it is unquestionably a start. When it comes to fighting for a cause, we all need a place to start, and these types of apps, like Monitoring Carbon Footprints, Managing Waste and Recycling and Tracking Water Usage, may provide that beginning point. Sharing the lessons we learnt, if not the application itself, with people around us would be a terrific way to go ahead.For a long time, we've been on a countdown to rescuing the earth. According to scientists, we have only seven years to heal the Earth before it is irrevocably harmed by the effects of human pollution or seventeen years until we run out of freshwater. Because this is our only home, we must put greater effort into caring for it.You can be the change that the world needs. We are your support.This environment we live in is the only one known to sustain living forms at the moment. The repeated harm we inflict on it is causing it to decay at a quicker rate than we realize. We must keep in mind that if it fails to the point that it can no longer support life, we would have nowhere to go, which is why we should not simply ponder about boosting environmental awareness, and take a step today, even if it starts through a smartphone app. Therefore if you have an environmental awareness mobile app idea in mind, get in touch with us, tell us your plan, and let us build a project that might change current things, peoples’ perspectives or the environment. Until the next article, stay safe and be responsible for the environment. --- ### Top 10 mobile applications that Millennials love URL: https://appssemble.com/blog/top-10-mobile-applications-that-millennials-love Here is a list of the top 10 apps that all Millennials use, whether you want to admit it or not. Take a look to check if we are right. If you're embarking on an app development project, you're probably curious about 'what applications do Millennials use?' Maintaining interest and involvement from the Millennials is going to be vital to the long success of your app. While earlier generations such as the Baby Boomers and Generation X, as well as the young Gen Z populations, are still significant forces to be dealt with, Millennials are now the largest working-age generation.Who are Millennials exactly?You may have preconceived ideas about who Millennials are and what their way of life comprises, but let’s define Millennials for a bit, so there’s no confusion between all these comprehensive labels like Baby Boomers, Generation X or Gen Z. Wikipediasays that “Millennials, also known as Generation Y or Gen Y, are the demographiccohort following Generation X and preceding Generation Z. Researchers and popular media use the early 1980s as starting birth years and the mid-1990s to early 2000s as ending birth years, with the generation typically being defined as people born from 1981 to 1996. Most Millennials are the children of baby boomers and early Gen Xers; Millennials are often the parents of Generation Alpha".To break down Wikipedia’s definition into a more contemporary manner, Millennials are those born between 1981 and 1996, making them between 26-41 by now. You probably didn't expect a Millennial to be nearly 40 years old!So you're not pitching to teens as much as you are doing it to the vastest majority of working individuals out there, which means they are most likely the ones to have the capacity to buy, generate downloads, and create revenue, but also to college-graduated young people.Millennials are still the most engaging social-media generation on the planet since it is the first generation to use social media. They are the generation that grew up during a period of fast technological progress, particularly in the areas of the Internet and phones.It's easy to get swept up by social applications and try to separate tastes between services like Snapchat, Reddit, Twitter, Instagram, and Pinterest. However, in order to properly comprehend what Millennials value, it is necessary to examine their total app usage patterns. For that reason, we'll look at the top applications that Millennials use the most.What has the biggest influence on Millennial app decisions?Nearly half of Millennials said that a unique feature set and functionality is the key factor that propels them to download an app. The second most influential factor is a recommendation from a friend.What type of apps do Millenials use the most?Apps are used by everyone, however, diverse age groups have varied interests. So, which applications are popular among Millennials? The apps vary from cashless payment alternatives to gaming to dating apps, as expected. There are even some with a high proportion of Millennials.Millennials' favourite general appsAirbnbThis mobile app started off as a website. It began as a home-sharing alternative for those travelling in areas with limited traditional accommodations or those that are too expensive. The site emerged in 2008, making it ideal for the Millennial age, therefore Airbnb has its majority of users - 63% as Millennials. Earlier generations, such as boomers, may be less inclined to choose house-sharing versus a private hotel room. And, due to a lack of autonomous earnings and age limitations for rentals, Gen Z was and remains too young to effectively utilize the site's services.Because it delivers a helpful service, this app is popular among Millennials. Airbnb allows Millennials to have more authentic travel experiences by staying in local areas and communities rather than hotels. Millennials seek one-of-a-kind, local experiences. Airbnb has discovered a method to leverage this need. They created an easy-to-use smartphone app that lets tourists locate lodging in practically any city around the world by sleeping in people's extra bedrooms or houses.VenmoVenmo first appeared on the market in 2009 as a money transfer software, and it soon became the favoured payment mechanism among Millennials. Whereas before individuals had to divide a bill four ways in a restaurant, much to the disgust of the waiter, or one person would have to pay with the intention of getting reimbursed later which might never happen, yeah we all know the feeling, so now with the help of this app, they are able to partake in a range of paid activities with ease.Mobile online activity has exceeded desktop online activity, and smartphones quickly become consumers' favorite portals to the internet. Consumers are spending 70% of their media consumption and screen time on mobile devices, with the majority of that time spent in mobile applications.This payment software has swiftly gained popularity among Millennials as a convenient method to repay pals for a night out or to pay for products and services. Millennials account for more than 50% of Venmo users since they are the early adopters of the app. Venmo has become so popular that the brand name is now used as a verb, "Just Venmo me".Venmo combines the convenience of online payments with a social element that allows people to share their recent transactions with peers. Venmo would not be the first mobile payment software, but it has grown in popularity because of its easy User Interface, a fascinating social component that Millennials enjoy using, and the fact that it provides a crucial function in a climate where financial transactions are becoming obsolete.TinderTinder is a dating app founded by Match Group that launched in 2012. According to a report, Millennials are the most frequent Tinder users, accounting for over 55% of the app's users from 25-44 years old. Tinder is not the first or last online dating service, but its clean and user-friendly layout has maintained it at them ahead of the rankings. Swiping is associated with the app, as is the simple and inclusive filtering for factors such as location, sexual orientation, and age.As the Millennial demographic becomes the dominant working generation and continues to relocate into hectic urban regions, they are increasingly depending on apps like Tinder to help them create connections while maintaining their fast-paced lifestyles.Millennials' favourite Social Media appsFacebookMillennials witnessed Facebook develop with them. The initial site was launched in 2004, and it immediately grew in popularity. By 2007, the Facebook mobile app had been created, and it, like the website, has swiftly expanded and improved for its user base.According to Harvard - Institute of Politics, Facebook, remains the most used platform among Millennials. Facebook is used by over 80% of Millennials at least once a week. This figure is far greater than that of previous generations, for example, only roughly 36% of Gen Z use Facebook once a week. So, when it comes to the Millennial demographic, Facebook remains the social media leader. Its key strength is its diverse material, which can span from text-based to graphic and everything in between.YouTubeMillennials witnessed Facebook develop with them. The initial site was launched in 2004, and it immediately grew in popularity. By 2007, the Facebook mobile app had been created, and it, like the website, has swiftly expanded and improved for its user base.According to Hootsuite, YouTube is the world's second most popular social media site after Facebook. In the United States, Millennials account for over 70% of YouTube users. Because it is totally video-based, YouTube is a notable social networking app.Many Millennials no longer contribute to a printed newspaper, but with YouTube, they can stay fully up to date on what's happening in the world or watch whatever content they want via longer or shorter videos that they can view from the comfort of their own homes. In an age when few people are watching broadcast tv anymore, YouTube is an important method for Millennials to learn about anything good that they may want to try, learn or improve.InstagramWhile Facebook has a firm hold on Millennials, social media stats reveal that Instagram is another one of the most popular platforms among Millennials, who now account for almost 50% of Instagram users.Instagram's close relationship to Facebook makes sense given that Facebook currently controls the platform and can therefore upgrade Instagram in ways that suit Facebook's lengthy base. Instagram also has its own distinct features that make it an enticing social tool to use, like stories, reels, fun filters, and the ubiquitous usage and impact of hashtags are just a few examples. Many Millennials use Instagram to remain in touch with friends in the same manner that people use Facebook to stay in touch with relatives.Pinterest and Twitter80% of Twitter users are affluent Millennials, and over 40% of Pinterest users are also Millennials.People enjoy these applications for the same reason they enjoy Instagram: all of the aesthetics with none of the 'boring' material. It's also rather short-lived, appealing to their desire for rapid fulfilment. Every day, two Million people pin things on Pinterest. Twitter is excellent for disseminating your company's message throughout the world.TikTokTikTok is no longer the new kid on the block. Even the most reticent Millennial has now installed the app on their phone. At one point not long ago, TikTok was the most downloaded app in the United States and the fastest growing social media application of all time.In fact, in less than four years, TikTok gathered over 3 billion downloads and reached one-third of all social media users in the world of which 39% are Millennials.Millennials’ favourite Fitness appsNike Run ClubThere are other popular fitness applications, but Nike Run Club has captured the attention of Millennials. Nike, the prominent athletic company, produced the app, which discovered a unique approach to integrate training and social engagement. Runners may use Nike Run Club to create objectives, participate in guided runs, and track run metrics including distance, duration, elevation, and speed.In addition, the app encourages runners to participate in group competitions to assist them to accomplish their goals. The competitions have specified lengths to run within a month, such as 30, 60, or 90 miles, and users of the app can be asked to join a group challenge by its host. This app taps into Millennials' feeling of solidarity as well as their unexpected level of brand loyalty.MyFitnessPalThis app has been there while Millennials were still using messaging applications on their iPod touches, but it's still trendy. It has over 1.3 Million downloads on the App Store and is still growing. Users may use the app to measure calories and macronutrients, register exercise, and establish goals. Users may assess their progress on a frequent basis and adapt accordingly with continuous tracking. Recipes and meal plans are also accessible for viewing and usage. A community feature displays success stories from various users in order to motivate others. When it comes to health and wealth, the app is all-encompassing, Millennials can store all they need on the matter of their general health at their fingertips in one spot.These are just the top 10 of the apps Millennials love, but there are plenty of others that we didn’t mention. If you have the possibility to create something unique, do it! And if you struggle with the process, contact us and we can help you. --- ### What are mobile applications analytics and why do you need them? URL: https://appssemble.com/blog/what-are-mobile-applications-analytics-and-why-do-you-need-them Get an insight look on what Analytics in Mobile Apps is, why is it important and how to use it to improve your business One part of designing your product is determining how you will provide value to your users. Yet, as wonderful as that purpose may seem, it is of no benefit to you as the product owner in and of itself. You’ll need to figure out a strategy to ensure that you’re doing what you set out to do at the beginning of your product journey. This is where the complicated realm of product analytics enters the picture.Even though there are many features in your product, this is how you’ll know how to measure them: track all your events and engagements by putting them in a system that will allow you to make sense of things. This is because not all user activities have the same impact, not even for the user, and not for the company you manage.A developer's best pal is mobile app analytics. They assist you in gaining an insight into how your users' actions and app may be improved in order to achieve your objectives. Without mobile app analytics, you would be experimenting recklessly with no data to support your discoveries. That is why it is critical for developers to learn their mobile app analytics in order to monitor their performance while working towards their goals.Why choose Mobile App Analytics?For a number of reasons, mobile app analytics are critical to your development process. They provide information on how users engage with your app, the sections of the app they engage with, and what activities they do inside the app. You may then use these observations to develop an action plan to further enhance your product, such as introducing new features that users appear to require, upgrading current ones in a way that makes users' lives simpler, or deleting features that users appear to ignore.You'll additionally obtain insights into your mobile app's objectives, income, exposure, or if other KPIs are being met, and then use the data to change your approach and improve your app to meet those goals even more effectively.What are the objectives of my Mobile App Analytics?To understand how to leverage your mobile app analytics to achieve your objective, you must first understand what your objective is. There is no universal solution because each app has its own set of aims and objectives.Mobile games, for instance, generally focus on increasing income, so their goal would be to build their user base while also pushing for in-app purchases. Similarly, retail apps may seek to enhance shop traffic and improve brand recognition, and other apps such as video and music streaming apps may seek to get people to subscribe to monthly or yearly packages. So it all relies on what you really want to achieve with your mobile app and also why you designed it in the first place.How do you monitor Mobile App Analytics?There are several choices available to monitor your mobile app statistics, including:iOS App AnalyticsFlurry AnalyticsApp AnnieLocalyticsMixpanelFirebaseHow to use Mobile App AnalyticsThe features and functions of mobile analytics applications differ greatly. Some free apps have technological constraints and have difficulty monitoring consumers when they switch between mobile websites and apps. A top-tier mobile analytics platform should be able to do the following:Integrate easily: With a codeless mobile feature for instanceOffer a unified view of the customer: Track data across operating systems, devices, and platformsMeasure user engagement: For both standard and custom-defined eventsSegment users: Create cohorts based on location, device, demographics, behaviours, and moreOffer dashboards: View data and surface insights with customizable reportingA/B test: Test features and messaging for performanceSend notifications: Alert administrators and engage users with behaviour-based messaging such as push notifications and in-app messagesOut-of-the-box metrics: Insights with minimal client-side codingReal-time analytics: Proactively identify user issuesReliable infrastructure: Guaranteed uptime for consistent access to the platformThe installation of mobile analytics entails installing SDKs to the mobile applications that need to be tracked. Most mobile analytics tools will be configured to track website visitors automatically. Platforms with codeless mobile features will be able to track certain fundamental app aspects such as errors, failures, and clicks instantly, but you'll want to augment that by manually labeling new activities for tracking. With mobile analytics, you'll have better insights about your mobile site and app users, which you can utilize to develop competitive, world-class goods and experiences.Why is Mobile App Analytics important?Mobile online activity has exceeded desktop online activity, and smartphones quickly become consumers' favorite portals to the internet. Consumers are spending 70% of their media consumption and screen time on mobile devices, with the majority of that time spent in mobile applications.This is a great chance for businesses to engage with their customers, but it is also a very competitive industry. There are over 6.5 million applications by now in major mobile app stores, millions of online apps, and over a billion websites. Companies employ mobile analytics tools to gain a competitive advantage in creating unique mobile experiences.Mobile analytics tools can provide companies with a much-needed competitive advantage in marketing. Mobile advertising accounted for about 70% of all digital marketing ($135 billion) and in 2019, imagine how it’s expanding in 2022. As more businesses compete for customers on mobile, teams must have a thorough understanding of how their advertising functions and if app users who engage with ads end up buying.How does Mobile App Analytics work?Mobile analytics tracks individual users in order to capture demographics and habits. Tracking technology differs between platforms that employ JavaScript or cookies and applications that need a software development kit (SDK). When a visitor makes an action, the application sends data to the mobile analytics platform. Typically, mobile analytics track:PageviewsVisitsVisitorsSource dataStrings of actionsLocationDevice informationLogin / logoutCustom event dataCompanies use this data to determine what their users want so they can provide a more enjoyable user experience. They can, for example, see:What allures users to the mobile app?How long do most users stay?What sections do users interact with and where they run into issues?What factors are associated with results such as purchases?What elements contribute to increased consumption and long-term retention?Product and marketing teams may develop positive feedback loops with mobile metrics. They may A/B test the effects of changes on their users as they refresh their app, launch promotions, and introduce new features. Teams may implement more changes based on how consumers respond, generating even more statistics and leading to more trials. This results in a continuous loop that polishes the product.How various teams use Mobile App AnalyticsCompanies use this data to determine what their users want so they can provide a more enjoyable user experience. They can, for example, see:Marketing: Tracks campaign ROI, segments users, automate marketingUX/UI: Tracks behaviours, tests features, measures user experienceProduct: Tracks usage, A/B test features, debug, sets alertsTechnical teams: Track performance metrics such as app crashesHow can I monitor Mobile App usage?Teams who use a mobile analytics platform may log into the interface to examine mobile app use, however, utilization implies various things to different businesses. Usage for a gaming app might be the amount of time people spend using it. Usage for an investment app might be the number of trades. Once teams specify the use, they may construct reports to track it.1. FiltersThe first step is to group the information based on what you want to see, most mobile app analytics platforms also allow you to download a CSV version of your sorted information:Platform: he version of your iOS or Android app.Date: Displaying data from today, yesterday, this week, the previous 7 days, the last 30 days, or even specifying a customized timeframe.Demographic Name: Identified consumers with comparable characteristics. (For example, new users, purchases, and so on.)User Property: Sorting consumers based on age, app version, device type, gender, ad frequency, and so on.2. Active UsersView daily, weekly, and monthly active users mapped through time, along with real-time statistics on the number of users who've been active in the previous 30 minutes, as well as the top conversion activities throughout that time, such as a user launching the app for the first time, finishing a lesson, and so on.3. ConversionsConversions are your most critical activities. Data on your top conversion occurrences may be examined over time.4. EngagementDaily user engagement displays the average daily interaction including a chart indicating trends over the given time period.5. RevenueDisplays the total revenue, which is the sum of all sources of revenue. It also displays the income sources, and also the average revenue per user (ARPU) and average revenue per paid user (ARPPU) for every time frame you want.6. Adoption and AcquisitionYou can see your app version acceptance charts, which indicate the proportion of active users for every app version, as well as your top acquisition methods, the number of times the app was launched for the very first time from every channel, and the lifetime value (LTV) of the people who launched it.7. Retention and AudienceRetention streaks are a group of users who began utilizing your app at the very same time (such as on the same day or during the same week). You may also look for more data about your target audience, which will give you a good understanding of your consumers' traits in terms of:Location: The proportion of encounters that originate in each of your top countries.Devices: The proportion of users who own each of the top device models, as well as the percentage of users who own each of the OS versions.Demographics: Genders user percentages by age range.Tools stack for Mobile App AnalyticsMobile app analytics tools provide a ton of data on your app and its usage. Here's a brief rundown of several characteristics that are shared by the majority of them.CRM or sales platformData management platform (DMP)Customer support platformContent management system (CMS)Marketing automation platformAdvertising platformsProduct or appTesting toolPayment systemWe’re here to support you at every step of the way!At appssemble, we understand how to develop ideas and make them durable via research, planning, and continuous improvement. Since we have plenty of experience building mobile apps, we can assist brands in developing applications and businesses in connecting with their users in order to build amazing digital environments. As always, get in touch if you want to learn more or talk to one of us about your mobile startup. --- ### 2022 - Design trends for mobile applications URL: https://appssemble.com/blog/2022-design-trends-for-mobile-applications Discover in only one article, what are the top 13 detailed graphic design trends of 2022 Mobile UI design trends change all the time, and as we stated before, this is why it's critical to stay on top of the latest app design trends. The world is changing, new technologies are emerging, and new design approaches are emerging, therefore keeping up with design trends is not an option for a firm looking to expand.Read our previous overview of 2021 mobile trends, and check what were the design trends of 2021 so you can easily compare how the design industry is developing from year to year since following the new design trends is essential for firms that wish to stay relevant.In this article, we've compiled a list of mobile UI trends 2022 to keep you up to date. Each of the businesses and niches has certain unique characteristics that impose some constraints on the design trends that may be used. Nonetheless, with a variety of tactics to choose from, you may find ones that are ideal for your application and perhaps even help us understand your perspective when it comes to your future project.Motion and animation designIf utilized sparingly, motion in UX may be beneficial and communicative. Motion is most typically used to provide subtle feedback for micro-interactions, rather than to please or entertain consumers.The main advantage of UI motion is that it draws the attention of the user. Motion detection is the responsibility of our human peripheral vision. The ability to detect movement outside the centre of our range of vision is, of course, advantageous in evolutionary terms: we can identify danger and protect ourselves.However, this implies that we are sensitive and easily distracted by any form of motion. That is why motion in user interfaces may quickly become irritating: it is difficult to ignore, and if unnecessary to the work at hand, it can significantly harm the user experience. Here are some of Motion Design applications:Transition Patterns: Users begin to lose concentration if the transition between displays takes too long. Motion design is used to assist users in understanding how the software flows between displays, making navigating easier and more appealing.Another occasion when motion design might be used in transitions is during loading periods. Why not use an intriguing animation to cut down on the waiting time? Animations keep consumers' attention while the gadget downloads the essential data.Transitions based on a containerTransitions with no containerFlawless transitionsMicro-interactions: Micro-interactions are occurrences that are employed to create a memorable experience for the user. These micro-interactions may be found across applications and websites. The majority of the time, the animation begins with a trigger (user action) that creates a reaction, informing the user of what's going on and making navigating inside an app or a website easier. These micro-interactions might occur without the use of animation, but motion design is used to make this interaction more fascinating and engaging.Graphic Cues: Motion design directs the user of an application by utilizing animations to signal where to concentrate, what to do next, or what seems essential on a screen. Consider employing motion to recognize user input and assist users in navigating content without getting lost. Navigation interactions appear more organic and less artificial when they are in motion. Motion breathes new vitality into the UI while preserving context.Responsive, Fluid Motion: Users expect and have come to expect fluid and responsive UI. When people are unsure about the functionality of something, they tend to linger over it. A smart UI rewards this behaviour by offering quick feedback—perhaps in the form of animation. To ensure that consumers enjoy a continuous browsing experience, respond to any queries they may have right away. User-interface designs come up on touch-enabled devices by permitting users to build strong connections in engaging ways.Playful branding and eliciting emotions: We may use animation to define the tone of a brand's identity, whether it's entertaining, playful, professional, or something else. The function of animation is to improve one's individuality.Designers can elicit emotions through animation. When we think of someone, we instinctively link them with the way they talk, walk, laugh, and so on. The personality of a person is what makes him or her unforgettable. Brands follow the same principle.Using motion design to show the personality of a user interface gets a stronger emotional reaction from users than static images. Motion design emphasizes the personality of the user interface rather than its visual identity, and so has a tremendous effect on the actions and feelings of users. In the same way that people's body language and movement reflect their personalities, so does motion in a user interface. Motion ensures that digital interactions and your brand are memorable to customers, and also make sure to also check how digital transformation can improve your product.Just-for-fun animations: Animations can, of course, be just ornamental - as long as they do not negatively impact user experience. Decorative animations aren't necessary, but they improve the overall appearance.Try adding a colourful animation to the basic 404 page the next time you want to play with motion design. Why not make it less unpleasant to look at as it isn't the most pleasant page to look at? We may generate a good experience for the user on a website that is intrinsically negative by employing a hilarious animation or minor interactions.Informing consumers about a change of state: Motion can be used to signify that the interface has changed state, such as a mode shift. Modes might be difficult to express to users, but animation can help in two ways:by making the mode shift visible;by giving a conceptual metaphor for the mode transition. For example, morphing a pencil icon into a disk after it has been clicked on marks the move from Edit to Save mode rather than simply changing one icon out for the other.Motion for spatial metaphors and navigation: It is sometimes difficult to describe the structure of a complex information space to consumers without exhausting their cognitive resources or taking up too much screen space. Scanning through navigation menus, tree diagrams, or even breadcrumbs to determine one's position in the information hierarchy is a difficult sort of cognitive effort.Zooming out reveals less detail but more items, implying that the user is moving up the hierarchy, whereas zooming in shows more information but fewer things, implying that the user is moving down the hierarchy.Grabbing and hijacking attention: Because the human visual system is extremely sensitive to motion, it may be exploited to capture users' attention, for good or bad. On the one hand, it might highlight a subtle marker, while on the other hand, unnecessary motion animations distract and frustrate the user. At this point, you could also consider all the possibilities in the realm of AI/ML on mobile applications from a design point of view, and if you feel overwhelmed then you should not miss this chance and just outsource.Furthermore, employing motion to divert users' attention or instil fear of loss is a dark behaviour: an unethical use of user-experience concepts and cognitive psychology to persuade users to do something they would not normally do.The best motion design tools:PrincipleLottieSQUID UI Flow Template for SketchThe IconicAfter EffectsFlat designFlat design is a type of user interface design that employs minimal, two-dimensional objects and bright colours. It is sometimes contrasted with the skeuomorphic approach, which creates the appearance of three-dimensionality by mimicking real-life features.Flat design was created for responsive design, in which the content of a website adapts fluidly based on the device's screen size. Flat design guarantees that responsive designs operate effectively and load quickly by using simple forms and minimal materials.The flat design delivers a simplified and more optimum user experience by minimizing visual noise (in the form of textures and shadows).Flat Designs’ Typography and Logos:Simple shapes, with no shadows, textures, or gradients.The colours are flat, that is to say, they are solid and consistent. They stand out from the rest of the app by employing colour palettes to separate the elements and guide the use, making it easier for the brain to find its way around.The readability of fonts is taken into consideration.Flat Design Colour Rules:Colours: may be used freely in flat design, but they must be chosen in a consistent palette. To guarantee that you choose the best colour palette for your company, avoid combining bright and pastel hues. Furthermore, the latter colours are frequently favoured in flat design. Colours should enliven the navigation while avoiding visual saturation.Illustrations & images: If you choose a website with a flat design, the image placement should be carefully considered so that it does not overburden the overall design of the interface. You may also experiment with other geometric forms such as circles, squares, triangles, and so on.Icons: A flat design website would be incomplete without them. We advise you to avoid using forms in favour of "flat" icons. Many icon kits, such as Designmodo and Thenounproject, may be used to satisfy most demands. Some are made in Syg format, and the colours and forms may be changed in Illustrator.Typography: The typeface should aid in the structure and organization of the material. Fonts are simplified and legible in flat design.Inclusive & accessible designUser experience designers are in charge of assuring the usability and accessibility of a product. Unfortunately, accessibility is frequently ignored. Content and features should be accessible, simple to comprehend, and efficient to use for a wide variety of abilities. Everyone benefits from accessible designs. Accessibility is frequently promoted as being helpful for the 15% of the world's population who have permanent impairments. People without chronic impairments benefit from accessibility in several scenarios.As we age, our abilities in vision, hearing, movement, and cognition tend to deteriorate. Misplaced glasses, musculoskeletal problems, bad illumination while reading a screen, and noisy settings while attempting to hear audio are all instances of temporary or situational limitations, therefore here are several inclusive and accessible designs to help all of us:Low vision: Low vision refers to visual problems other than total blindness, such as those caused by age, diabetes, contrast sensitivity, and colour blindness. We can improve low vision experiences by designing with the figure-ground concept in mind.Principle of Figure-Ground: One of Gestalt's Principles is that when we observe anything visually, our minds strive to separate the foreground from the background. It creates visual tension when neither the foreground nor the backdrop shines out significantly. When someone has impaired eyesight, this might be considerably more difficult.Von Restorff Effect: When numerous comparable things are given, the one that differs from the others in size, colour, form, or other features is more likely to be recalled. It is critical to use this idea correctly to improve the experiences of persons with visual impairments.Physical Disabilities: Physical impairments include reduced mobility, involuntary movements, and painful movements caused by conditions such as arthritis, amputations, repetitive stress injuries, tremors, and physical traumas. We can enhance experiences for people with physical limitations by designing with Fitt's law in mind.Fitt’s Law: The time it takes to reach a target is determined by its size and distance. As a result, when buttons and links are smaller in size or farther away from the starting point, it takes longer to reach them. When someone has a physical limitation, this might be more difficult and time-consuming.Cognitive Disabilities: Neurodiversity, intellectual impairments, autism, Alzheimer's disease, and ADHD are all examples of cognitive and learning disorders (attention deficit hyperactivity disorder). We can enhance experiences for people with cognitive disorders by designing with Miller's and Fitt's laws in mind.Miller’s Law (Magic Number 7+/- 2): Our short-term memory has a capacity of 7 sticks of information, plus or minus 2. This is why phone numbers and credit card numbers aren't just one long string of digits, but rather "chunked" for easier recall. Here's an example of a number that has been broken into pieces rather than gathered together.Hick’s Law: People will take longer to decide if they have more options. This also applies to the amount of information that humans must digest to discover information and execute activities. Hick's law and Miller's law may appear to be similar, however, Miller's rule is about "chunking" material for short-term memory, whereas Hick's law is about limiting possibilities for faster decision making and shorter job completion times.Brutalist designAnother trend that is on the rise is brutalist design. Brutalism appears to be a counter-trend to all of the designs that are filled with gradients, shadows, and happy 3D figures.Flat style, powerful edges, contrasting colours, unbothered, raw, ugly, reactionary, bold, uncomfortable are some of the words one can use to describe a brutalist design. However, one of Brutalism's key distinguishing features is missing in this new form. It now employs all of the aforementioned characteristics, but adheres to a more traditional arrangement, as seen in other design styles.This app design style is called from the architectural style that translates as “raw concrete”. These designs may elicit many of the same sentiments as a brutalist structure might. Similarly to how brutalist buildings stand out from the rest of the buildings in major cities, brutalist applications stand out from the rest of the modern ones.If you're wondering what characteristics constitute a brutalist app design and how to recognize one in the wild, Matt Stewart of Creative Momentum has compiled a detailed list of characteristics which I'm going to borrow:Black or white backgroundsNo gradients or shadowsOverlapping elementsLack of symmetryCrowded designNo distinct hierarchyMonospaced typographyOne font used throughoutContrasting colour paletteLack of animationSparse imagerySimple or non-existent navigationSingle-page website designTypes of brutalist design:Purists: If you're familiar with brutalist design, this one should come as no surprise. The purist brutalist design emphasizes employing as few components as possible, similar to how concrete and steel are utilized as major construction materials in brutalist structures.UX minimalist: The colour palette remains relatively simple, consisting largely of black and white, and the links aren't blue, a departure from the pure design. The rationale for these variations is that the goal of this style is to focus on efficiency rather than strictly adhering to the core HTML components.‘Anti-ists’ or Artists: a flawless marriage of brutalist minimalism and artistic self-expression In terms of programming, the artistic design differs from purist design in that it does not want to keep to fundamental HTML components. It frequently includes experimental JavaScript that is used to create a specific vibe or emotion. When designing insane epilepsy-inducing designs, it is critical to understand who your audience is.Unique illustrationsAn illustration is more than just an ornament: it is a medium of communication, compensation, a method of giving or improving knowledge, a means of strengthening connections, and a means of guiding people through circumstances. An illustration is more than just an aesthetic feature; it may take several forms and function as a visual aid to the user interface.Illustrations have an important part when it comes to expressing ideas, whether in a presentation, interface, video, or simply illustrating a text. When utilized correctly, they can alleviate cognitive load, inform, and link ideas and feelings. Furthermore, graphics have a tremendous impact on the emotional appeal of the interface. They are also memorable and catchy, which helps to increase brand recognition, storytelling, and brand recognition.Why use unique illustrations?It boosts brand identityIt’s a universal method of communication It’s a valuable tool in your toolboxIt promotes clarity and understandingIt helps people feel goodLimitless imageryApp imagery, such as product shots, is intended to be viewed in a small size. Apps allow users to interact with graphics in a variety of ways to fit smaller screens on smartphones and tablets, including animations, panning and zooming. Products in eCommerce and retail applications no longer have to be contained within a square or rectangle. Instead, they look limitless and meld with the backdrop, as if they're floating amid the app's other design components. This provides the user with a much more unified app experience and unifies the app design.This type of artwork is frequently exhibited in parts or cropped to reveal greater detail. If you want to take it a step further, you could pair this look with varying levels of interaction. For example, you might employ augmented reality in an eCommerce app selling furniture or houseware to allow consumers to visualize how the goods would appear in their homes.Menus and galleries that are asymmetricAsymmetry in design and layout draws attention to specific aspects inside an app. People's eyes often go in a specific direction while processing visual input, therefore developing an asymmetrical design can run with the audience's visual motion. Designers are flexing their innovative powers in 2022 to escape the polished feel of symmetrical applications, particularly for apps with multiproduct galleries, such as eCommerce apps.The asymmetrical design may assist to establish your brand's distinctive character while also bringing a fresh and interesting perspective to your menu or gallery. It catches your audience's attention by disrupting patterns and offering something distinctive in design from the ordinary.Spherical patterns that are abstractCircular and spherical designs are widespread. These forms may be found in both organic and manufactured things, Circular shapes are appealing because of their fluidity, and when employed in digital design, they are recognized to provide a welcoming, soothing experience.App designs in 2022 will take this tendency for rounder curves a step further. Many people are using circles in their graphics and backdrops. By combining circles with zigzags and bright hues, they lean towards the abstract, whimsical, and nostalgic motifs of the 1980s style.Play with abstract circular patterns to give depth to backdrops and brand individuality to your app. Another alternative is to animate your circular designs to represent state changes in the customer journey or advancement throughout a task flow.Unconventional text alignmentAnother app design concept that will be thriving in 2022 is experimenting with copy layout. Designers are producing unconventional designs with vertically and diagonally positioned text for those targeting left-to-right readers.Creators are employing copy to mix into other aspects of the app, challenging how consumers usually view text in-app designs. Experimentation with space, case, and font is common when dealing with atypical text alignment.Borders define characteristicsBorders aid in the management of data in app design. Borders work as dividers to construct a hierarchy to direct the viewer by placing a simple stroke around each piece. They leave enough room for each headline, graphic, or button to breathe.Borders is also a bit out of date. Earlier GUIs in technology, employed borders to visually separate items such as scroll arrows, icons, and windows. Many applications connect with consumers through nostalgic overtones by quietly evoking this time of early digital design.Multi-directional navigationIn terms of usability, the top applications and websites make using them feel natural. The use of multi-directional navigation is an easy technique to simplify complicated flows and interactions.Instead of merely scrolling up and down among functions, these designs urge users to interact with the app more deliberately. Incorporating horizontal sliders alongside vertical scrolling displays results in a more fascinating and memorable user journey.It's a particularly common tendency for apps that have many goods or profiles. Those who include podcasts, music, or social networking should leverage this as a jumping-off point to expand content and allow users to completely immerse themselves in designs.Layered sheer screensThe use of drop shadows or blur effects on buttons and text boxes partially obscure the backdrop picture when stacking sheer screens over other design components. This method establishes page structure while creating a pleasant, warm vibe.Using a glow or drop shadow to distinguish an element from the backdrop helps to direct the user's attention. The Fabulous, as shown in the image below left, is a health and wellness software that makes extensive use of overlays. To prevent the superimposed text boxes from merging into the backdrop picture, each has a drop shadow.This technique is also utilized in other contexts, such as subtitling. Subtitles for films, tv series, and videos frequently utilize strokes, overlays, and blurring effects to make the text easier to understand. The layered sheer trend is not only attractive but also improves reading and utility.Super appsSuper Apps are mobile apps that combine many services into a single app. These applications are immensely popular in Asia and are rapidly spreading in Africa. Super applications will become more prevalent around the world by 2022.Designers are tackling this all-in-one app experience with a slew of bright hues and charming, detailed iconography. These app designs, which immerse users in gaming, retail, social networking, and banking, must show how much they can give. A clear framework, frequently in the form of a simple grid, with multi-directional navigation, is essential for managing multi-product galleries of this size, without being overwhelming which is hard for a startup, that is why you should definitely outsource for cost and time effectiveness, assistance and professionalism.Does your mobile app need a brilliant design? When you add them all up, the design trends of 2022 are a ragtag bunch. Motion and flat, brutalist and unique, asymmetric and abstract. It's difficult to picture any of these diverse characters meeting at a party, yet that's exactly what will happen this year. And it's precisely on these unexpected mashups that you won't want to miss out on this year, so create your amazing design, if it’s a bit too much for you then outsource it, and after it’s ready to share, here is a detailed guide on where to announce your work to the world.If you need a great graphic design for your mobile app, let our talented team create something unique and limitless. Until the next one, stay awesome! --- ### An Overview of 2021 from a Mobile perspective URL: https://appssemble.com/blog/an-overview-of-2021-from-a-mobile-perspective We have prepared for you an extensive guide about this year’s hottest trends when it comes to mobile app designs, new technologies, business models, and Apple App Store vs. Google Play Store end-of-the-year analysis of apps, games and revenues. With the Earth's orbit around the sun complete, and a vaccine authorized by the FDA, it's past time to forget about what occurred in 2021 and focus on what went well in the mobile technology industry. The uncertainty of 2020 drove people to stay indoors for most of the year, resulting in widespread adoption of some technologies, particularly mobile technology, and that continues to grow in 2021 as well when restrictions started to ease.You must always maintain your finger on the pulse to be successful in any industry. In addition to researching your competition, keep up with industry advancements. It's no secret that our world is becoming increasingly mobile. As a result, every company regardless of industry must keep up with emerging mobile trends. This is especially true for businesses that have a mobile presence, such as a smartphone app or a mobile website.This year, we've used mobile applications more than ever before. Our mobile devices become our digital clinics, pharmacies, restaurants, grocery stores, preferred shopping centers, and more, from grocery shopping to clothing shopping, from ordering medicine or video-conferencing with the doctor to ordering meals. Mobile technology will continue to infiltrate even the most little areas of our lives.It's critical to stay educated in the mobile environment, whether you're a mobile app developer or a small pizza business owner. This statement also applies to those of you who do not have access to a mobile app. That's because, if you haven't already, you should be considering mobile application development. However, with so many sources of information available, it may be difficult to tell which trends are real and which are merely fad or fake news. As a result, we have prepared for you a guide with all the important trends that happened in 2021 when it comes to mobile technology.App Store vs. Google PlayThrough iOS and Android, Apple and Google control more than 95% of the app store market share. Both mobile OSes launched with a few pre-installed apps at first, but third-party developers rapidly added more to improve the experience.Within a year of the platforms' introduction, tens of thousands of developers had created apps and games for them. Both Apple and Google had over one million applications and games accessible in less than five years, generating millions of in-app revenue for both businesses.These two platforms, which have enlarged their services to include apps for consumers and businesses of all sizes, are at the heart of the app economy. According to App Annie, its value is projected to surpass $6.3 trillion.For the past three years, both Apple and Google have increased the restrictions on entry for developers. They've also removed millions of applications from their separate stores to enhance the ecosystem's overall quality.Fun factsThere are 2.39 million applications and 442,000 games in Google Play's App Store.Games account for 15.6% of the Google Play Store.Education and business applications are the second and third most popular categories in the Google Play Store.Free apps account for 96.2% of the total.Number of apps on Apple App Store vs. Google Play StoreThe number of mobile apps has been increasing steadily year after year, while in 2011 there were 0.28 million apps in the App Store, in 2021 it grew up to 3.6 million, with a growth rate of 5.8% from year to year, and on Google Play it started from 0.06 million and grew up to 2.3. Its highest peak was in 2018 with 2.6 million apps and continued varying every year, with a growth rate of -8% from 2020 to 2021.Number of games in Apple App Store vs. Google Play StoreThe number of games on both the App Store and Google Play is lower than the number of apps, as expected. On App Store, it started from a number of 89.000 games in 2011 that grew up to 984.000 in 2021 with 5.4%, and on Google Play it grew from 53.000 games in 2011 to 442.000 in 2021 with 21%.Most popular categories in Apple App Store vs. Google Play StoreThe most popular apps on App Store and Google Play varies significantly from one store to the other. The number 1 most popular category remains the Games section in both stores while the following categories are mostly different from one another. The second most popular category on App Store is Business, and for Google Play is Education, while the third is exactly the opposite.Paid vs. Free apps on Apple App Store vs. Google Play StoreFree apps have a broad appeal and attract hundreds upon thousands of users, whom corporations can then efficiently monetize through in-app adverts or transactions. That’s the reason why there’s such a huge difference between paid and free apps. While the paid ones are in a percentage of 6.31 on App Store and 3.72 on Google, the number of free apps is considerably higher, with 93.69% on App Store and 96.28% on Google Play.Most popular app on App Store vs. Google PlayThe most popular apps on App Store seems to not change at all year after year, with the same well-known apps like TikTok, YouTube, Instagram, Snapchat and Facebook, while on Google Play there are other popular apps this year, such as Crypto.com, Cash App and Google Pay.Most popular games on App Store vs. Google PlayWhile the most popular games on App Store are the well known Among Us!, Roblox, Call of Duty, Subway Surfers and others, on Google Play the popular ones are Survival 456, Bowmaster, Merge Animals, Text or Die and othersRevenueGross app sales in the Google Play store reached USD 12.1 billion in the third quarter of 2021, up 17.4% from the same period the previous year. In the most recent quarter, the Apple App Store produced 21.5 billion dollars in customer spending on in-app purchases, subscriptions, and premium apps.DesignIn terms of hardware, the smartphone market evolves every 2 to 3 years, because trends change regularly. If your app doesn't appear modern, then it probably isn't modern. That's why it's critical to stay on top of the latest app design trends.However, the finest solutions remain: the trends can and will be utilised in the future with a few tweaks. The most effective solutions are those that benefit both your company and your users. All of 2021 was particularly effective in eliminating unpopular and deficient ideas. So here are a few trends that were popular in 2021:1. Clarity and minimalismGiven the limited size of mobile devices, clear, clean, and simply accessible designs are constantly important. Users have increasingly shown a preference for clean, minimalist designs in recent years. A clean design makes it easier to understand the content and helps the app perform better:Neumorphism (lush dimensional makeover for flat icons and buttons)Neutral interfaces and content-focused experiencesDynamic Visual ExperienceRounded, organic shapesTransparent elementsFuturistic colourSerif fonts2. Dark contrasting designOne of the best UI techniques has proven to be dark mode. There are a large number of people that like it, and they aren't going anywhere. Eye strain is reduced by the use of a dark contrasting pattern. Highlights stand out against a dark backdrop, allowing every detail to be seen. The dark contrasting pattern is attractive and tasteful. It's established itself as a timeless masterpiece.3. Functional 3D graphicsThe popularity of 3D graphics continues to grow, especially in e-commerce. However, 3D is evolving. The wow element is decreasing in importance. Today's solutions, on the other hand, are progressively emphasizing 3D interactivity. It's no longer just about displaying a product from every angle, it's also about assisting the user in customizing the settings for interacting with a 3D picture. There appears to be no question that 3D graphics will continue to improve in utility.4. CustomizationThe user will feel as though the material was developed specifically for them thanks to the customized design. With design becoming ever more person-centred, this tendency will only get stronger. If you’re interested in building user personas for mobile apps, here you have the perfect article.5. Data visualizationIt's still relevant to turn boring statistics and information into easily understandable graphs and diagrams. This tendency applies to all types of organizations and is likely to continue.6. Unique illustrationsThere are an infinite amount of designs available now. It's nearly hard to produce something that hasn't been done before. You must, however, stand out from the crowd and introduce some novel design concepts. You may do this with the aid of an extravagant digital illustration. 2021 wasn’t afraid to play around with the photographs and you should do too, if you don't like the results, you can always go back to the prior forms.7. Maximum interactionOne of the best UI techniques has proven to be dark mode. There are a large number of people that like it, and they aren't going anywhere. Eye strain is reduced by the use of a dark contrasting pattern. Highlights stand out against a dark backdrop, allowing every detail to be seen. The dark contrasting pattern is attractive and tasteful. It's established itself as a timeless masterpiece.Modern user interfaces are nearly always designed to create a personal, almost intimate relationship with the user. As a result, the existing tendencies will only get more advanced:Interactive videos -- Videos have grown popular and valuable in a variety of fields, and their use will only grow. It's a reasonable assumption that most applications will use interactive movies in the not-too-distant future.Emotional ​design -- Emotional design has always been in demand and will continue to be so. It personalizes any app, increases user engagement, captures users' emotions, and prevents them from leaving the app.Animation and gamification -- The combination of animation and gamification improves user engagement by making it simpler to interact with the app. It's no wonder that they're getting better and more frequentStorytelling -- Visual storytelling has emerged as the most effective approach to engage consumers and communicate information in recent years. This is a trend that we think will last.Emoji -- Emojis offer a splash of colour to the user experience. They have become essential to our communication, which is why they will continue to be vital as technology advances.UX copywriting -- The latest copywriting trends all lead to making the user interface interactions easier. Simple, short forms supported by visual clues are increasingly replacing walls of text and complicated words.In-app gestures -- We all utilize gestures when using an app. We put our fingers on the screen, swipe, tap, and rotate it. The motions are diverse, but we always anticipate it to take little time to locate the perfect one. We've gotten into the habit of double-tapping each Instagram post we 'like,' and it's become one of our go-to motions. We don't even notice some of the movements and perform them instinctively.8. Chatbots and conversational designThis is unquestionably one of the mobile UI trends for 2021, and it isn't going away anytime soon. Chatbots aid in the optimization of business processes involving customer interaction. They're also beneficial when it comes to handling several requests at once and dealing with typical problems.9. Voice interactionsThe visuals in mobile UX trends 2021 aren't the only thing to consider. They now support voice interactions as well, similar to Siri, Google Assistant, and Alexa. However, with VUIs, it's critical to stay to the concept and message of not overloading people with data.10. Liquid swipe and buttonless designOne other trend that developed rather well this year is the liquid swipe and buttonless design. Users don't need to see a visible button to figure out where they need to click or swipe to achieve their goal. So, what's the point of keeping these graphics in the UI?11. Advanced AnimationAdvanced animation was one of the most important mobile UI design trends to incorporate into your projects. Simple gestures that no longer entice your audience. I think you saw a change if you added new, more intricate transitions. Looking for some proof? Check these 10 innovative apps of 2021 for examples in design, compare them and let us know what you think about the trends of this year.New technologiesMobile app development in 2021 was an area of lightning-fast developments, technological advances, and new emerging trends that helped firms acquire clients. Although the COVID-19 outbreak has been a nightmare for many firms, the mobile development industry continues to grow. Here are 15 technologies that were successful in 2021:1. 5GModern app development can make use of 5G technology, which is the newest generation of telecommunication networks that has already demonstrated incredible connection speeds. During experiments, Opensignal claims that 5G download speeds were between 1.6 and 15.7 times quicker than 4G. Support for this new networking standard has become one of the essential 2021-2022 mobile app trends, thanks to the better security and greater number of possible connections per square kilometre that 5G provides. 5G also allows for the development of more advanced and realistic AR/VR apps, the streaming of high-definition 4K-8K and 360-degree media, and the introduction of more networked IoT devices to the market.2. Voice technologyIn the not-too-distant past, speech technology was just portrayed as a fun gimmick to attract clients; currently, it has risen to become one of the most popular app development trends for mobile and IoT platforms.Here are some cases of speech technology and why people like it:Many consumers who possess a smart speaker system prefer to use voice search. Voice search, in contrast to typing, delivers a rapid and hands-free experience that makes surfing more enjoyable for consumers while also improving shop marketing.A voice user interface, or VUI, is a novel technique to create the user interface. It combines speech recognition and predictive machine learning to allow users to communicate with the app using only their voices. It adds a new degree of personalisation to the game, which is critical for client conversion and retention.Voice shopping consultants do exactly what they say: they guide consumers around online marketplaces, suggesting things, answering inquiries, and informing them of current discounts and specials.One good example of a voice-enabled app is voicecal - calories counter. You can easily track your daily nutrient intake and adjust your diet by using only your voice, and it’s usable in 63 different languages. All you have to do is tell the app what you ate and voicecal will take care of the rest.Different forms of push notifications are used by current mobile advertisers to encourage consumers and promote engagement:To boost sales, eCommerce stores deploy tailored push notifications.To keep users up to date, social networking apps offer real-time information.Content is sent by media businesses to deliver time-sensitive information.3. App clips & instant appsWhen it comes to mobile apps, high conversion rates are critical and difficult to achieve. You just have seconds to attract a user's attention and persuade them to install your app and even less time to persuade them to remain. Instant applications (App Clips for iOS devices) are useful in this situation.Instant applications were a crucial element of the 2021 mobile app trends, allowing users to test out an app without having to download it. They just retain a little amount of data locally and do not require users to install anything to utilize them. The app may be opened by simply clicking on the link that the developer provides on their social network or website.4. Foldable devicesFoldable devices might be the future of mobile app development, as consumer demand grows despite higher-than-average pricing. The fundamental feature of folding screens is their capacity to transform: they may be used as a phone and then unfolded to become a medium-size tablet when needed.Some types may be folded in rather than out, making them more compact. Samsung, Huawei, Motorola, and LGglobal are among the companies that provide foldable displays, with their Galaxy Z Fold model.The trend offers app developers a creative and technological challenge in addition to an opportunity for smartphone makers. Developers should pay attention to this trend as the price tags for foldable devices become more affordable for the majority of customers and adjust their apps to accommodate various types of screens, including folding displays.5. Beacon technologyAnother booming hit in mobile development is beacon technology, which allows consumers to merge their online and offline experiences. Beacons, in their most basic form, are miniature transmitters that communicate with cellphones through Bluetooth.They are suitable for use in retail malls, airports, hospitals, and almost any other location. Beacons transmit signals to the company's app on a customer's phone when they enter such an area. The user may get real-time in-store navigation, customised promotions, discount notifications, and other information this way.Beacons are already available at Apple and Macy's shops, and the relevant functionality is included in the companies' apps. Beacon technology is also used by Aruba Networks and Google for indoor navigation and enhanced data collecting. As more areas become linked, mobile app developers should consider beacon technology while creating appropriate and useful apps.6. Mobile-first leisureLast years people used to spend about three hours every day on their phones. This amount has already surpassed 4 hours 6 minutes in 2021 devoted to mobile applications rather than web usage. Due to COVID-19 constraints, leisure was the first industry to go digital, and users aren't ready to give it up anytime soon. In essence, the most simple of the new app development trends are mobile-first leisure, because customers prefer mobile platforms, your company should make use of them.7. On-demand appsOn-demand apps have risen to the top of the list of contemporary top trends in mobile app development, thanks to the coronavirus pandemic. In essence, unlike games or planners, these applications remain inactive in users' phones until they need to access a certain function. In 2021, according to Eastern Peak the most popular and extensively used on-demand applications were:UberGrubhubRinseHandyInstacartSootheDoorDashWag8. Mobile walletsMobile payments are another app trend to keep an eye on in 2021. The fintech business is growing at a pace of 23.58%, and utilizing digital wallets has already become second nature to customers, especially in an era where online purchasing and little personal interaction are common.Fintech companies can provide mobile wallets with contactless payment capabilities and in-app purchases of tickets, loyalty cards, coupons, and other items. Market experts project that by 2025, each user of proximity payment technology would spend an average of $4064 via mobile contactless payments.While PayPal, Venmo, Google Wallet, and Cash App are the most well-known applications and services in this industry, there are other emerging businesses on the market that provide extra capabilities.Want to develop an app? Contact us right now if you're thinking about developing an Uber competitor or adopting an on-demand business model into your industry.9. M-commerceSince the start of the COVID-19 epidemic, mobile app development has shifted its attention to various new industries, with m-commerce leading the way with a 25.5% CAGR (compound annual growth rate). Online buying isn't a new concept.However, the virus's omnipresence and long-term lockdowns have driven people to try shopping online for the first time, and many of them will continue to use m-commerce applications to shop even after the pandemic has passed.Mobile commerce is one of the most stable and promising app trends, as seen by the enormous success of Shopify, Instacart, and countless more applications for anything from grocery delivery to all types of retail.10. WearablesThe market for wearable devices continued to increase, which implies that the demand for mobile apps that work with these devices will rise as well. Wearable technology has a lot of potentials, particularly in the sports and healthcare areas. People are drawn to smart wearable gadgets such as watches, bracelets, and even jewellery because they can measure and analyze vital signals in real-time.Machine Learning will play a role here as well, from generating predictions and suggestions based on health indicators to even identifying diseases in their early stages.11. Virtual events streamingTaking an online Zumba class was a novelty before the epidemic, but now that live streaming is at the forefront of the current developments in mobile app development, it's a new type of normality.Platforms like ConnexMe, Hopin, Glisser, Eventee, vFairs, SpotMe, and others have seen significant growth in the recent year. Zoom and Jitsi, for example, have grown in popularity, and this trend is expected to continue into 2022. Check out How to build a Live Streaming app - Product, Monetization, Tech, Features & Costs.12. Internet of things (IoT)Although mobile applications are only one component of any IoT infrastructure, they are critical in linking people to their smart gadgets, automobiles, and complete homes.The Internet of Things is essentially a network of items that can communicate with one another and with the Internet. Smartwatches, self-driving Tesla, and Control4smart home systems are among them.IoT is a disruptive path in terms of app trends, and it has already begun to dictate new norms for developers. Since more people are becoming aware of the benefits of IoT, mobile developers must create applications that work well on a variety of devices.Furthermore, IoT allows developers to construct entirely new types of apps, allowing them to be more creative and experimental.13. AI & Machine LearningMachine learning allows for autonomous and deep analysis, which has a huge range of applications in the mobile app development sector. Here is a list of popular use cases for machine learning in mobile platforms, which is not exhaustive:Personalization -- Gain a deeper understanding of your consumers so you can provide better services, more relevant recommendations, and improved experiences, resulting in more retention and sales.Analytics -- Apply machine learning to gain a more complete understanding of your business processes, allowing you to make better judgments, projections, and optimization efforts.Security -- Use machine learning as one of the top mobile trends in data security to protect your consumers' sensitive data.Convenience and competitive advantage -- AI enables biometric verification and provides several solutions, including picture recognition, voice help, smart maps with route planning, and others, all of which can play a role in user retention.What is possible in the realm of AI/ML on mobile applications?14. AR & VRSince the release of Civilisations AR, the use of virtual and augmented reality features in mobile software has increased dramatically. Civilisations AR is an augmented reality production from the BBC that serves an educational function in a genuinely amazing way. It lets users interact with ancient artefacts by rotating, moving, and scaling them.AR and VR are already being used for a variety of applications other than game production, thanks to recent developments in smartphone apps. Virtual reality in education delivers effective hands-on training experiences while being safe and relatively inexpensive, which is especially beneficial to the healthcare, aerospace, military, and industrial areas.When utilized for online purchasing (enabling users to "try on" an item using their phone), marketing, and home and property tours, augmented and virtual reality can entice clients. Learn more from our article Augmented & Virtual Reality (AR/VR) in mobile apps.15. Enterprise mobile appsEnterprise mobile applications are one of the hottest business trends since they allow you to interact remotely with coworkers, employees, or customers via mobile devices. Enterprise apps are excellent tools for controlling and improving corporate operations. The fact that these applications may be used on mobile devices adds to their popularity.We saw a growth in the number of medium and small firms interested in adopting enterprise mobility into their daily operations to boost productivity, profitability, and stay competitive.Business modelIn 2021, the development of mobile apps was the top priority for organizations and corporations. Are you prepared to plan your needs and create a reliable company mobile app? Here are the details you had to plan in 2021, details that would probably remain factual in 2022 as well.1. Proposition of valueCustomers will not use or purchase an app that does not address their issue. A proposition of value is a list of benefits your product provides to users and why they should pay for it. Let's look at a few mobile app value proposition business model examples:Novelty is defined as meeting needs that have never been met before or that have yet to be met.Productivity is defined as the efficiency with which a client's business or personal demands are met.Price is defined by providing a solution that is less expensive than the current one while maintaining or improving efficiency.2. AlliesWithout forming alliances with other individuals and groups, no firm can exist. As a result, a description of your important partners and cooperation should be included in your business model canvas. This year you had to consider the following forms of partnerships for a mobile startup:Co-founders -- Let's pretend that the individual who came up with the concept was a brilliant businessperson or salesperson but lacked a good technical background. They needed the help of a technologist, who served as the CTO and oversaw the technical aspects of the project.Contractors -- As you work on the mobile app, you need to sign contracts with organizations that will help you with different areas of the project, such as a software development firm, a marketing agency, a law and accounting firm, and so on.Suppliers -- If your digital business was going to be strongly integrated with selling, buying, or making real goods, you needed to form a connection with local suppliers.Be sure to involve all of the necessary parties to launch a successful business in the future.3. ResourcesTo form a mobile app business, you need a specific motor and cognitive property, as well as people and financial resources to build the app. This attribute was referred to as your essential resources in your business model canvas. Consider the following examples:Physical things such as equipment, buildings, and transportation are examples of material resources.Intellectual property, patents, trademarks, patterns, and databases, are examples of intellectual resources.Human resources are the individuals who will help you build your concept. This is especially true for undertakings involving science or creativity.Money assets, credits, and cash will be employed to finance the development process.4. CustomersThis is when you had to describe your platform's target audience. You should have assessed your potential clients from the standpoint of demographics, interests, and wants when working on this area. The following questions will be of use to you:Who are the people who could be interested in your product?What are their ages?What city do they call home?What are their passions?What are their necessities?What are they afraid of?What factors influence their purchase decisions?Why should people download your app?A buyer persona - a thorough description of your ideal customer - should emerge from this investigation. Knowing who your customer is and what his preferences are can help you create a product that is more tailored to his requirements.5. Relationship with customersYou have to decide how you engage and assist your consumers here. Let's have a look at how this was done.Personal assistance involves direct contact between a consumer and a corporate representative.Self-service - the corporation does not engage directly with clients but instead provides them with all of the tools they need to do all of their tasks on their own.Automated service is a more developed kind of self-service that combines automated technologies such as chatbots with self-service.Establishing communities where users may share their expertise is what community is all about. This form also aids the organization in better understanding its clients' wants.A buyer persona - a thorough description of your ideal customer - should emerge from this investigation. Knowing who your customer is and what his preferences are can help you create a product that is more tailored to his requirements.6. ActivitiesHow will you reach out to your consumers and provide them with your value proposition? This question may be answered using the key activities section of your business model canvas.If your organization is all digital, the majority of your efforts was focused on internet marketing strategies (email newsletters, social networks, online advertising, etc). Tangible applications also needed to focus on building physical infrastructures, such as warehouses, distribution centres, and shipping terminals.7. Sales channelsWhat strategy did you use to sell your value proposition? The major possibilities for mobile app business models are Android and iOS applications. You might also sell your goods using a website, email marketing, social media, and other methods.8. CostsThe more budget things you manage, the fewer obstacles you have while constructing your software. Let's go over the costs that undoubtedly occurred:Organizational charges –- legal and accounting services to create your firm as a legal organization.Required -- everything you need to get your business up and going, including an office and required equipment.Hardware - the labour of your software development team, and the upkeep of the web platform are all part of the development costs.Employee pay is a part of human resources.Advertising and marketing.We also advise that you to set aside some money for unplanned costs. It's always a good idea to be cautious.9. RevenueWhat were your plans for monetizing your app? Let's have a look at some of the possibilities:Selling the value proposition generates revenue (selling the physical goods, commission, subscriptions. etc).Advertisement (you could have used your platform to post ads).Use of a brand (when your app became a recognizable brand with a registered trademark, you were able to charge for use of the brand).After you’ve finished making a business plan, you can start thinking about developing your Android or iOS mobile app, so make sure to prepare yourself for this as well with the help of our articles.Staying on top of the mobile industry's challengesConsider a few things before getting started, like planning your mobile app and choosing the right developer. You must strategize before building your app, you must define characteristics such as objectives, budget, specs and scope, and before delivering your app to a mobile app developer, create a clear image of it so that you may be priced properly, sensibly, and realistically.We may come out as a bit biased here, however, it must be emphasized that we assist companies all over the world in fulfilling their ambitions for their mobile apps. With strong, agile teams and focused QA procedures, we deliver consistent, high-quality, and cost-effective products. Our professional staff can assist you with accurately identifying your requirements, selecting the technology and framework required to construct your app, customizing the app to meet your needs, updating and maintaining it regularly.We're here to help if you're not sure where to begin with your corporate or your own mobile app, therefore make sure to contact appssemble’s team, because we can assure you we are all professional, hardworking and of course, an excellent company. --- ### All about Push Notifications and how they can help you URL: https://appssemble.com/blog/all-about-push-notifications-and-how-they-can-help-you We have prepared a detailed article to help you understand what push notifications are or how to use them. Every day, we are exposed to upwards of 10,000 advertisements. While this may come as a shock to some, it simply goes to show how tough it is to capture a user's attention. An ever-increasing level of competition doesn't help matters, driving businesses to come up with innovative ways to communicate with customers. If you have a mobile app, you must understand what push notifications are and while some of you may be aware of what a push notification is and how it works, the question remains, are you taking advantage of it?Push notifications are an excellent marketing tool for anyone who has a mobile app since they allow you to communicate with your consumers. Just be cautious when employing this method. If you use this strategy too frequently, people may choose to ignore your push alerts. This is clearly something you should avoid.I'm here to help those of you who don't understand what push notifications are or how to use them. That is why I wrote this manual. That way, you'll be able to figure out how to apply them to your current mobile app. Let's get started.What are Push Notifications?A push notification is a brief message that prompts the user to take action. Push Notifications, first offered by Apple in 2009, have evolved into a significant user interaction strategy in past years. In today's busy, distracted world of short attention spans, Push Notifications aid to capture a user's attention. Users receive them when an update is available, when something is due, or when they need to resume to an app.Push notifications can be sent by websites, web apps, smartphone apps, and even wearable apps. With consumers spending approximately 5 to 6 hours each day on their phones, mobile app notifications are a great way for developers, marketers, and app publishers to encourage users to take action.Different forms of push notifications are used by current mobile advertisers to encourage consumers and promote engagement:To boost sales, eCommerce stores deploy tailored push notifications.To keep users up to date, social networking apps offer real-time information.Content is sent by media businesses to deliver time-sensitive information.Types of Push NotificationsLocation-based notifications: When users visit a specific location, they receive location-based notifications. Consider Google Maps recommending nearby areas of interest according to your recent travels, or a dating app telling you to find your match in a new location.Transactional push notifications: Transactional push notifications inform users about recent acquisitions, membership renewals, order tracking, and other relevant information. Transactional notifications are used by banking apps, financial platforms, and eCommerce apps.Customized notifications: Notifications that are customized are used to provide relevant information to mobile devices. For instance, a customised special offer to persuade a user to make a purchase.Insightful push notifications: These messages provide real-time information and updates. Consider news applications that bring you real-time information on global events or a weather app that keeps you up to speed on the weather.Promotional push notifications: Apps use push notifications to distribute promotional and marketing offers to segmented user lists. Promotional notifications can boost website traffic and conversion rates while also being a more cost-effective marketing tool than PPC, social media, and other channels.Abandoned carts push notifications: These push messages prompt clients to finish their transactions. These are also used by eCommerce platforms to inform purchasers that a bargain is only available for a short time.Rich push notifications: use video, GIFs, emojis, or graphics to attract attention and increase interaction. For example, food photos linked to restaurant menus are used by online food delivery companies to make customers order directlyTriggered push notifications: These push notifications have been triggered as a result of the user's actions. One example could be receiving a daily mobile reminder about an exercise after signing up for a health or fitness program.Time-sensitive push notifications: Users will feel a strong call to action when they get time-sensitive notifications. In the eCommerce industry, this is ideal for limited-time offers or promoting discounts.Reminders: Reminders assist users to remember crucial things like meeting somebody, finishing a daily chore, and so on. How can push notifications help you?Push notifications provide a fantastic chance for mobile entrepreneurs to communicate directly with their customers.If used effectively, Push Notifications can be a great tool for connecting and gratifying people. Some of the advantages of using them for mobile apps are as follows:Users can choose whether or not to receive Push Notifications. This provides the user power over them, making them less likely to uninstall your mobile app just because they dislike or find Push Notificationss bothering. This alternative is a win-win situation because only those who are eager for your Push Notificationss will receive them.Push Notifications can be sent based on the user's location, giving them a lot of flexibility. As a result, you'll be able to tailor your marketing plan to each market or location, improving your likelihood of succeeding.Push notifications are little more than a marketing tool because they can assist you to improve the user experience. Even though the two are strongly interrelated, there is a distinction to be made between delivering a message that simply promotes a new feature and one that provides value to the user. Things are all about how you say it at the end of the day.Push notifications improve user retention and engagement. As previously said, these notifications are a call-to-action and, just as they can aid in conversions, they can also be used to increase user engagement. A significant part of this is not going overboard, because users who receive too many Push Notifications are more likely to unsubscribe or abandon your app completely.What characteristics make a Push Notification great?It's not enough to understand the significance of push notifications. You must devote time to your marketing plan and understand what makes them succeed. They might implode if they don't.You need to know who your intended audience is , just as you do when designing a mobile app, so you can figure out what sort of message to deliver and when. This will assist you in crafting the most effective message for that audience and ensuring that it is received well.Make your messages distinctive. Personalized material has a higher chance of making an impression than generic stuff. Make use of whatever data you have about your consumers to create a push notification that is tailored to their preferences. This also applies to user segmentation; there are a variety of methods to divide consumers (by region, demographics, or device kind), all of which may help you design a more tailored strategy. A tailored message is more likely to be opened by the recipient, resulting in higher retention and engagement.Keep in mind the various gadgets. Knowing a user's mobile device is important for a variety of reasons. It's crucial to note in this example that while an Android user is more likely to click on a push notification than an iOS user, iOS users open the messages seven times quicker. It's also crucial to comprehend how this influences your plan.Use analytics to your advantage. Any marketing plan should be based on data analytics. You should explore the effects of your push notifications on your most important metrics and make necessary adjustments. When you miss the target, analytics will assist you to improve your plan. You may experiment with different sorts of messages and sending times until you find what works best.Find a perfect equilibrium. As previously said, one of the most important aspects of good push notifications is not going overboard. You should strike the correct balance between delivering too many or too few alerts and distracting or discouraging your users.Push Notifications Do’s and Don’tsHow do Push Notifications appear to users?Users typically receive notifications in the form of a banner or pop-up alert while using their phones. This message appears regardless of what the user is doing. Push notifications are usually displayed in a single window on most operating systems. iOS has the Notification Center where users access it by swiping down from the top of the screen, and it is sorted in chronological order. Unread messages are displayed on the lock screen of Android devices. Users can configure push alerts for particular apps. Users can turn on or off notifications, as well as select the alert style used by iOS and Android. Users can also change the red label on an app's homescreen icon that displays the number of unread notifications.20 Push Notification statistics for 2021In recent years, push notifications have become an important element of a marketer's toolkit. Here are 21 intriguing statistics and facts about push notifications that you should be aware of:Based on the device and sector, push notification subscription rates to range from 0.5 % to 15%. Currently, the financial sector has the greatest rate of opt-in.While you may execute push campaigns on both mobile and desktop platforms, the former gets a larger rate of subscribers 60% than the latter 30%. The remaining 10% are tablet users.Push notifications can enhance app retention by 3 to 10 times.In terms of click rate and subscription rate for mobile push notifications, Android smartphones exceed iOS devices, 91.1% for Android vs. 43.9% for iOS.A single push notice sent to new customers within the first week after installing the app may increase retention by 71% over the course of two months.The average click rate for web push notifications is 12%, but with push notification management, this may be increased to 15%. This percentage rises to 18% when push alerts include rich media.When you run highly focused push notification campaigns, you may receive a 30% click rate.Push notifications for cart abandonment have a click rate of 16%, while push notifications for re-engagement mobile marketing techniques have a CTR of 13%. Campaigns that have been recently viewed have a CTR of 13%.The largest click rate is found between 3 and 6 p.m. The best days to increase opening ratios are Wednesdays and weekends.The largest subscription rates of the year occur in July and December.Depending on the sector, the best day and hour to deliver push alerts differ. eCommerce often receives the best answers between 3 and 4 p.m. on Wednesdays, media and marketing between 9 and 10 a.m. on Tuesdays, BFSI between 3 and 5 p.m. on Tuesdays, and digital marketing firms between 2 and 7 p.m. on Tuesdays.Including actionable CTAs in push notification campaigns can increase their success rate by 40% or more.Among all businesses, the eCommerce industry sends the most push alerts, 22.03%. Media, blog articles, and publications all pay attention to it. Media, blog entries, and publications are all carefully following it, with 18.79%.Push notifications have a 3500% return on investment!.Users who had been active in the previous 24 hours had the greatest push notification delivery rate, which was above 80%.Email marketing appears to be losing ground to push notifications in terms of results. When comparing open rates, click rates, and retention rates, push notification campaigns saw a 50% boost in opening rates, a 7-fold rise in click rates, and a 93% increase in retention rates.Push notifications are incredibly beneficial to 70% of app users, and as a result, 53% of these users are prepared to give personal information like their location.The most popular push notification content is promotions 34%, followed by fresh developments 26% and geo-localized material 26%.App users that opt in to get push alerts to see their retention rates double, with an app engagement rate of 88%.Emojis 20%, industry-specific send timings 40%, rich formats 25%, personalisation 4x, and advanced targeting may all help increase push notification open rates 3x.For a better engagement, use Push Notifications smartlyIs using push notifications a requirement? No. But is this something you should be doing? Absolutely. You can see how push notifications can benefit your app and your business based on everything we've discussed. When communicating with consumers, push notifications are far superior to SMS. Just ensure you don't deliver them too frequently, or users will stop getting them. To improve the user's experience and provide value, send them based on their location. Push Notifications with customised content, for example, can help you boost interaction, loyalty, and recruitment. When sending them out, remember to keep the user's device in mind.Look no further, we’re here to support you at every step of the way!As always, get in touch if you’d like to discuss more. Until the next article, use them push notifications wisely, folks! --- ### An easy guide on where to announce your startup to the world URL: https://appssemble.com/blog/an-easy-guide-on-where-to-announce-your-startup-to-the-world Check out this detailed guidebook on where can you publish for free your mobile app startup. Do you think your hard work is done once you’ve developed your mobile app? Not really. If you want your app to perform well, you will need to actively promote it because success does not happen by itself. Promoting/marketing applications is difficult, and if you don’t have hundreds of followers on social media, it may seem impossible. However, there are certain things you may do to spread the word on your own.People that enjoy your products are, of course, your primary advertising avenue. Their sharing efforts are the most effective kind of advertising. As a result, the fundamental concept is to develop a product that is helpful, usable, and appealing to end consumers. Then and only then does it make sense to share the word about the things you’ve done.To give you more information on publishing your mobile app, here are 8 categories from where you can promote your new startup plus another:Publishing NewsMaking an app release is probably the simplest method to introduce yourself and your company to the public. There are thousands of new enterprises popping up all over the place. So, publish your news on pages which you wish to be included. Reddit is perhaps one of the most interesting social networks. It can be very odd at times and users can be ruthless, but its 51 million unique users can nevertheless offer you a good community to promote your mobile app. After you draft an intriguing app release describing your startup's goals, you can share it either on Reddit or 13 other platforms, so download the handbook and check out the other sites as well.Creating a Product PageOne of the most essential pages on your website is the product page. So it's obvious that you'd want to make a good one. Product pages that are well-designed can help convert browsers into customers. They also assist in providing your consumers with the knowledge they require to make an informed purchase. ProductHunt is a great place where you can submit carefree your app. There’s a ranking system that can be a bit intimidating but you can still get some good SEO boost there. Other than that, we have prepared for you 4 other sources to help you create your product page. Take a look.Posting an ArticleYou have many choices now when it comes to posting articles about your startup. The internet is a beautiful and large place where you can even be a little pretentious when it comes to choosing where to post articles. One platform that’s growing is LinkedIn, and there you can promote your business just great since the audience is already there and LinkedIn might even promote your content, therefore you’ll get great reader engagement. We also have other 25 well-selected sites where you can publish great information about your startup for a massive community, so don’t miss them.Sharing to the News BlogsTNW said that when they couldn’t find a technology event where to promote their startup, so they decided to host their own. Check out their page and post news about your mobile startup. Consider what your target audience would find useful and entertaining, and keep a list of your preferred sites so you can quickly and easily discover links while doing status updates. Post interesting content regularly to establish your page as a reliable source of important information. You might leave a brief remark explaining why you believe it is essential to share. Try doing this on any of the 11 sites we have prepared for you.Q&AsNot all information can be written down, and much of what it can still isn't. It's still in people's brains or is only available if you know the proper individuals. Bringing together individuals with diverse viewpoints so they may better understand each other, and empowering everyone to share their knowledge for the benefit of the rest of the world, is one method to link the people who have information to the people who need it. Quora is one of the 2 social networks we establish the right usage of social media platforms. You can update your product’s new features and options and gather customers' attention with the Q&A method. Check the other platform where you can gather around a question and provide insights about your mobile app and startup.Posting on ForumsPosting on a forum is a fantastic approach to receiving answers from the forum's community. A forum-related topic will encourage others to respond to your post. Once you've created an account in the forum where you want to post, you may start creating new topics. HackingWithSwift is a popular website among the iOS developer's community, and they have an App Announcement section where your can post your new mobile app and further announce your app updates or deals, and people or why not, possible customers can follow and appreciate you. We also recommend you 2 others, so feel free to check them out as wellUploading a VideoBecause YouTube is one of the most famous websites in the world, with a massive global audience, a solid YouTube social media plan may do wonders for your online success. And, while YouTube marketing may have appeared out of reach for small businesses and start-ups a few years ago, it is now easier than ever, so give it a try!The suitable choice of what you require will aid in the efficient use of resources, time, and effort. In turn, appssemble is prepared to maintain and upgrade your app in addition to building it. It’s simple, contact us for further information on how to fine-tune your application with no worries. --- ### Why you should update your mobile app frequently URL: https://appssemble.com/blog/why-you-should-update-your-mobile-app-frequently You should aim to be up-to-date and relevant with everything, so here is why an old mobile app might be bad for your business. Once you’ve finished developing your Android or iOS mobile app, you launch it and then people start downloading it. After the initial wave of app download has passed, things may slow down, and if you don't update your app, it may become lost in the sea of many others. When you invest in a business, you anticipate a profit, just like any other company owner. The correct parameters were initially set to give the ceratin outcomes. Your application is a ship, and the updates it receives are a breeze, ensuring that users receive continuous value.It is no longer enough to give a high-quality digital platform in today's infinite application environment. The world of technology is rapidly evolving. Your application really shouldn't stop in order to exist and compete with other apps. Regular software feature upgrades will keep it from rusting, and consumers will be given new chances rather than abandoning it.Building a mobile app for your business is a significant undertaking, therefore you must comprehend the significance of having a mobile app for business and the benefits of updating it periodically. This article will explain why your company needs to update the app it manages, what are the downsides of not updating it, and how often you should do it.Issues with apps that are not updatedThe world is going mobile and your app is competing with millions of others. But with great power comes great responsibility. Believing that once your app is released, the work is over, couldn't be further from the truth. It's important to understand the significance of mobile app updates. Updating mobile apps is essential to keep your users and maintain a sense that your business still exists and is doing well.1. The user experience is damagedApps that appear hastily constructed or as if creators aren't striving to address particular problems within the software, have a hard time holding their users. Most of the time, they are soon forgotten.By upgrading your app on a regular basis, you not only keep it current and up to date, but you also demonstrate to consumers that you actually care about their experience and want to enhance it.In the battle for the greatest app, consistently upgrading yours with meaningful new features demonstrates to customers that you are truly concerned about their requirements.2. Going incognito is a brand killerUsers can see the last time you updated an app, whether it's on Google's Play Store or Apple's App Store.If the user perceives the design to be outdated and notices that it hasn't been changed in a long time, it appears that your organization is stagnant. Users are left to wonder if the firm is still in operation and if they are committed to maintaining their own app. These are the kinds of doubts that no company wants to be linked with.This is particularly necessary as mobile app expectations continue to evolve. When a new feature is introduced to the world of applications and becomes popular, it is no longer considered an additional value, but rather the standard by which other apps must be judged.This type of function is changing the landscape of every app style, and upgrades may help you keep on top of current trends.3. You don't care about brand loyaltyYou should constantly seek user feedback as a developer. While programs are thoroughly tested before being released, certain bugs and mistakes are unavoidable.Even a minor problem might result in a remark being displayed on app reviews. By addressing concerns as soon as they are raised, you will gain the trust of your user base.So, examine app store customer reviews, ask users to rank your app internally, or encourage answers via email. Whatever you decide, keep an eye on reviews and resolve issues as soon as you can.4. You’ve got nothing to tellDevelopers should be searching for new and enhanced features to optimize the end-user experience from the minute an app is launched.It is critical to notify users when you hit particular benchmarks. Not just for the purpose of openness, but these improvements may also revitalize users and increase engagement.It is common for people to install the app and afterwards fail to engage it. When you plan a new update around a milestone, you remind users why the app exists in the first place while also welcoming them back with better features that encourage interaction.5. Out of sight, out of mindAs Homer said in The Odyssey, Out of Sight, Out of Mind represents exactly what you think it does, once something is gone for a period of time, it is no longer thought about.When you update your app, you provide consumers with another opportunity to interact with it. You're putting your brand back to the forefront of their minds the instant you invite them to see what fresh things you've done.When you update your mobile app, you have the option of sending out a relevant push notification informing users of new changes. You may inform your users about all of these new features and how your app's functionality has improved.6. Making users vulnerable to hackersThe major reason anyone creates updates is to protect oneself from vulnerabilities. Older software will continue to include the same bugs and weaknesses in the code that hackers and cybercriminals may exploit.This is amplified by the fact that all of these vulnerable entry points are often made public whenever hackers discover them.Unfortunately, just as engineers rapidly find ways to close vulnerable gaps in their software, hackers find new ones too.App MaintenanceWhy is it important to update your app?People enjoy novelty, so do something new and follow the trends.Get rid of everything that is no longer relevant and make room for renovation.Mobile status, because you need to maintain a good reputation.Amend your mobile strategy.Optimization of user experiences like outdated design, interface, rebranding, and OS.Keeping everyone safe.How often should you update your app?What do you say? Every week, a month, a year? Customers, as well as Apple App Store and Google Play Store, prefer applications that are regularly updated. In theory, there are a few straightforward options:Consistent updating -- It implies that there is a method and a schedule for updating mobile apps.As a result of necessity -- bug fixes, new feature releases, and so on.At the moment -- you update your app whenever you want, without any schedule.According to Instabug data, the top 100 revenue apps are published every 14 days. Appbot discovered that the top 200 free apps are updated every 18 days.The frequency with which you should update your app is determined by your business goals and functionality. In the context of a free app, we recommend that updates be released more often, every 20–25 days. This is due to the fact that you must monetize it by offering advertisements, paid premium services, and in-app purchases. You should continuously expand and improve the application's capabilities. In the event of a paid app, updates should be made every 50 to 55 days. To summarize, the ideal choice is to deliver updates every 20 to 40 days.How does Google rank your app update?Retention of an appNumber of downloadsDownload growthNumber of user ratings and reviewsRegular app updatesPage rankSocial media "Rep"The keyword rate factorVideo demonstrationHow does Apple rank your app update?Length of use, duration, retention app stay time, uninstallNumber of app searchesNumber of app downloadsNumber of user ratings and reviewsApp Update Frequency Statistics 2021The rate at which mobile app developers update their apps on the Google Play Store and Apple App Store provides a different perspective on the Android and iOS marketplace. While apps update provides a general view of the worldwide app industry, it may also be used to investigate the engagement, and thus market vitality, of each genre, subgenre, location, or country.Updated vs. not-so-updatedHere is a quick comparison between apps that update more frequent, keeping themselves over the top, addressing issues and improving their app constantly and the ones who don’t:Health & Fitness: MyFitnessPal vs. ErgomoWhile MyFitnessPal updates its app 2,3 or 4 times a month, with a sum of 9 updates in the last 3 months only, Ergomo did its last update 11 months ago. Okay, sure, it’s not fair to compare one big and popular app with any other, but if you want to grow your business, and make your app a success like the other one, you need to update and be up-to-date. As a result, MyFitnessPal has 1.3 million ratings, and Ergomo has non yet.Entertainment: Crunchyroll vs. Stremio OrganizerYep, as you guessed by now, Crunchyroll is updating its app often, once a month specifically. Therefore it has many users, hence the 377.9K ratings. On the other hand, we present you Stremio Organizer which unfortunately did its last update 1 year ago and with a habit of updating once a year, therefore no reviews or ratings are available yet.Podcasts: The Podcast App vs. RadioPublic - The Podcast AppAnd lastly, here are two Podcast Apps. Both of them should be popular right now since almost everybody listens to podcasts lately, right? Wrong. While The Podcast App has a tendency to update 2,3 or 4 times a month, keeping the app fresh, safe and bug-free, justifying its 209K ratings, RadioPublic made its last update 2 years ago and people don’t really like that, therefore they don’t download, rate or review the app.Consequently, the fact is that apps must be updated on a frequent basis in order to remain relevant and functional. Just like you wouldn't launch an app with a confirmed flaw, updates keep your program safe and allow you to fix any issues that arise. Acknowledge that upgrading your app isn't a suggestion, but rather a need if you want to stay relevant. Taking advantage of possibilities to improve your app is a continual process that evolves in tandem with market changes and improvements.The suitable choice of what you require will aid in the efficient use of resources, time, and effort. In turn, appssemble is prepared to maintain and upgrade your app in addition to building it. It’s simple, contact us for further information on how to fine-tune your application with no worries. --- ### Essential advice for mobile startup founders URL: https://appssemble.com/blog/essential-advice-for-mobile-startup-founders A thorough list of the most essential and transformational startup tips. A lot of the advice provided to startups is tactical and it’s supposed to be useful on a day-to-day or week-to-week basis. Some though is more fundamental. Here is our list of the most essential and transformational startup tips. The advice provided here will assist most entrepreneurs in finding their way to success.Begin immediatelyThe first word of advice we usually provide to entrepreneurs is to launch their product as soon as possible. This is the only way to understand consumers’ problems and whether the solution fits their demands. Delivering a poor product as quickly as possible followed by user feedback and iteration is far superior to waiting to develop the “ideal” product. This is true as long as the product has a “quantum of usefulness” for buyers whose worth outweighs any flaws.Once a company is up and running, we advise entrepreneurs to avoid doing things that don’t scale. Many startup advisers encourage businesses to expand up far too soon. This will cause the development of technology and procedures to enable scalability, which, if undertaken prematurely, will be a waste of time and effort. This technique fails and even the demise of a business. Rather, we tell companies to obtain their first client by whatever means required, even physical labor that could not be managed for more than ten consumers, much alone 100 or 1000.Create something that others wantAt this point, entrepreneurs are still determining what needs to be created, and the best way to do it is to speak straight to the customer. For example, the Airbnb founders first offered to “professionally” photograph its earliest customers’ houses and flats to make their listings more appealing to renters. Then they went and took their photos. Their site’s listings improved, conversions increased, and they had fantastic discussions with their consumers. This was completely unadaptable, but it was critical in learning how to establish a lively marketplace.Determine the 90/10 solutionTalking to users results in a large, difficult list of features to create. In this scenario, one piece of advice that we often provide is to seek the “90/10 answer.” That is, search for a technique to accomplish 90% of what you want with 10% of the work/effort/time. There is always a 90/10 answer accessible if you look hard enough. A 90% solution to a genuine customer problem that is immediately available is far superior to a 100% one that takes decades to create.Write code & interact with clientsAs a company grows, there is a multitude of possible distractions. Conferences, meetings with venture investors or corporate development executives from major corporations, pursuing press coverage, and so forth. We often tell entrepreneurs that the most crucial responsibilities for an early-stage firm are to write code and communicate to customers.This means that to create something people desire, any firm, software, or otherwise, must first launch something, then talk to your users to determine whether it meets their requirements, and then take their input and improve. These duties should take up all your time and attention. This cycle never stops for excellent firms. As your company grows, entrepreneurs will be forced to pick between numerous routes for their firm. It is almost always better to pursue the more ambitious option; it is remarkable how often entrepreneurs manage to avoid dealing with these types of challenges and instead focus on other things.Identify 10–100 consumers that admire your serviceWhenever it comes to customers, most entrepreneurs don’t know that they get to pick theirs, as much as their customers do. We remark that a small number of customers who appreciate you is preferable to a huge number who only tolerate you. In other words, acquiring 10 consumers who have a pressing issue is far superior to recruiting 1000 customers who have a little issue. Because it is simple to make mistakes when selecting consumers, companies must dismiss their customers. Some clients might cost far more in terms of income or learning than they offer.Development is the outcome of a good product, not the cause of itProgression is always a priority for startups because a startup that does not expand is typically a failure. Yet, when and how to grow are frequently misinterpreted. We urge firms to communicate to their consumers, develop what they want, and iterate rapidly, so growth is a natural byproduct of properly completing these three tasks.However, expansion is not always the best option. It makes little sense to expand if you have not yet created something that your consumers desire — in other words if you have not established a product-market fit.Don’t expand your game until you’ve created something that people desirePoor retention is almost usually the end consequence. Furthermore, if you have an unproductive product, expansion drains cash from the firm. It makes no sense to charge a consumer 80 cents and then give them $1 back. It should come as no surprise that unit economics are important, yet far too many companies appear to overlook this fundamental truth.Avoid lengthy transactions with large clients whenever possibleThe instinct of startup founders will always be to do more, but the ideal approach is always to do less, but well. For example, founders are typically attracted to pursue significant agreements with large corporations that symbolize great, company-validating partnerships. Deals between huge corporations and small startups, on the other hand, rarely end favorably for the startup. They take too long, are too expensive, and fail altogether. One of the most difficult aspects of starting a business is deciding what to do because there is an unlimited number of things that might be done.This means that to create something people desire, any firm, software, or otherwise, must first launch something, then talk to your users to determine whether it meets their requirements, and then take their input and improve. These duties should take up all your time and attention. This cycle never stops for excellent firms. As your company grows, entrepreneurs will be forced to pick between numerous routes for their firm. It is almost always better to pursue the more ambitious option; it is remarkable how often entrepreneurs manage to avoid dealing with these types of challenges and instead focus on other things.Know that at some time, every startup backfiresVery early a startup must choose the one or two key metrics it will use to measure success, and then founders should choose what to do based exclusively on how the task will impact those metrics. When your early-stage product isn’t working it’s often tempting to immediately build new features to solve every problem the customer seems to have instead of talking to the customer and focusing only on the most acute problem they have.Value does not necessarily imply successFounders are frequently surprised to discover that they need not be concerned if their firm appears to be damaged. It turns out that almost every startup, even ones with billion-dollar valuations, has profound, basic problems. Success is decided not by whether you are broken from the start, but rather by how the founders deal with the inevitable issues. As a founder, your work will frequently appear to be constantly correcting a damaged thing, therefore it’s quite normal.As a fresh startup entrepreneur, it is impossible not to worry about competition, both present and hypothetical. Spending any amount of time thinking about your competition is almost always a terrible decision. We like to argue that startup firms are always killed by suicide rather than murder. There will come a moment when competitiveness will be crucial to your business’s success, but this is extremely unlikely to be the case in the first year or two.The funds you raise are not your ownThe first item of fundraising advice is to gather funds as fast as possible and then return to work. When a firm is fundraising, it is generally easy to tell by looking at their growth curve, and then when it flattens down, they are soliciting funds. It is also critical to recognize that value is not the same as success or even the possibility of success. It is necessary to keep in mind that the funds you raise are not your own. You have a legal and ethical obligation to spend the money exclusively to improve your company’s chances.Maintain your sanity and your startup out of chaosIt is also critical to maintaining your sanity throughout the unavoidable chaos of startup life. So we constantly advise entrepreneurs to take pauses, spend time with friends and family, get proper sleep, and exercise in between periods of hard, concentrated work. Finally, a word on failure. It turns out that most businesses fail quickly due to founder dissatisfaction. Relationships with co-founders are more important than you realize and open, honest communication between founders reduces the likelihood of future blunders. It turns out that being kind is one of the finest things you can do to make your business successful, and indeed, to be successful in life.We understand what a challenge it is to be a first-time tech founder. It’s pretty difficult to pitch, design, develop and market your idea. Not to mention how hard it is to prove you’ll succeed in a very competitive industry.appssemble is here to be your bold digital product development partner! This service is the cheapest way to start your startup. What will we do? We'll help you define your product, understand its technical feasibility and costs, then validate it. You’ll receive all the tools and information you need to pitch to investors or develop your next products. Come up with the idea and we’ll help you with the rest! --- ### COVID-19 impact on tech startups in 2021 URL: https://appssemble.com/blog/covid-19-impact-on-tech-startups-in-2021 Check out the effects COVID-19 had on tech startups, and what’s the future for them. Unlike most other industries, the tech business has passed relatively well throughout the COVID-19 storm. Whereas stay-at-home restrictions and company closures have wreaked havoc on industries that depend on physical services and in-person consumers (such as hospitality, arts, and tourism), tech companies appear to be surviving this crisis relatively unharmed.Nevertheless, with the coronavirus boosting our daily screen time by a third and accelerating the adoption of digital technology by several years, the incidents of the pandemic have caused several aspects of the software industry to function better than they did before. Now is a good moment to reflect on how these past years' exceptional circumstances have contributed to the recent spike in software development. Now is a good time for tech startups to begin their journey.In the following article, we will be covering several subjects like digitalization during COVID-19, how startups around the globe are dealing with the ambiguity of the new normal, and a little about the future of the tech industry.Digitalization and COVID-19The epidemic made it simpler for startups who had been contemplating whether or not to embrace digital transformation. Nobody expected COVID-19, and no one predicted the changes it would bring to corporations in all industries, therefore the ones that can survive without much struggle are the ones that can apply the digital transformation.The term digital transformation refers to the integration of digital technology into all areas of a business, which alters the way organizations function and provide utility to their consumers. Technology, data, process, and organizational change are the four key domains of digital transformation, with each domain dependent on the others so that firms can establish themselves in the digital economy.How are startups dealing with the new normal across the globe?As previously said, the impacts of COVID-19 may be felt all over the world and have a substantial impact on startups in the technology industry. From raw material supply shortages to disruptions in the electronics value chain. Positively, the disruption has encouraged remote working and a quick focus on assessing and de-risking the end-to-end value chain.On the other hand, now is the time for Tech Startups Industries, since there are 5 branches that are growing during COVID-19: Artificial Intelligence (AI), Healthtech/biotech, Space tech, Edtech, Fintech. Their potential long-term effect on technology sub-sectors such as software development reached these 5 stages:On the other hand, now is the time for Tech Startups Industries, since there are 5 branches that are growing during COVID-19: Artificial Intelligence (AI), Healthtech/biotech, Space tech, Edtech, Fintech. Their potential long-term effect on technology sub-sectors such as software development reached these 5 stages:1. Increased productivity as a result of remote workingWhile the transition to working from home disrupted communication and limited collaborative work for many organizations, it did appear to have a silver lining — it improved productivity. Many people believe that the COVID-19 standards shifted their attention to software development and IT operations. Others will claim that it has accelerated their cloud migration activities.Why is this likely to have occurred in the IT and software industries? Because software development is generally a solitary activity, remote working appears to function well by preventing coders from wasting too much time in group meetings. When it comes to staying in touch with the team, the variety of video conferences and social platforms such as Slack, Skype, and Telegram, makes it possible. Furthermore, because of the flexible structure of remote work, software engineers may adapt their schedule to their preferences, allowing them to produce more output in an eight-hour day than they could in a lengthier in-house office stay.Even so, the information on higher efficiency during COVID-19 seems to come with certain cautions. While larger trends indicate that productivity was increasing, others suggest that certain employees struggled to avoid distractions and that their performance dropped as a result of the lockout. As a result, with remote working clearly not benefiting all software workers, a hybrid working style may give diversity and additional support to IT workers as we enter a “new normal”.2. Increased request for servicesDespite the decrease in requirements for most key service providers through 2020, demand for data and software development positions has increased. Data and software development positions grew by 1% and 8%, respectively, during the first few months of the crisis, with data engineering positions increasing by 6% once lockdown limits were announced. The biggest noteworthy spike, however, happened before the coronavirus was widely known, with demand for IT positions increasing by 93% in January 2020 when compared to December of the previous year.Aside from the increased need for software services, low-code development methods are also getting more popular. While there is concern that new user-friendly software platforms would reduce demand for software engineers, it is feasible that these technologies could increase the value of conventional developers’ labor. Whether it’s reading and publishing data, organizing data storage, or dealing with hosting or logins, low-code systems can handle the basics while developers focus on their more specialized tasks. So, with increased demand for low-code tools and conventional software developers as a result of the pandemic, this can only be positive for the software business in the future.3. Increased digital expenditures70% of startups decided to increase or maintain expenditures in digital technology, while just 19% intended to decrease tech budgets. The increase in expenditure appears to be accompanied by concerns about economic circumstances affecting business, with 52% of firms admitting to boosting digital spending as a result of the macroeconomic disturbance created by COVID-19. Given how disruptive the epidemic is proving to be for businesses and startups, it’s no wonder that firms are leveraging digital technology to allow employees to work from home, automate processes, and remotely help customers.Investing in digital transformation initiatives often brings benefits. Many people claimed that previous digital transformation programs were effective based on a variety of different assessment parameters. Fintech initiatives received 19.9% of funding, distribution and services received 18.6%, and digital infrastructure received 14.8%. Although software spending was somewhat lower, 40% of firms expected to increase their software budget.4. Increasing customer preferencesIt’s no wonder that COVID-19 shook up customer behavior. From purchasing groceries online to depending on eCommerce sites and click-and-collect services, the days of leisurely in-person browsing are pretty much gone for many individuals. Startups are now expected to create attractive websites or apps that market their products and allow for remote buying.5. Advancing tech-led healthcare solutionsAnother unanticipated result of the COVID-19 pandemic was a greater role for digital technology in healthcare. From hospitals using software to give patients with contact-free healthcare services to private firms developing AI apps to alleviate some of the healthcare responsibilities, digital solutions have aided the healthcare system in quantifiable ways.What’s the future for Tech Startups?The number of businesses that have worked on new development products in fintech and finance has increased significantly. Startups, with a little creativity and money, can identify trends and leverage long-term technologies. What are the main industries to monitor, and can an industry like fintech continue to stimulate the economy and offer the tools we need to recover from the pandemic’s impact?Building a significant social impact will be critical.Customer service will be a big issue for the majority of startups.AI will be used more prominently by tech startups.Working from home or remotely will become more common.New innovative and creative approaches to improving employee well-being will be implemented.Resilience will become an important factor in tech startup success.If there is turbulence in a firm, that can result from disrupted structures, routines, and capabilities. Unfortunately, planning is needed for effective crisis management, and few companies could’ve been prepared for a crisis of the size of the COVID-19 epidemic. In general, the qualities of creative startups should make them more suited to deal with the COVID-19 problem than other types of businesses. Being creative is a prerequisite for being resilient, as innovative firms continually anticipate and react to a wide range of problems. Businesses, on the other hand, may not always understand the true threat that a possible crisis event carries, and the vast majority of startups will not have been prepared for the occurrences.The concept of a turning point for technology adoption or digital disruption is not new, but the statistics show that the COVID-19 problem is a historic turning point and that further adjustments will be necessary as the economic and human situation unfolds. It also demonstrates that important lessons may be gained from the efforts that companies have already made. One is the significance of learning, both tactically and organizationally, in the process of making particular changes to organizations. Both forms of learning will be essential in the future, as the rate of change is unlikely to diminish.ReferencesCovid-19 and the technology industry (PWC)COVID-19 Pandemic: Shifting Digital Transformation to a High-Speed Gear (Pedro-Soto Acosta)How COVID-19 has pushed companies over the technology tipping point—and transformed business forever (McKinsey)Startups in times of crisis – A rapid response to the COVID-19 pandemic (Journal of Business Venturing Insights)Maximizing the impact of technology investments in the new normal (Deloitte)5 ways COVID-19 has accelerated software development (Market Finance)We hope this information helped you get more informed on what happened to startups during COVID-19 and what is still to happen. Whenever you feel overwhelmed, or you might need help with your project, we are here to assist you in creating your best startup and reaching success, so get in touch and let’s discuss more. --- ### Why competition is bad for your mobile startup URL: https://appssemble.com/blog/why-competition-is-bad-for-your-mobile-startup Find out what competition does to your startup business while aiming for the monopoly. IntroductionPeter Thiel said an interesting fact in an article in The Wall Street Journal “What valuable company is nobody currently building? This question is harder than it looks because your company could create a lot of value without becoming very valuable itself. Creating value isn't enough—you also need to capture some of the value you create.”In “Competition is for Losers”, he talks about business strategy, competition, and the monopoly theory. The main idea that Peter uses as a rule in his business and investments is that, if you're starting a company or if you're the founder entrepreneur starting a company, you always want to aim for monopoly and you should always avoid competition because competition is for losers.Peter, the founder of PayPal and Palantir, and investor in world-changers like Airbnb, SpaceX, and most of the tech companies in Silicon Valley, outlines 6 directions that you should understand as a startup founder, directions that we will present in this article, which are Capturing Value, The Lies People Tell, How to Build a Monopoly, The Last Mover Advantage, The History of Innovation and The Psychology of Competition.Capturing valueHow do you go about creating value? What makes a business valuable? We'd like to start with this first direction by saying something about the idea of embarking on a startup. There's a very simple formula, that if you have a valuable company two things are true:Number one, that it creates "X" dollars of value for the world.Number two is that you capture the "Y" percent of "X." And the crucial thing that people always miss in this sort of study is that "X" and "Y" are completely independent variables, and so "X" can be very big and "Y" can be very small. "X" can be an intermediate size and if "Y" is big, you can still have a very big business.For example, even large corporations may be bad businesses. United States airlines serve millions of passengers and generate hundreds of billions of dollars in revenue each year. Yet, in 2012, when the average trip price was $178, airlines earned 37 cents for each passenger journey.In comparison, Google generates less value but takes more. Google made $50 billion in sales in 2012 (compared to $160 billion for airlines), but it kept 21% of that income as profit - more than 100 times the airline industry's profit margin that year. Google earns so much money that it is currently worth three times as much as all the United States' airlines combined. Airlines fight against one another, while Google remains alone. Economists illustrate the distinction using two simplistic models: perfect competition and monopoly.In Economics 101, perfect competition is both the ideal and the default condition. When producer supply meets consumer demand, a market is to be completely competitive. In a competitive market, every business is similar and sells the same items.Because no business has a monopoly on the market, they must all sell at whatever price the market sets. If there is money to earn, more businesses will enter the market, increasing supply, driving prices down, and so eliminating the profits that drew them in. If too many businesses enter the market, they will lose money, some will collapse, and prices will return to sustainable levels. Under perfect competition, no corporation generates an economic profit in the long term."The opposite of perfect competition is a monopoly. Whereas a competitive firm must sell at the market price, a monopoly owns its market, so it can set its own prices. Since it has no competition, it produces at the quantity and price combination that maximizes its profits. -- Peter Thiel"To an economist, every monopoly appears the same, whether it eliminates rivals, obtains a governmental license, or innovates its way to the top. We shouldn't have an interest in unlawful bullies or government favorites. If a corporation is so good at what it does, no other company can offer a near alternative. Google is an excellent example of a firm that progressed from 0 to 1. It hasn't competed in search since the early 2000s when it separated itself from Microsoft and Yahoo.The lies people tellSo let us talk a little bit about the lies people tell. Imagine that there were companies that went from perfect competition to monopoly. And people who have monopolies pretend not to. So anyone who has a monopoly will pretend that they are in incredible competition.Now imagine if you are competitive, and if you're in some sort of business where you'll hardly make any money, it will be tempting to tell a lie that goes in the other direction. And you will promise to do something unique that is somehow less competitive because you want it to be different.Thus if the monopolists pretend not to have monopolies and the non-monopolies pretend to have monopolies, the plain difference is very small and the real difference is quite big. So there's this business deformity that happens because of the lies people tell about their businesses, lies that are sort of the opposite.How to build a monopolyLet's move on to the third direction. One of some very counterintuitive ideas that come out of this monopoly thread is that you want to go after small markets. If you're a startup, you want to get a monopoly. You're starting a new company, you want to get to monopoly.Monopolies have a large share of the market, how do you get to a large share of the market? You start with a small market and you take over the whole market and then over time you find ways to expand that market in concentric circles. The first mistake is going after a giant market on day 1. That's evidence that you somehow haven't defined your categories, which means there is going to be too much competition in one way or another."You want to be a one-of-a-kind company. You want to be the only player in a small ecosystem. You don't want to be the fourth online pet food company. You don't want to be the tenth solar panel company. You don't want to be the hundredth restaurant in your zone." -- Peter ThielThe first very unreasonable idea is to go after small markets, markets that are so small that people often don't even think that they make sense. That's where you get a foothold and then if those markets can expand, you can scale into a big monopoly business. There are always very unique businesses that are doing something that has not been done before and ends up having the potential to be a monopoly.The last mover advantageOne way to think of Peter’s fourth direction is through the idea that most of the value in these companies exists far in the future. If you do a discounted cash flow analysis of the business, you'll need to consider the following. Look at all the profit streams, have a growth rate, the growth rate to be higher than the discount rate so most of the value survives far in the future.Growth is something you can measure in the here and now, you can always track that. The question of whether a company will or will not be around a decade from now, is actually what dominates the value equation and that's a qualitative thing.And so if we go back to the idea about characteristics of monopoly, the proprietary technology, network effects, economies of scale, you can think of these characteristics as ones that exist at a moment in time where you capture a market as it is and take it over but you also want to think if these things are going to last over time.So there's a time dimension to all these characteristics. Network effects get more robust, and so if you have a network business it's often one that can become a bigger and stronger monopoly over time.History of innovationThere are some very interesting perspectives on the whole history of innovation in technology and science. We've lived through 300 years of incredible technological progress in many different domains. Steam engines to railways, the telephone, refrigeration, household appliances, the computer revolution, aviation, all different areas of technological innovation. Then there's sort of a comparable thing to say about science where we've lived through centuries of enormous amounts of innovation in science as well.To build the future we need to challenge the dogmas that shape our view of the past. That doesn’t mean the opposite of what is believed is necessarily true, it means that you need to rethink what is and is not true and determine how that shapes how we see the world today. As Peter Thiel says, “The most contrarian thing of all is not to oppose the crowd but to think for yourself“. -- Process Expert TipBecause "X" and "Y" are independent variables, some of these things can be valuable innovations, but the people who invent them and come up with them, do not get rewarded for this. You need to create X dollars in value and you capture Y percent of X. We live in a culture where it's very hard to get people to buy anything that's super complicated and takes very long to build. We shouldn't rationalize that way. It's worth understanding this better.Psychology of competitionThe idea of Peter’s last direction is that the psychology of competition is for losers. It’s always a provocative way to title something because it's in our nature to think losers are the ones who are not good at competing. It's not the case that we don't understand this monopoly-competition dichotomy. It's because people lie about it, it's distorted, the history of innovation deliberates it in all these very strange ways.“Competition is for losers. Winners too, but statistically speaking, it’s mostly losers” - @perlhackIt's an intellectual blind spot, where we find ourselves very attracted to competition, and in one form or another, we find it reassuring if other people do these things. There is always this question about competition as a form of validation, where we go for things that lots of other people are going for. It's not that there is the wisdom of crowds, it's not that lots of people are trying to do something, but because that is the best proof of being valuable.Therefore, so much of people's identities get wrapped up in winning these competitions that they somehow lose sight of what is important and what is valuable. Competition doesn't make you better at whatever it is that you're competing at because when you do it, you're comparing yourself with the people around you. But this way, you're figuring out how to beat the people next to you, how to do better than whatever it is they're doing, so you will get better at that. Don't always go through the tiny little door that everyone's trying to rush through, go around the corner and go through the vast gate that nobody is taking.Starting a business is difficult, and building a successful firm necessitates several sacrifices. If you're looking for a team of mobile experts that would help you take your idea and transform it into a user-validated mobile app, get in touch, we would love to help! --- ### A conclusive guide for making your Android Google Play submission successful URL: https://appssemble.com/blog/a-conclusive-guide-for-making-your-android-google-play-submission-successful A step-by-step guide and materials needed for making a successful Google Play submission. The number of available apps in the Google Play Store is placed at more than 3.4 million apps. Google Play is certainly one of the largest platforms for distributing, promoting, and selling Android applications.Publishing your Android app on Google Play is not only exciting but also a crucial element of your application development process that influences its final success. Will your app be submitted, will it be popular, and will people download and install it? All this and more depends on how fruitful your release will be.Why is it important to have a good Product Page?In the Android ecosystem, the Google Play product page is almost the only way to get potential users to install a mobile app or game. In other words, almost all potential users for an app are exposed to the product page, making it one of the most important elements in a mobile growth strategy. The Google Play product page should convey to potential users the most impactful messages around why they should install the app, the unique selling point of the app, and the benefits of using it.The Google Play Store is a marketplace and in this economy, potential users consider multiple apps and games when they face a certain problem or are looking for their next piece of entertainment. App developers who best understand their users will be able to craft the most effective creatives enjoy higher conversion rates and even lower user acquisition costs. All things equal, the developer with the most understanding of their users will be able to command higher growth rates.NameThe name of an app in the Google Play Store is an important ASO (App Store Optimization) on-metadata factor to keep in mind. It affects, above all, the search results, but as well the conversion rate to install.Google allows developers to include 50 characters in the app Title, so use them wisely. Keep your brand name short, easy to spell, and easy to memorize for your users. Include your most relevant keyword(s) alongside your brand name. This can significantly improve your app keywords rankings!Remember that you can add one title in each language to localize your app. Don’t ignore localizing your app title — the mobile world is global, and the demand for your app can arise from the countries that you have never expected.Short descriptionYou must provide a short description to publish your store listing. Your short description is a quick synopsis meant to spark user interest by outlining your app or game’s key value. Your short description is the first text users see when looking at your app’s detail page on the Play Store app and can be expanded by users to view your app’s full description. The description can appear in locations beyond your store listing, so any user should be able to use it to quickly understand the core purpose of your app or game.In Google Play Store, the short description of an app has a strong effect on the ASO in keywords rankings and conversion rate. Google allows developers to include up to 80 characters for the short description, and if the users are interested to know more, they can expand the short description to view the full description of your mobile app or game.Highly recommendedSummarize the core function or purpose of your app or game in simple and concise language, highlighting any aspects that make it unique.Reflect on the latest state of your app or game.Avoid time-sensitive copy that can become outdated quickly to reduce the need to update.Call-to-actions, for example, “download now,” “install now,” “play now,” or “try now.”Localize your description as appropriate for different markets and languages.Avoid slang or jargon, unless it is a language that would come naturally to your target users. Ensure your short description is correctly formatted: Do not include special characters, line breaks, emojis, emoticons, repeated punctuation. Only capitalize your app name if your Google Play listing app name is also capitalized.ScreenshotsUse screenshots to convey capabilities, the look and feel, and the experience of your app to potential users for better app discovery and decision making. You can add up to 8 screenshots for each supported device type: Phone, Tablet (7-inch and 10-inch), Android TV, and Wear OS by Google.Screenshots may be displayed throughout Google Play, for instance in search or on the homepage, in addition to your store listing on Google Play. When Google Play displays both your preview video and screenshots together, for example on your store listing page, and if your preview video is available then your screenshots will be shown after the preview video, followed left-to-right by the screenshots best suited for the device the user is browsing on.Requirements To publish your store listing, you must provide a minimum of two screenshots across form factors that meet the following requirements:JPEG or 24-bit PNG (no alpha)For apps, you must provide at least four screenshots with a minimum 1080px resolution. These should be 16:9 for landscape (minimum 1920x1080px) screenshots and 9:16 for portrait screenshots (minimum 1080x1920px).For games you must provide at least three 16:9 landscape screenshots (minimum 1920x1080px) or three 9:16 portrait screenshots (minimum 1080x1920px). Make sure these screenshots depict the in-game experience so users can get a sense of what the gameplay will be like if they download and play.Screenshots must demonstrate the actual in-app or in-game experience, focusing on the core features and content so users can anticipate what the app or game experience will be like. Stylized screenshots that break UI across multiple uploaded images are allowed, but prioritize UI in the first three screenshots as much as possible; Use high-quality images with the proper aspect ratio and avoid inappropriate or repetitive image elements.If you’re also interested in iOS App Store submission, we recommend you to check out our article on this topic, “A conclusive guide for making your iOS App Store submission successful”.Feature graphicAs the name points, the feature graphic is an image used by Google Play when they recommend your app. Since the majority of apps have a preview video, the feature graphic will usually have a Play button overlaid on top of it and will allow the video to be played instantly, on click. Unlike the iOS App Store where you have to use a frame of the video as a thumbnail to be displayed before the screenshots, in Google Play you have to upload the asset separately.RequirementsJPEG or 24-bit PNG (no alpha)1024x500px dimensionsIconAn icon is the first visual impact that your app will have on the user, the essence of your application. Right after making the search request in Google Play, what the users see is a huge list of apps with different names and icons, and at this point, the users will decide which app to check out and install.You must provide an app icon to publish your store listing. The app icon does not replace your app’s launcher icon but should be a higher-fidelity, higher-resolution version that follows Google Play’s icon design specifications. Your app icon is used in various locations on Google Play, including your store listing, search results, and top charts.Once you got the requirements right, you should start prioritizing your efforts towards the features that have the most impact and influence on the overall decision of the app user. Hence, growing your app’s chance of getting downloaded.RequirementsJPEG or 24-bit PNG (no alpha)512x512px dimensions1024KB maximum file sizeMeets Google Play’s icon design specificationsPreview VideoIf an image is worth a thousand words, a video is worth a thousand images! A preview video is effective to show the capabilities, look and feel, and experience of your app to potential users for better app discovery and decision making. It is not required, but we highly recommend providing a preview video for games particularly. Your game requires a preview video to be shown in certain parts of Google Play. You can add one preview video to your store listing by entering a YouTube URL in the “preview video” field.Your preview video is displayed before your screenshots on your app’s store listing on Google Play. Users can watch the video by tapping on the play button that overlays on your feature graphic.RequirementsDisable ads for your video to be shown on Google Play. Turn off monetization in your video, or upload a different video without monetization claims and update the URL in Play Console.Set your video’s privacy setting to public or unlisted, do not set it to private, and do not use an age-restricted video.Make sure your video is embeddable on Google Play.Properly localize the video including the UI, taglines, and audio.360-degree stereoscopic imageTo publish a Daydream-enabled app, you’ll need to add a 360-degree stereoscopic image to your Store Listing page. When you’re creating a 360-degree stereoscopic image, think of it as your app’s background image within the Play Store on a Daydream device.RequirementsJPEG or 24-bit PNG (no alpha)4096x4096pxStereo 360°15MB maximum sizePricingWhen it comes to pricing, you can set your app as free or paid, update your app’s pricing universally or per country, and use pricing templates to simplify them for your apps in Play Console. After you publish an app or update, including price changes, adding SKUs, or making changes to your app’s distribution settings, it can take a few hours for your changes to be shown on Google Play.Make your app free or paidOpen Play Console and go to the App pricing page (Products > App pricing).In the “Pricing” section, next to “Your app is,” click Make your app free or Make your app paid.Changes to your app’s Free or Paid selectionYou can change your app from Paid to Free.Once your app has been offered for Free, the app can’t be changed to Paid. If you want to charge for the app, you need to create a new app with a new package name and set a price.Enter a priceWhen you offer paid apps and in-app products on Google Play, a service fee applies. If you aren’t distributing a paid app or in-app item to a country that you enter a price for, users won’t have access to it.You can use pricing templates to set up or manage the same set of prices for multiple paid apps and in-app products. If you update a pricing template, all items linked to the template will use the template’s latest prices. You can use up to 100 different pricing templates per developer account, and you can link up to 1,000 items to each pricing template.There are a few ways you can temporarily offer your apps for free or at a discounted price:Offer your paid apps at a discounted price.Give users a paid app or in-app product for free with a promo code.ReviewGoogle Play has been adjusting its app review process, requiring some apps to take more time for a thorough review before approval. This can impact the timing of an app or update going live, so developers should keep it in mind when pushing out updates for functionality or App Store Optimization.The important thing for developers to do is to plan their releases accordingly. Since it is possible that apps can take up to a week to be approved, they should plan for an appropriate time frame for the approval process. If a developer is aiming for a specific release date, they should publish to a closed testing track, then use Timed Publishing to go live at the specified time. They should still submit it at least a week or more in advance, in order to provide enough time for the Google Play review process or in case the app gets rejected and requires fixing.How to prepare your app for review by providing app informationAdd a Privacy policy -- Adding a privacy policy to your app’s store listing helps provide transparency about how you treat sensitive user and device data. The privacy policy must, together with any in-app disclosures, comprehensively disclose how your app collects, uses, and shares user data, including the types of parties with whom it’s shared. You should consult your legal representative to advise you of what is required.Ads -- You must declare whether or not your app contains ads. This includes ads delivered through third-party ad SDKs, display ads, native ads, and/or banner ads). Apps that contain ads will have a “Contains ads” label shown on their store listing. This label will be visible to all Play Store users.App Access -- If your entire app or parts of your app are restricted based on login credentials, memberships, location, or other forms of authentication, you must provide access details.Target audience and content -- You must declare your app’s target age group. Any apps that include children in their target audience must comply with Google Play’s Families policy requirements. It’s important to provide accurate information about your app. Depending on the target audience selections that you make, your app may be subject to additional Google Play policies.Permissions declaration form -- You can communicate familiar and locally relevant content ratings to your users and help improve app engagement by targeting the right audience for your content. To prevent your apps from being listed as “Unrated,” sign in to Play Console and fill out the questionnaire for each of your apps as soon as possible. “Unrated” apps may be removed from Google Play.ReleaseWhether you’re publishing an app for the first time or making an update, your app’s publishing status helps you understand its availability on Google Play. You can see your latest publishing status under the title and package name when you select the app in Play Console. For certain developer accounts, Google will take more time to thoroughly review their app to help better protect users. This may result in review times of up to seven days or longer in exceptional cases. You’ll receive a notification on your app’s Dashboard about how long this should take.There are three types of publishing status:App status -- Helps you understand your app’s availability on Google Play and who it’s available to (such as testers, all Google Play users, etc.).Update status -- Helps you understand the availability of your latest update. An update is a set of one or more changes that you’ve made to your app.Item Status -- Helps you understand the availability of a specific part of an update, such as a particular release, a content rating, or a store listing experiment.Publish a draft appWhen you’re ready to publish a draft app, you’ll need to roll out a release. At the end of the process, clicking Release will also publish your app. If you see the heading “Errors summary” at the top of your app release’s review summary page, click Show more to view the details. When available, you can also view the recommended or required resolution. You can’t publish your app until errors have been resolved. If you only have warnings, minor issues, or a combination of the two, then you can still publish your app, but we recommend addressing them before doing so.Publish an app updateStandard publishing -- Updates to existing apps are processed and published as soon as possible. By default, your app will use standard publishing. Certain apps may be subject to extended reviews, which may result in review times of up to seven days or longer in exceptional cases. Go to Update or unpublish your app for more information.Managed publishing -- Updates to existing apps are processed as usual. After they’ve been approved, you control exactly when the changes are published. Go to Control when app changes are published with managed publishing to learn more.Once you’re done with submitting your app and finished publishing it, you want to start promoting it since user download action isn’t enough for you to grow, therefore we recommend you to read our article on “How to promote your mobile app for free”.We hope these instructions will help you get through the submitting process easier, and that soon, the Google Play Store users can download your very special app. But remember, the journey does not stop at publishing. Running a mobile application requires continuous efforts to get it trending, otherwise, competition will overshadow the app, but if this is your first product and you feel overwhelmed, contact us at appssemble, and our experts will help you make it a success for sure! --- ### Ten innovative applications that you should check in 2021 URL: https://appssemble.com/blog/ten-innovative-applications-that-you-should-check-in-2021 Check out some of the apps we find intriguing and see what makes them special Coming up with million-dollar app ideas is not easy. The concept of the app is the foremost important part of creating a successful app, just after finding the mobile app development company with the best developers to hire on the team. App developers are improving and enhancing our smartphone and tablet experiences daily. In fact, so many Android and iOS apps come out every day that it’s difficult to keep track of them all. It’s difficult to usurp the best of the best but if you’re getting bored with what you’ve got and you can’t think of novel ideas for your app, here are some original app ideas for 2021 that you can steal:Eyeware BeamEyeware Beam is an app that shows a lot of potentials. They have a demo app on the app store to showcase their implementation of an eye tracker using just an iPhone or iPad that has a TrueDepth camera. If you are a streamer the best use case would be to show a circle where you are watching the screen, as you have probably already seen on other streamers, but without buying a dedicated piece of equipment for this, as it’s not cheap. Maybe you just want to see how your audience will take it.Another use case would be to rotate the camera around you while driving in a game in first-person mode. I’m talking about the simulators/driving games that support this function, like Euro Truck Simulator 2. I can see it being really useful, especially if you already have a wheel and pedals.If you are a streamer or you play games that could benefit from it you should try it out, as for now, it’s free. The app gives you an installer on a windows machine and needs to be in the same network for it to work. The whole connecting process could be improved and I think it will as the app matures.Wheels — Ride SafeWheels — Ride Safe is an app that allows you to enjoy a ride with a Wheels vehicle, a hybrid between a bicycle and a scooter. The Wheels vehicle in itself it’s very innovative, but the app doesn’t fall much behind. The cool thing about it is that the Wheels vehicle seems to have a built-in speaker that offers hands-free navigation or music with the help of the app and also an easy way to unlock the helmet from the holding enclosure on the vehicle. They also claim it’s one of the safest vehicles around, and at a first glance it does look safer than an average scooter, so if you ever have the opportunity, you should try it out and let us know if it raises the expectations. Just from the app alone, it seems to offer more than the competition so it would be nice to see them grow and be available everywhere because let’s face it, green cities are the right way if not the only way.The app has a 4.5 out of 5 and over 60.000 ratings. Its Age Rating specifies 4+ so it’s for everyone. Also available in many languages like English, Danish, Dutch, French, German, Korean, Polish, Portuguese, Simplified Chinese, Somali, Spanish, Swedish, Tagalog, Traditional Chinese, Vietnamese. It collects information like Financial Location, Contact, Identity, Usage, and Diagnostics. It’s available both for Android 8.0 and up, or for iOS 11.0 or later, and it’s free of charge.Verishop — Social ShoppingEveryone knows shopping is more fun when you are doing it with someone else and this app makes that a lot easier. So, Verishop — Social Shopping, combines shopping and social media in a single app. Users can upload and share their ideas, follow other brands and people just like you would on a normal social media app. Furthermore, they have a shopping party where users can join their friends in a live shopping session, or just live stream their shopping experience.You can discover unique brands and new trends; watch Livestream Shopping for styling tips and beauty demos, and chat with streamers in real-time; hang out and video shop with friends; share your styles with the community — all with the convenience of Free Shipping, Free Returns, and 24/7 Customer Care.The app has over 500 ratings already and a 4.7 out of 5 stars, so the numbers don’t lie, people like it. Even the reviews are generally great, customers are pleased to use it since they think it’s fast, easy to use, and shop, it has great products and filters and the design is amazing as well; The app is designed just for iOS and it requires compatibility for iOS 11.0 or later, it’s for people over 17 and it’s free of charge. So here are just a few reasons why Verishop is a great app, beautifully build and pleasantly presented for the user.BearBear is an app where you can write in portable Markdown notes, encrypt your notes, sync notes, organize notes with nested tags, add sketches, pick a beautiful theme, export to a variety of formats. Bear is a focused, flexible notes app used by writers, lawyers, chefs, teachers, engineers, students, parents, and more! Bear has quick organization, editing tools, and export options to help you write quickly and share anywhere and preserve your privacy with encryption. The app has so many features, but here are some of them easily synthesized:Write our way with flexible yet simple toolsOrganize quickly with tasks and hashtagsShare anywhereSearch all the thingsUse it everywhere with sync in Bear ProPrivacy for your notesThe app has a rating of 4.7 out of 5 and over 5k reviews, it’s free of charge but has in-app purchases like a monthly Pro subscription of $1.49 or a yearly Pro subscription of $14.99. It’s available in many languages like English, French, German, Italian, Japanese, Korean, Portuguese, Russian, Simplified Chinese, Spanish, and Traditional Chinese. It requires an iOS system and an iOS 11.0 or later. Supports Family Sharing and Siri, so it’s very accessible for everyone.Gawq — Local & World NewsGawq is a news app with no biased algorithms. Local, national, & world news from over 850 top media sources. They believe that you should have easy access to news from all sides, and without being manipulated by a click-hungry algorithm. It filters the noise and stays informed with 360-degree coverage on breaking stories happening near you and around the world. They also have as a source some of the most well-known media stations like Fox News, CNN, NBC, CBS, BBC, NYT, NY Post, The Guardian, ESPN, NBA, NFL, MMA, US Weekly, Vanity Fair, TMZ, Billboard, Rolling Stone, Wired, TechCrunch, NASA, National Geographic, and many others. The app offers you the following features and assets:850+ top sourcesNo biased algorithmsNo in-stream adsFilter opinions, celebrity, politics, or non-newsLocal news & weatherFollow your favorite topics & keep up with the latestBe the first to know with major news alertsMute topics or sources that clutter your feedReview media coverage to help build a better news platform for allCompare the latest fact checks across the webThe app has a rating of 4.6 out of 5. As a privacy policy, they use your Location, Identifiers, Contact info, Usage data, and Diagnostics. It’s free of charge, with an age rating of 17+, and available for iOS 11.0 or later, and for Android 5.0 or later.Warby ParkerThe app Warby Parker says is the easiest way to shop for Warby Parker eyeglasses, sunglasses, and contacts. With the app, you can:Shop frames starting at $95, including prescription lenses.For iPhone X and above you can virtually try on frames with life-like accuracy, and you can also measure your pupillary distance (PD) in no time — no card or ruler necessary.Try out shop Scout, their very own brand of daily contact lensesShop daily, bi-weekly, and monthly contacts with no hidden feesStrengthen your sunglasses game by an exponential factorHandle all of your eyewear prescriptions with easeWarby Parker has your eyes covered. Whether you’re looking for designer eyewear at a revolutionary price or your next supply of contacts, you can handle it all in one place. With free shipping and returns, it’s easy to shop with no risk. Plus, apps are fun. The also has a policy that for every pair purchased, a pair of glasses is distributed to someone in need.People seem to really enjoy this app since it has a rating of 4.9/5 and over 200k reviews, most of them being positive. As for privacy policy, it uses data such as Health & Fitness info, Contact info, User Data, Purchases, Identifiers, and Search History. It’s available both for iOS 13.0 or up, as for Android 2.1 or up. It’s totally free o charge and accessible for everyone.Vera: Plant Care Made SimpleThe app Vera: Plant Care Made Simple s a plant care management app that helps you and your plants thrive! There are a few simple parts when it comes to using the app, and those are:Create a Schedule: Never leave your plant hanging again! Easily set up watering reminders and fertilizing follow-ups for every plant. Track your plants’ progress as you go and become the best plant parent.Track Your Plants: View your plant collection in one place, and create profiles for each leafy friend, with their name, adoption date, and photos you take. Log your plant care activities over time and watch your jungle thrive.Document your journey: Journal away when you’re excited for a new sprouting leaf, worried about unwanted pesty guests, or mesmerized by the way the morning light hits your Fiddle Leaf Fig just right.Learn New Skills: Curious about how to report your Monstera? Need to know how to trim your Money Tree? They’ve got you covered. The Library has all the plant care tips and tricks you’ll ever need. Plant Mom approved, of course!The app has a very pleasant design and a 4.3 out of 5. People seem to enjoy it, and when they feel like there’s room for improvement, they wrote feedbacks, which the developers seems to always take into consideration and improve their app. It’s available for Android, 6.0 or up, and iOS 12.0 or later. It’s for everyone who is into learning how to take care of their plants, and it’s free of charge.Vestiaire CollectiveThe app Vestiaire Collective is an app where you can buy and sell pre-owned designer items. You can join their global fashion activist community and discover thousands of carefully curated new bags, shoes, watches, and more. Every week, they add designer items from brands like Louis Vuitton, Celine, Gucci, Hermès, Rolex, and Cartier.The Vestiaire Collective app gives you:Access to thousands of unique second-hand items.Quality-checked designer pieces.Search tools for the brand, category, new arrivals, size, price, and more.Personalized notifications for items you’re looking for.A convenient way to sell designer items you no longer wear.An easy payment process, with the option of interest-free installments.With the Vestiaire Collective app, you can:Keep in touch with the Vestiaire Collective fashion community.Make offers to sellers and negotiate the price of an item.Add items to your wishlist and share the products you’re currently coveting.Follow members whose products and styles you like.The app has a rating of 4.7 out of 5 and almost 13k reviews. It’s available for multiple languages like English, French, German, Italian, Spanish, and it’s free of charge. Accessible for everyone, but only on iOS 12.0 or up, or Android 5.0 or up.PoparazziThe app Poparazzi is a new photo-sharing app where your social profiles are created by your friends. You are your friend’s paparazzi, and they are yours. You’ll receive a notification when a friend takes a photo of you. Don’t worry! You have complete control to remove any photo from your profile that you don’t like.Everyone can take photos of you on Poparazzi, but only users you follow can post directly to your profile. All photos posted by users you don’t follow will go through an approval process before they show up on your profile.Blocking a user will prevent them from being able to take or upload a photo of you. If you block someone on Poparazzi, they will no longer be able to communicate with you through the app. They won’t see photos you’re in and you won’t see photos they’re in.The app has a 4.6 out of 5 currently, and is available only for iOS momentarily, for versions or 13.1 or up. It collects information about contact and user and it’s free of charge.Otter: Transcribe Voice NotesThe app Otter is an app that helps you with automated meeting notes for Zoom, Google Meet, Microsoft Teams, and more. You can stay connected and collaborative when you work from home.Otter records and takes meeting notes for you in real-time, so you can stay focused on the conversation, and rest assured that all information (e.g. actions, highlights, photos, attendees) is captured, easily searchable, and shareable with your team. Supercharge your note-taking with AI and use Otter for all your meetings, interviews, lectures, and everyday voice conversations. Some of this app’s main features are:Take meeting notes automaticallyRecord & Transcribe LiveEnrich Notes with AIShare meeting and summary with teammates to keep everyone in syncRecord and transcribe interviews, lectures, podcasts, videos, webinars, keynotesProvide live captioning to deaf, hard-of-hearing, ESL people, and anyone with accessibility needsOrganize & ExportImport & SyncOtter has a rating of 4.8 out of 5 and over 17k reviews. It uses your Location, Contacts, Search History, Identifiers, and User Content. It’s available for everyone, free of charge but with a possibility of monthly in-app purchases of $12.99, or yearly for $99.99, for Otter Pro. It requires iOS 11.0 or later or Android 5.0 or later.These are just 10 of the innovations of 2021, but there are plenty of others that we didn’t mention. If you have the possibility to create something unique, do it! And if you struggle with the process, contact us and we can help you. --- ### A conclusive guide for making your iOS App Store submission successful URL: https://appssemble.com/blog/a-conclusive-guide-for-making-your-ios-app-store-submission-successful We walk through all the steps and materials needed for making a successful App Store submission. The App Store is a platform where you can distribute iOS apps. It was developed by Apple and it’s the second-largest app store (after Google Play) with almost 1.96 million apps available. Whereas the exact number of apps may fluctuate as Apple regularly removes low-quality content from their stores, the number of applications has been steadily increasing over the years.With a focus on bringing the best experience for the end-user, the store ensures every app has the highest standards that bring something new. It’s important to prepare an attractive and informative product page, complete with all important information. It’s a crucial part of the entire app development process.Why is it important to have a good product page?Along with the icon and the first two screenshots, the name contributes generously to the first impression as this is one of the first things your potential user learns about your app. On the product page, you provide detailed information about the app. This information will be visible to the App Store’s users. Here, you have the opportunity to encourage them to download your app by putting in well-crafted metadata.The product page contains a few tabs — iOS App, General, and In-App Purchases. So, coming up next, we’ll cover the following topics, product name & product description, assets, pricing, privacy, review, and release, which will help you better understand how to submit your iOS product in the best way by following Apple’s App Store Guidelines.NameYour discoverability chances grow once you give your app a good name. The title with the most relevant keywords included has the biggest impact on the App Store’s algorithm. According to Apple’s recommendations, the app name should:Be simple, catchy, compelling, and easy-to-understandCommunicate the key purpose of your appBe up to 30 characters longDiffer from competitors’ app namesExclude generic terms, popular app titles, special characters (e.g. #, @), prices, as well as celebrity names, trademarked terms, and other protected wordsSubtitlePlaced right below the title, a subtitle is a short phrase that brings additional information to your app. It complements the app name by communicating the purpose and value of your product in detail. To leverage your app name and subtitle, use relevant and descriptive keywords, and don’t include those already used in your title. The Apple App Store algorithm will only count them once. Here are the App Store requirements for the subtitle:It should be compelling to encourage users to explore your product page and download your appIt should be limited to 30 charactersIt shouldn’t include generic descriptions, for example, “world’s best app.”Title and subtitle together provide 60 characters for you to get through to your users. Focus on your distinctive features or typical usesSubtitles have to comply with App Store’s standard metadata rules. Avoid misleading or false product claims or inappropriate content, and never exploit competitor’s apps by any means.DescriptionThe first sentence (about 3 lines) of the description counts the most. So start with an attention-grabbing sentence that pitches users and sets out what the app is intended for, without having any references to another platform like Android, or Google, or that the product might be a beta, alpha, or test version, they should all be functional versions by then.Following should be an informative, comprehensive yet engaging summary of your app’s functionality and main features. Use the allowed space — up to 4,000 characters — to explain how your app differs from competitors and why users should download it. Take into account the following Apple’s recommendations regarding the product page description:Keep it concise, informative, and easy-to-understandStick to the tone of your brandAvoid forbiden terms (beta, Android, test app, etc.), keep it simpleAvoid keyword stuffing, otherwise, your app won’t pass the reviewDon’t mention prices: pricing is already disclosed on your product page and may also differ across the supported localizationsLet users know about your awards if any, but better do it at the end of the descriptionScreenshotsImages win the struggle with text for user attention. Screenshots are another visible product page element that contributes to your app’s impressions. App Store Connect requires uploading at least one app screenshot, while the upper limit is 10. Depending on the image orientation — portrait or landscape — the first 1–3 screenshots will be seen in search results. Therefore, Apple recommends using the first three image gallery visuals to convey the app’s purpose and value, while the rest of them may point out your distinctive features and complement the message.IconUsers see this element in App Store search results, even before they find themselves on the product page. The visibility of an icon places extra importance on how it should look like. To be eligible for the App Store, icons have to meet the following specifications:Color space: sRGB or P3 (see Color Management)Layers: flattened with no transparencyResolution: varies (see Image Size and Resolution)Shape: square with no rounded cornersPromotional textThe promotional text goes before the app description and is limited to 170 characters. A huge advantage of this product page element is that it can be changed without having to upload an updated app version. Consequently, it’s a good place to share messages that are limited in time, such as sales, announcements of new features, events or content, and more.PricingFor this part of the process, you’ll have to select your pricing and the territories it will be available, from the Pricing and Availability section. For pricing, even if your app is free, you have to input a start and end date. If you don’t plan on changing the price anytime soon, then you can select no end date. You’re also able to schedule a price change.For territories, you can select “All Territories” if you want your app to be available for download worldwide, however, some might recommend starting with a few places then expand later, so you can test how your app does on a small market, then you can expand.It might be common knowledge to developers that Apple only permits developers to sell apps at certain price points.Apple permits developers to choose from 94 price tiers, which range from US$0.99 to US$999.99. Developers pick one price tier, which applies to every country that their app is distributed in. So, before you submit your app for review, you must set a price for your app, which will be used for all App Store territories. If you don’t have a Paid Applications agreement, you can only choose a free price.What currency is used for a given App Store territory? You can refer to Exhibit C of your Paid Applications agreement to see the currency used by a specific App Store territory. You can select the territories where you want your app to be available on the App Store. By default, all countries or regions are selected, but you can deselect territories where you don’t want your app for sale. Your app will appear on the App Store in the updated or changed countries or regions within 24 hours. Now talking about Apple’s fees on your product. Apple's cut is between 15–30% (15%, for software developers with less than $1 million in annual net sales on their platform).PrivacyApples guiding principle of the App Store is very simple, they want to provide a safe experience for users to get apps and offer a great opportunity for developers to have success. They do this by offering a highly curated App Store where every app is reviewed by experts and editors to help users discover new apps daily.The App Store now helps users better understand an app’s privacy practices before they download the app on any Apple platform. On each app’s page, users can learn about some of the data types the app may collect, and whether that data is linked to them or used to track them. You need to provide information about your app’s privacy practices, including the practices of third-party partners whose code you integrate into your app, in App Store Connect.They also strongly support all points of view being represented on the App Store, as long as they respect the guidelines. Any attempt to cheat the system, for example by trying to trick the review process, steal user data, copy another developer’s work, manipulate ratings, or App Store discovery, your app will be removed from the store, and you as a developer will be expelled from the Apple Developer Program.You are responsible for making sure everything in your app complies with their guidelines, including ad networks, analytics services, and third-party SDKs. Apps should implement appropriate security measures to ensure proper handling of user information collected according to the Apple Developer Program License Agreement and their Guidelines, and prevent its unauthorized use, disclosure, or access by third parties.Apple wants their user to feel confident that the app they download is safe and will not break their phones. That is why:Users can choose whether or not to share dataEvery week, Apple's experts review around 100k appsThere were over 150k app rejections last year for violating privacy guidelines and over 1M rejections for inadequate contentEvery app has a page with detailed information, which an app owner must fill during the publishing processReviewFor your app approval to go as smoothly as possible, you should review the most common missteps listed below, missteps that can slow down the review process or trigger a rejection. So make sure that you:Test your app for crashes and bugsEnsure that all app information and metadata is complete and accurateUpdate your contact information in case App Review needs to reach youProvide an active demo account and login information, plus any other hardware or resources that might be needed to review your app (e.g. login credentials or a sample QR code)Enable backend services so that they’re live and accessible during the reviewInclude detailed explanations of non-obvious features and in-app purchases in the App Review notes, including supporting documentation where appropriateCheck whether your app follows the guidance in other documentation.After submitting, your app will be on the waiting list for Apple’s certification and review team. You’ll just have to wait now. In the past, the review process took between 1 to 2 weeks, and then a couple of years ago, they said they would be working on improving the speed, so the review process was cut down to a few days, usually between 24 – 48 hours, but certainly not weeks. The process isn’t artificial, but human. They have real persons playing with your app so they can give subjective feedback.ReleaseOnce the review process has finished successfully, you'll be able to publish the app (it takes between 24 - 48 hours to be available in the App Store). After the review process, the app can go directly to the store, or you can decide on what date you want it to be released. For existing apps that release a new update, phased releases allow you to distribute the update to the users over a period of 7 days. Phased releases don’t quite have the same flexibility as the Android staged rollouts but it is certainly much better than releases to potentially millions of users simultaneously.If you opt for phased releases, App Store Connect will gradually release your new version to users who have opted into automatic updates over the period of 7 days. All users can still bypass this and go directly to the app store to download the new version if they chose. It ramps up as follows:Day 1 - 1%Day 2 - 2%Day 3 - 5%Day 4 - 10%Day 5 - 20%Day 6 - 50%Day 7 - 100%You can pause a release at any time for a total maximum paused time of 30 days. This is a cumulative number and doesn’t reset if you unpause and pause again. You can pull the app version from sale if there’s a critical problem you can’t fix, this will remove the app from the store though so it’s a last resort. You’re free to cancel the phased release at any time and release it to all users.Even though the process may seem long and complicated at the beginning, with this article we hope we’ve shown you it’s not as hard as it seems. And if you still feel insecure about the whole process, don’t worry and contact us, because at Appssemble we’ve got it covered. We’ll ease the process because there’s already plenty of experience with apps launching in our background, so you don’t have to worry about it anymore. --- ### The ultimate guide to building user personas for mobile apps URL: https://appssemble.com/blog/the-ultimate-guide-to-building-user-personas-for-mobile-apps Check out how to create user personas for your mobile app and personalize the experience of your target audience. User personas are the foundation on top of which you build software products.Before thinking about the User Interface, technical solutions, and business model, you need to determine who your target audience is, who are you building a new mobile product for.Why do you need user personas?Having a clear picture of who your customers are, will help you create a product that better suits their needs and characteristics. User personas heavily influence the design hence the development phases as well as the business model used. For instance, colorful and playful interfaces work better on younger people, if your target audience is more mature the product you're building should also reflect that.Ideally, you should have the landing page ready a couple of months before the app is launched, this will help you gather early feedback regarding your product and can serve as a means of gathering email addresses from your tech-savvy, early adopters. Once the app is ready, you can email everyone that has expressed an interest in the app and ask them for their feedback, if done right, this should offer you a nice base of initial users. You can use free services such as mailchimp for sending out emails and measuring the engagement of the receivers. As a founder you have to walk a few miles in the shoes of your target customer, this will help you better grasp their motivations and will help build something that is custom made for the needs of your customers and the problem you're resolving. Surveys have shown that having a personalized experience for the target audience increases the revenue in 41% of the cases and improves customer retention for 51% of the users.How to create user personas for mobile applications?Before writing and creating user personas you need to conduct thorough researchfor your product. You need to have a clear vision of what problem is it solving, and what types of people would be interested in such an app.If you are not a solo founder and you already have a team, the Nielsen Norman Group has shown that projects in which the entire team is involved in the user research process are more likely to create better user personas.Firstly, you need to define where your target audience spends most of their time when online, for instance, if you have a mobile app that offers fashion advice, you might find that a lot of your potential customers spend a lot of time on Instagram. When creating a new user persona, it's best to start with a template that will give you a general structure to follow for your user research. Next, we are going to talk about every section from the template.NameWhen working on a new user persona, you firstly need to start with a name for your new persona. Usually, the name you use for the persona should reflect some of the personality traits of the user.As an example, if you're building a running tracking app, you could define a user persona for highly active runners (an example of persona name could be "Fast Jenny").Age rangeAge is one of the most important values to look at when building a product. The age of your core audience dictates the way the app should look and function. In addition to this, it also provides some insights in understanding better where is your product going to be used, what is the general emotion of your customer, and what things are important at their point in life.An app built for teenagers will look completely different from one built for 30+ years old, even if it solves the same problem -- for instance making a video call. The one built for teenagers will be more colorful and will have a lot of playful features to keep them engaged (video filters, masks, etc.) while the other one built for a more mature audience could focus more on productivity, integration with the calendar, fast inviting other peers to join a conversation and so on...LocationEven tho we live in the age of globalization, the location of your core audience impacts drastically how the product would be developed. By having a clear view of where your customers reside, the copy of your app could be more personalized. There are a lot of cultural differences and something that could work in Asia, won't necessarily apply to Africa or Europe for the same types of people.An example of this is making a payment, in a lot of African countries a different payment system (M-Pesa) is used widely, but integrating and promoting such a service in Europe or America might not be useful or suited as most of the people in those geographical areas are used to paying directly with credit cards or services such as Apple and Google Pay.GenderThe gender of the core users of your app is important as it will help you build a better solution for the problem you're trying to solve.For instance, if your app is focused on women's health, the majority of your users will be women, you might not want to use leaderboards for motivating the users to use and engage with your app. Women are usually not driven by the same goals and motivations as men and finding the right incentives for using your app could make the difference between a failed and a successful product.Income"How is my product going to make money?" is one of the first questions a founder should answer. The income of your target audience dictates how to product and the business model should be structured.For instance, if you're solving a problem for high-income earners, you could make your app paid, or having in-app purchases for some of its content. On the other side, if the wast majority of your users won't be able to pay a monthly fee for your services, in-app ads might be a better revenue source.ProfessionsThe profession of the users helps a founder make a better assumption on what are the interests of the audience.If the app is focused more on persons who work in creative professions, then the app should take advantage of this. As an example, a note-taking app for creative people will be different from a note-taking app for mathematicians. Creative types are more likely to draw and doodle, and they don't care about inputting complex mathematical formulas easily in the notes.Personality traitsThe personality traits of your target customer also affect the product. Studies have shown that personality traits have a significant impact on user adoption in the case of mobile applications.If you're building a photo library app for organized people having the ability to create albums would be one of the main flows of the app. If you're building the same app for more careless users, they will probably use more the search function, as they are interested in finding a specific photo without caring how the photos are organized.We use the following additional questions to better define the personality type of the user:Is this persona more introverted or extroverted?Are they analytical or creative?Are they more active or passive?What personal characteristics are important to be taken into account?What goals is the user trying to achieve?Another important characteristic when building a user persona is detecting what that specific user is trying to achieve. This is especially useful in situations where the app could have 2 different types of users.As an example in the case of an on-demand delivery app, the customer's goals are different from the deliverer's goals.What keeps them motivated in completing their task?By fully understanding what is the motivation of the users are, the product team could enhance those experiences by making it easier for the user to achieve them.In the case of a calorie counting app, some users will want to lose/gain weight, while others might only want to keep track of the foods they ate, based on the target audience those motivations might result in new or more customized features.EnvironmentThe context in which the user is using the app has a major factor in how it would need to be designed and developed.If a founder is building an app for measuring the performance of athletes, the user experience should also reflect that. When a top athlete is training and wants to measure his blood oxygen levels, they don't care about the typography of the app or the colors used, they need a fast and accurate method for starting/stopping the measuring.Where are they physically, what are they doing, and what is their mindset?While for some of the apps the location in which they are used is not important, for others, it's one of the most important aspects of the app. By knowing where the user is when using your app and what's their mindset, the entire experience and approach for solving a problem would be different.CityMapper is one product that nailed this. Users of the app use it while navigating the city or commuting and are usually under the stress of being in an unknown, new city or being in a hurry. One of the most common ways of traveling in big cities in the metro system. Once the users are underground, they don't have an active internet connection anymore, so the team behind the app has found ways of helping them navigate the city without using an internet connection (local push notifications, timers for the schedule of the trains, and so on).User storyThe user story is used for describing how the current user persona would use the app, it usually the main, most common flow that the user is going to make. It's a summary of everything we've collected about the user with the previous questions.An example of a user story for a booking app for speakers would be: "Dave whos an industry leader in the domain of AI, wants to share his knowledge on a new ML algorithm with the community. He makes a video (with the front camera of his device) in which explains the broad concept of the algorithm and posts it to his profile".How to make sure you're building a good user persona?All the information you write in the user persona chart should be backed by research and statistics combined with real observationsMake sure the user persona has as much detail as possibleEnsure that the created user persona reflects behaviors from the target audience, not your personal assumptionsUser personas are the foundation of every product, if this process is done right you will easily validate/invalidate the idea of your product, the feature specs and roadmap become more clear and the design and development are better in sync with your target audience. Thinking about building an app or someone to help you out scoping your idea? Get in touch, we'd love to help! --- ### How to promote your mobile app for free URL: https://appssemble.com/blog/how-to-promote-your-mobile-app-for-free How to promote your mobile app for free Founders usually overestimate what publishing an app in the AppStore or Google play would do, they expect flocks of people downloading and trying out their new mobile app, unfortunately, that's not the case. Doing marketing for a mobile product is not easy nor is cheap, but there are a couple of free-ways of attracting users to your new app.WebsiteEven before launching the mobile app, you should take care of the website/landing page for it. A website offers your app a unique place on the web, where you can engage with customers on your terms.Ideally, you should have the landing page ready a couple of months before the app is launched, this will help you gather early feedback regarding your product and can serve as a means of gathering email addresses from your tech-savvy, early adopters. Once the app is ready, you can email everyone that has expressed an interest in the app and ask them for their feedback, if done right, this should offer you a nice base of initial users. You can use free services such as mailchimp for sending out emails and measuring the engagement of the receivers.In addition to this, a website will also help new users find your app easier through search engines. By picking out a good domain name, writing content, and implementing SEO best practices, you'll rank high in searches for your desired keywords. This is a laborious task, but it pays dividends in time if you're consistent and you do it properly.The good news is that you don't have to pay a development team for implementing your website if you're not technical, there are a lot of services that you can use for a small fee or even free of charge for building your website using simple, intuitive tools. Two of the most popular such services are Wix and WordPress.Social NetworksIf you have done you're job right as a founder you should be able to pinpoint your target audience with laser precision and that will help you get new customers.Almost everyone in modern societies spends at least a few minutes a day on a social media platform, those are proving to be super effective at attracting new customers. An easy way of attracting new customers on social media is using social media ads, however, those don't come cheap and there are still a lot of things to be done without spending a penny.Firstly, you need to define where your target audience spends most of their time when online, for instance, if you have a mobile app that offers fashion advice, you might find that a lot of your potential customers spend a lot of time on Instagram.You should create social profiles for your app on all the major platforms such as Instagram, Facebook, Twitter and interacting with people and communities that share interests that are associated with your app. This is again a slow process, but given enough time, you'll start building a community around your product, if you fail to do that, maybe your product hasn't yet achieved product-market fit and you need to work a bit more on its core idea.A much faster way of getting fast feedback or customers of your new app is posting it on discussion boards such as Reddit in /subreddits where your target audience spends time in. If we're thinking about the same fashion advice app, you could promote it in a couple of the many fashion subreddits such as r/malefashionadvice,r/streetwear, r/femalefashionadvice, r/sneakers, and so on. You could also validate your product idea and get some feedback on its current implementation in entrepreneurial subreddits such as r/Entrepreneur, r/startups, r/growmybusiness,r/ladybusiness.Another super effective and fast way of reaching customers and getting feedback is by posting about your app on platforms such as ProductHunt or IndieHackers. A well-made post on ProductHunt, with eye candy marketing materials and a well-delivered pitch, would ensure a few dozens if not hundreds of new customers over a short period of time (around 24 hours). In addition to this, the communities around those platforms are really helpful and they will surface many things that could be improved for your product.There are also discussion boards such as HackerNews or technology websites such as TechCrunch, but unless your app already has some traction and it does something completely revolutionary, you're going to have a hard time getting to the front page in there.If your product is helping people achieve a certain task or improves the process of doing one, for instance, an app that would help you pick the best items from your wardrobe for a specific event, you could answer questions about that specific task on sites like Quora and promote your product.The number one rule on using social media for advertising is: don't spam! Nobody wants to read or see ads, so if you're posting content you should make sure that the content alone provides valuable information and you should not try too hard to sell your app.Using social sites for getting new customers is a difficult process that takes a lot of time. There are shortcuts like making a post on ProductHunt or posting into a subreddit but those usually are short-lived and will give you a nice bump in the number of downloads for 24 hours, but they can not be used as a funnel for new customers. For the rest of the methods presented, the results don't come back as easily, however, they can represent a constant funnel of new users if done properly.Conference / MeetupsWhen you first launch a new product, the focus should be on gathering as much feedback as possible and adjusting your approach to find the product-market fit. The best way to gather feedback is by talking with the customers and seeing their reactions when they test your product.Conferences and meetups are great places for meeting tech-savvy people, early adopters, and entrepreneurs who can give you insights on how to make the product better. A good place for findings gatherings is meetup. In addition to this, you should also participate in tech conferences that have some focus on the area of your product, or even enter a startup contest and present your idea in front of large audiences. An example of such a conference is Techsylvania an event that takes place every year in our hometown Cluj - Napoca. In addition to advice and interacting with people that have similar interests the startup competition could give you international recognition and even funding if that's something you're searching for.There is no easy way of getting customers to try your product for free, at least not in the early stages, the entire process is difficult and time-consuming. However, it can be made much simpler by knowing who your target audience is and how to reach them, that why we recommend all our founders to do a Digital Product Discovery Workshop before diving into implementing and working on their idea.If you're thinking about building a digital product and you're searching for someone that could build it and guide you through the process of building a mobile startup, we'd love to help, get in touch! --- ### How much of your tech business should you outsource? URL: https://appssemble.com/blog/how-much-of-your-tech-business-should-you-outsource We dive into details and analyze what are the downsides of outsourcing software and product development. We live in an era of innovation and possibilities. When you read tech news, all the success stories about startups, inspire you to build your own. But creating your own tech business that lasts, is not easy, sometimes you get stuck, or lack the time, energy, and capabilities to develop, so it’s fairly common for your business to find itself in the need of extra help. Improving your efforts by outsourcing is often the best solution for these obstacles. If you focus on the bright side of entrepreneurship, you can learn how to prevent falling.The Digital Europe Programme (DEP) began in January 2021, intending to improve the European Union’s strategic digital capabilities and facilitate the cross-sector integration of digital technology. Cluj, a growing Eastern European innovation center, participates in this phase through its local Digital Innovation Hubs, a well established IT and software development hub, by embarking in the process of stimulating investments in Artificial Intelligence, Supercomputing, Advance Digital Skills, Cybersecurity, and supporting the necessity of digital technologies in social and economic domains. Check more on Softech’s article, Cluj: Emerging Innovation Hub For 2021–2027. Now let’s talk about outsourcing.What exactly does outsourcing mean for your tech business and how does it work?Let’s start at the beginning and define what Outsourcing — sometimes called Contracting — means. Outsourcing is a business strategy in which a firm employs a third party to conduct activities, manage processes, or deliver services on its behalf. The outside firm, known as the service manager or third-party contractor, arranges for its staff or programs to execute the activities or services either on-site at the contracting company’s premises or remote locations.So, if you want to build an app you can use an outsourced product developmentwhere you can either hire a programming agency to work on a contract, a freelancer, or another specialized person, all of them hired as a third party. Companies will also outsource a variety of duties or resources. They also outsource information technology resources such as programming, product creation, and technical assistance. They may outsource whole departments, such as their entire IT department, or just portions of a certain department.Examples of mobile app development outsourcingFor just one search on the web, you can find so many outsourced products created by multiple companies. We recommend you start with some from appssemble’s portfolio, where you can check some of the apps on Healthcare, or Fitness, Social, Education, Cryptocurrencies, Gaming, Transportation, or others. With over 10 years of experience behind us, big corporations and startups trust us for our agility, knowledge, and guidance in helping them achieve their goals and building their products, as proof of all the positive reviews on Clutch.What are the benefits of outsourcing your app developmentOutsourcing is often the best option for businesses when developing a digital product such as a mobile app for several reasons. As opposed to recruiting all of the talent involved to fully create a new product from the ground up, hiring an established, committed agency is typically often less expensive. Furthermore, businesses with many products under their belt understand that there is much more to developing a solid product than just writing code.Let’s see what are the benefits of outsourcing your app development:Cost-effectiveness — Outsourcing your mobile app development will significantly reduce your overall costs. It will not only help you save money on overhead costs, but it will also help you save them on infrastructure and services. According to stats, outsourcing mobile app development will help you save up to 75% on costs. Outsourcing is now used by 59 percent of companies for cost-cutting purposes. Seems a very good reason for me.Time-effectiveness — If an app concept has been developed and the company is preparing to launch, time is short. There is no such thing as an original idea because someone will still be there to beat a slow-moving organization to the line. Outsourcing significantly decreases the time constraint and one of the most important principles is timely delivery. The less time spent in development, the easier it is for a company to achieve long-term success. Speedy turnarounds are often advantageous to all parties involved.Enhanced performance — When looking for an outsourced team, look for a professional, who can handle all of your requirements and progress. At appssemble we have everything needed to develop and give you a smooth, high-end mobile app. We have everything we need to produce excellent quality work, from a committed team of developers to cutting-edge equipment. So be sure to hire a good one for a quality result.End-to-end assistance — Before a smartphone app can be launched onto the market, a series of measures must be performed. Some factors are addressed as the best software production firms are hired on an outsourced basis. A customer that requires assistance with conceptualization gets the needed suggestions and insights. The same is valid with clients who need assistance with back-end testing. Outsourcing also gives a company access to sales statistics that they would not have been able to find otherwise.Flexibility — A true startup is defined by its flexibility, agility, and confidence in scaling a creative business model. Being a startup means ensuring a stable workflow through difficult times — adapting the team to meet urgent market demands whilst staying focused on the key plan and core activities. This can occur before the launch of a product, when new ideas must be introduced rapidly, or when a startup is expanding its sector and improving its development. In other words, startups should accept stability to pivot as required without collapsing.Hiring top-tier experts — Professionalism is everything in the field of software production now that there is a far higher degree of competition. Outsourcing enables a customer to increase their degree of expertise without making any other unneeded compromises. It is important to enlist those with the most expertise in a specific niche. This is how some of the most obvious errors can be prevented entirely. Outsourcing firms have already gone through it all and have seen much more. These businesses also take pride in being up to date on the new trends. They would never let themselves slip off the curve. It is important to stay up with industry trends, and this is where outsourcing firms excel.If you’re captivated, you should check Forbes’ — 11 Signs A Company Should Outsource IT — article, and if that one keeps you engaged, also check Why The Pandemic Led To An Increase In IT Outsourcing. Moving along, yeah, you’re better off working with a full-service digital-product firm that will assist you with everything from optimizing brand strategies to planning and improving the product, promotion, and continuing support. And even if you did not come to us in the first place, we will always assist you in filling in the gaps where appropriate. When done right, expanding the work with outsourcing should feel natural — auxiliary agencies should be an extension of your team rather than a piece you’re trying to bring into position.So here are some ways you can use us to compliment your work:Mobile strategy — If the product is nearing completion or is already on the shelf, you can need extra testing from a concentrated, independent test team. This would allow for more candid input on the app’s architecture and service, exposing implementation strategies.UX/UI design — The design of the user interface has a significant impact on how the underlying program is coded since it defines how components behave during user interaction. Often a certain “style” does not translate well in terms of intended features. We will make things more development-friendly by assisting you in rethinking aspects of the concept, resulting in a better product.On-time consultancy — When deadlines are approaching and you already have the right team in place, you will simply need additional eyes or hands in the game. We could appoint the correct guy from our workforce to work with the current team to enhance your efforts to ensure you don’t miss your deadline.Product management — You may have all of the necessary talent and tools to complete a project but are unsure how to continue. And here is where outsourcing product managers (PMs) come in — these people are in charge of managing materials and assigning roles to members of the team and other outside parties, as well as initiating strategies and sustaining progress once a project is underway.Development & testing — In a scrum-based Agile manner, our development and quality assurance teams code and test the app according to the agreed designs. You will receive builds every two weeks for tracking the process, gathering feedback, and adjusting features.Regardless of how daunting such challenges are, startups have a strong chance of overcoming them. Outsourcing is the solution to all of a new entrepreneur’s issues. Even if this is your first project, you don’t have to make any beginner’s mistakes by yourself. But how do you stop making these mistakes in your play if you don’t have any experience? The simplest solution is to seek out a technical partner.What are the downsides of outsourcing your tech part of the startup?Problems also occur when companies do not often recognize all of the different skill sets that must be brought together to complete a project. As a consequence, we encounter cases in which an internal team or an outside firm requires extra assistance when they are missing certain puzzle pieces. Often, these departments do not need to be replaced; rather, they need to be augmented with the best talent. So, here are the disadvantages of outsourcing:You lose some control — And one would imagine, when you outsource work to a third-party company or freelancer, you lose control of how those projects are managed and accomplished. That shouldn’t be a problem as long as you know and trust the people you’ve recruited — but you must proceed cautiously.Hidden costs — While outsourcing is usually thought to be less expensive, you must still be wary of being taken advantage of. Outsourcing firms or large agencies will usually expect small business owners to sign lengthy contractual arrangements including a lot of fine print. If you do not carefully read the terms, you will be faced with unforeseen costs.Security risks — In this day and age of data security, you must use consumer data with caution. If you want to outsource processes that include personal data, you could jeopardize the privacy of others or the security of your company by disclosing that information to others.Reduced quality control — Money, rather than a job well done, can empower outsourcing companies and some freelancers. This means that whilst the job you send out may be returned easily, it will fall short of the value and quality that consumers have come to expect from the product and service they paid for.Different time zones — One significant drawback to outsourcing specific assignments is the risk that the freelancers or partner entity will be set in a different time zone than you. As a result, it can be challenging to synchronize plans to ensure that the client achieves what they are expected, in a reasonable timeline.Details lost in translation — It doesn’t matter if you’re working with foreign freelancers or a brilliant specialist right down the street. If you’re delivering remote work by email or phone, essential instructions are frequently lost in translation. That could cost you a lot of time, money, and hassle.Even though we may not have been your first pick, that doesn’t mean we can’t hop in to help your project get to the end of the race. When you start a project, there are indeed a variety of problems that may arise, and supplementing your efforts with an extra hand is the best course of action. Contact us right away and we’ll work with you to find a plan and get the project moving! --- ### How to build a mobile app on a budget URL: https://appssemble.com/blog/how-to-build-a-mobile-app-on-a-budget Find out what can you do to cut costs when building a mobile app MVP Building a mobile app is an expensive endeavor, while the overall costs are still high, there are some things you can do to lower the cost of your product. Before spending any money on developing the product, you need to plan everything thoroughly and make sure that your app idea is good, that you have a valid business plan and there is a need for the product you want to build, the best way to do that is trough a Product Discovery workshopThe first iteration of your product should be an MVP. The purpose of the MVP is to gather feedback, to test if your idea is valid, to check if there is a market for your product, to gain insights into how the people are using your product, how can be improved, and whats their general feeling about your app. To do this, you don't need to implement all the whistles and bells, you don't need a complex payment mechanism, or in-app purchases, as all of those will be in vain if no one is using your product.Single platformOur number one recommendation for someone who builds a new mobile product is to target only one platform. There are only extremely rare cases where both platforms are needed for testing the idea and building a mobile product for both platforms in the early stages is not cheap -- as you'll have to pay for 2 separate pieces of software, neither is fast as more design and development time is needed. Instagram and Foursquare were both iOS-only apps in the beginning, after they've reached product-market fit they build Android versions as well. Another successful mobile product built for only one platform is Clubhouse.FeaturesMVC is short for Minimum Viable Product, the first version of your mobile product should only contain the core feature of the idea you want to test. A good example is Shazam, when they started out the MVP only contained one feature, determining the name of a song based on a recording, later after they've validated their idea, they've built all the other social features, charts, notifications, and so on. Having a slim feature set for the MVP allows the founders to pivot their idea and implement different approaches once they get feedback from their users. A complex, feature-full product is a few orders of magnitude more expensive to build, more complex to change, and stiff to adding or modifying features.Among the features you can easily skip in the first version of your mobile product in most cases are:Push notifications & deep linking — this introduces extra complexity in the codebase and introduces new complex scenarios to handle. If you're keen on implementing push notifications, you can do it without deep linking. Push notifications will keep the users more engaged and they work great at reminding the users of your app however, before doing that you need to make sure that you have a user base to send those messages to, and in 95% of the cases push notifications are not helping you build your user base.Login with social platforms or complex authentication flows — Nowadays is much cheaper and faster to log in with your phone number or using Apple Sign In, or Google. Integrating multiple sign-in options such as Facebook, Google, LinkedIn, Twitter, Apple Sign In, is not a cheap task. When building an MVP, you should not hinder the experience of the user in any way, creating an account before trying out an app something that the new users don't want to do, so if you can use a fast login mechanism such as a phone number, or no login process at all, the experience of your early adopters is better and you have lower development costs, win-win.Unit tests & automated testing — Doing unit testing and automated tests will assure that the product you're delivering does what it supposed to do, however, in the case of startups where the entire product roadmap and feature specs are more flexible and in 99% of cases changes, it's better to stick to traditional ways of testing the app -- manual testing. Unit tests and automated testing takes quite a bit of time to implement and while it's super effective for mature products, for an MVP is usually not needed.DesignThe MVP should take advantage of as many out-of-the-box design components as possible. For instance, if your app requires a date picker, use the default one, and don't spend resources on implementing a custom design on secondary components. Both Instagram and Whatsapp have a lot of UI components that are native or close to native ones, and both applications are highly popular. When developing an MVP, you should pay more attention to the user flows than to the design, offering a fast and easy way of achieving a task is more valuable to your early adopters than a fancy UI animation or illustrations.By using native components you'll save a lot of money on the design phase but also on the development phase, as native components are much easier to implement and use than implementing complex ones. For instance, if a developer needs o use a native date picker, he could implement it in the app in a couple of hours, if he needs to build it from scratch, it might take even weeks to get all the animations right.DevelopmentIf you're not a developer then you'll most probably need someone to build the app for you. You could either hire an in-house developer, contract a freelancer or work with a development agency.For most founders hiring an in-house developer is not a viable choice as they don't yet have a proven business model and they might end up in a situation where they are not able to pay the hired person or simply don't have enough work for a full-time developer.Your best options are using a freelancer or a specialized agency. Finding a developer who would deliver on time and implement so that it can support the roadmap of your product is not an easy task. Trustworthy specialized agencies have previously built mobile applications, they can offer you insights and guidance and usually have end-to-end capabilities in house, so if you need a new design, a logo change, or help with the marketing, you don't have to search for new freelancer.Even if the agencies might charge more than a freelancer, you're guaranteed that you'll get your product in time, tested, and built by someone who has done this before and fully understands the lifecycle of a mobile product. In addition to this, agencies specialized in building mobile products will offer you consultancy and guide you through the entire process of building, releasing, and marketing a mobile app.Do you have a mobile app idea? Awesome! We’re here to help with the restWe understand what a challenge it is to be a first-time tech founder. It’s pretty difficult to pitch, design, develop and market your idea. Not to mention how hard it is to prove you’ll succeed in a very competitive industry.appssemble is here to be your bold digital product development partner! This service is the cheapest way to start your startup. What will we do? We'll help you define your product, understand its technical feasibility and costs, then validate it. You’ll receive all the tools and information you need to pitch to investors or develop your next products. Come up with the idea and we’ll help you with the rest! --- ### How to avoid a bad mobile development agency for your mobile app? URL: https://appssemble.com/blog/how-to-avoid-a-bad-mobile-development-agency-for-your-mobile-app We cover all the important factors you need to consider before choosing the technological partner for your product. Are you considering building a mobile app for your startup? Then most likely you already know that it’s not an easy job and that’s why you’re here now, to learn. Picking the perfect Mobile Development partner for your journey is one of the most important decisions in your app’s life and course.appssemble, as a mobile development company itself, encountered plenty of situations and experience in this field, so we’ll enhance the next several points about how to, both beneficially assess and select exactly what’s best for your app, and be aware of the general mistakes that are usually made in the process. Let’s dig in!General advice for your StartupAccording to Forbes’s article, there Are Now 8.9 Million mobile apps on this planet. So you want yours to succeed? Well, here are several tips.Take your timeDon’t jump into a collaboration. Instead, take your time and examine any potential agency thoroughly, taking into account their experience with your app concept. Check numerous agencies, their services, and then get in touch with them and set a meeting.Be sure your app concept remains safeAs extravagant as it may sound, try not to put your idea out there without an assurance that it’ll remain confidential. Imagine planning your app idea, investing time, energy, and other resources into it, only to have someone steal it from you. Therefore suggest and then use a non-disclosure agreement with confidence.“Investigate” their portfolioLook for their previous development projects, search for client reviews, maybe even get in touch with a previous customer. The point is to look if they delivered a product of quality, if they communicated effectively with the client, if they respected the deadlines, gave the client the source code, and so on.Search for Mobile Development Agencies with a background and an approach that matches your plan and visionYes, it’s obvious that you’ll be looking for someone who offers what you're searching for, but nevertheless, it’s very easy to get lost in details and lose track, hence choosing the wrong partner to work with. So be sure to search for someone who, during those challenging creations-issues moments, will most likely know how to address and resolve them. It’ll be a spare of time and a magnification of the product’s quality. Therefore, it’s important for you to know how the development agency works and how they will collaborate with you. The process is everything, so find out if their teams’ process will make your app truly unique.General mistakes clients make when going for an outsource mobile development agencySo given our previous information, here are summarized, several errors mobile development agencies make, alongside some made by the customers. We’ll present next all the details so you can be more aware from now on and actually end up with the best results.1. Choosing Price over QualityOne of the biggest traps that people fall into sooner or later is a false notion that cheap work equals a possible quality result. Even though a low-cost company may not always be a bad one, we can assure you that most of the high-priced ones deserve their revenue based on their experience.2. Failing to check their portfolioRemember what we’ve told you a few lines above about checking their work? You should definitely do that! Don’t hire the first company that comes your way, instead, you need to do a background check, verify their experience, their knowledge of the market, look at their rate of success, all these criteria because with experience comes accountability and security. So go over their previous work to check if they are capable of successfully building your mobile app.3. Failure to communicateNeedless to say that if both you and the agency that you eventually hire, are not on the same page, the result will be faulty. Imagine asking them questions about the product and them replying with a big delay, or them contacting you and you responding very late. You can already visualize the outcome. Outsourcing mobile app development works through plenty of people, that’s why it’s extremely important to maintain clear communication between each other from the beginning.4. Failure to set deadlinesChoose a timeframe that suits both of you, that’s realistic, practical, and fair, then communicate it clearly. This act will make things run smoothly and allow everyone to work within the timeline. If you’re working with someone from abroad, you also need to take into consideration the gap in different time zones. It might not seem like an important detail at first, but imagine needing to honor a deadline that’s doomed to overpass due to the difference in time zones. So be careful!5. Failure to get the source codeThe source code is created by the mobile app development agency but you need to own it too after the whole project is done. If you fail to do so, you’ll constantly have to go back to the agency and negotiate, financially most likely, every update or edit you want to make on your app. Wouldn’t that be extremely unfair and annoying for you? Just make sure to obtain that source code!Why mobile application development project actually fails?Over 1.000 mobile apps are uploaded daily to the Apple App Store and 9 out of 10 fail. So what could make your app unsuccessful and fail? Here are several reasons:Process failures — the app doesn’t get past the design stage and it’s never coded into an actual app; the app requires a re-design after coding has started; it requires a re-coding after the app was launchedDesign and development failures — the app has poor user ratings after launching; technical difficulties make it undesirable as wellNot honoring deadlines and budgets — the app goes over the settled budget and/or deadlines.How to actually find a mobile app developer?There are several options when building an app. These are the following ones: if you’re a company, you can hire an employee on your payroll as in-house product development, or use an outsourced product development where you can either hire a programming agency to work on a contract, a freelancer, or another specialized person, the last 3 options being hired as a third-party.In-house product development vs. Outsourced product developmentIn-house refers to conducting an activity or operation within a company, instead of relying on outsourcing. A firm uses its own employees and time to keep a division or business activity, in-house.The main advantages and disadvantages when using an in-house activity are the following:The essential advantages are, complete control over product commitment and delivery since you can use your whole team to work at full power in the same direction, this leading us to another possible advantage, namely the capability to perfect yourself to differentiate from the competition.The main disadvantages are the indispensable need to possess good management and organizing skills because of the struggle to unfailingly balance an inconsistent income for your rent, for employees with different salaries, and other weekly/monthly costs, and lastly an overwhelming and time-consuming process of managing the company.If you’re here as a developer yourself, you should definitely check Forbes’ “13 Mistakes To Avoid When Developing An App”, it has some very specific and proper points for you to follow.Outsourced product development (OPD) is a practice in which an organization hires a third-party provider for the development of products and services in a variety of fields , and even idea generation. OPD success depends on finely integrated strategic planning, communication, collaboration, management, and specialized resources.Contract Developer vs. Freelance DeveloperAs I said a little bit earlier, there are 3 main roads to outsourcing your development, specifically, a contractual development agency, a freelance developer or simply hiring a specific person who possesses the skills you require for the job.Choosing an additional person with the required skillsetStarting with the last one on the list, this decision applies to the companies that lack a specific item in their project, like development, design, or management. Therefore they contractually hire someone with the required skillset for the job, to take care of that specific part of the project.Choosing a Contractual Development AgencyA development company has its own staff who will take care of everything you require and will bring you the app in its final form. Although it may be more expensive than a freelancer, the chances of your project going south are exponentially lower because they vouch with their experience, therefore their capabilities. So the whole project is actually very straightforward with them.Choosing a Freelance DeveloperChoosing a freelancer works if you are willing and able to get involved as well. You need to know exactly what kind of help you need for your project and constantly manage and direct the one you hire. Their possible lack of experience will make them turn back to you for every problem they’ll have. So, overall it will be a time-consuming procedure where you’ll have to constantly stay in touch and oversee their own development on the project. Not to mention you need to pay close attention when hiring them, on their aptitudes, their programming skills, negotiate a contract, make an offer, and a detailed plan about your app’s idea. If you don’t possess the time and capability to supervise them, the whole freelancer idea might not be very suitable for you.We build outstanding apps with professionalismYou can consider yourself informed now and capable of making the best decision for your star up, and by extension for your mobile app. Our professional, experienced and dedicated team at appssemble will help you in this journey from start to finish, to discover what you desire, develop and design your product. So get in touch with us and let us build you the app that you’ve been thinking of. --- ### The ultimate guide to developing an Android app in 2021 URL: https://appssemble.com/blog/the-ultimate-guide-to-developing-an-android-app-in-2021 Read our breakdown of the new technologies from Google and learn more about what's currently possible in an Android app. You're thinking about building an Android app but you're not technology-savvy? No problem, we'll walk you through the ins and outs of mobile Android development for startups.When deciding to build an app, the focus should be on its core functionality, not necessarily the technologies used for building it, so let's look at the things Android as a development platform excels from a feature-wise perspective.Machine learningAndroid provides all the tools you need for developing ML features in your app, from building and training your machine learning models to deployment as app features. Using ML techniques will help you automate many processes of your app or business which will drive down your recurrent costs. Some examples of ML features that Android supports and would bring great value to your startup are text recognition (OCR), face detection, barcode scanning, image labeling, object detection, and object tracking, language identification, smart replies, or translation. Although the whole machine learning framework is pretty new on Android it is robust enough to start deploying ML features in your app which will also become better and better with every framework improvement.Augmented RealityAR is still a new field and many startups ignore or are not aware of the value AR could bring them, or even when they take AR into account we get many questions about what is possible on Android when it comes to Augmented reality. The answer to this really depends on your needs and requirements because AR is highly dependent on the hardware it runs, but with the adoption of new devices, the gap closes quickly. There are two big directions an AR project can take, using Unity or ARCore, both have their advantages and disadvantages. The real power of AR is more obvious when it is combined with machine learning. Without getting into too much detail, AR + ML could help you place virtual objects into the real world, detect real-world objects like balls in sports, human body position and movement, and taking measurements of the real world. This could really take your app to the next level and make friction-free user stories for your app.Instant appsOne of the latest technologies introduced by Apple is App Clips, which offers users the possibility of interact with an app before downloading it. It's a great way for startups that operate in the physical world to interact with their customers. For instance, restaurants or mobility startups could offer functionalities such as renting a car or ordering a food dish without needing to download an app for that. App Clips are also great for ticketing or offering information at an event or conference, as the user won't have to download an app to consume or consult digital content but they will able to do it in a user-friendly manner, just like they would use a native app. Another technology provided by Google that could help you reach a wider audience is Instant Apps. Adding the Instant App feature will allow your users to try your app directly from the Google Play store without installing it. This provides a great opportunity to get some exposure to your app and convert potential users to download your app. For instance, restaurants or mobility startups could offer functionalities such as renting a car or ordering a food dish to try and if the user is pleased by your service he will become a recurrent user and download the app. Another use case could be one-time events where downloading the app for a one-time use could seem too much work. The Instant app could provide all the digital content and information needed just like a native app but without the friction that an app install brings.eSimThis technology got more and more adoption lately and became a really convenient way for users to buy better mobile plans, especially when traveling abroad directly from an app without having to switch their sim cards. The use of eSim however is not limited to just this, with the development of wearable devices eSim allows to use of the same phone number on multiple devices or have multiple phone numbers and mobile plans on the same device. Like Revolut changed the traditional way of using your card giving you more control over your finances, eSim allows you to do the same thing for mobile plans.Android TV, wearables, and smart devicesThe Android development is not limited to just smartphones nowadays, there are a lot of opportunities outside of the smartphone world. Google tries to build a whole ecosystem with Android being the infrastructure for this. Whether your startup is focused on streaming, well-being, sports, or smart devices, it will be a huge advantage to have your apps running on multiple types of devices. Because these markets are not as mature as the smartphones market the entry bar is lower and there is more place for growth as the user adoption of these new devices grows.Tech stackIf you’re reading this, then most probably you already know what you’re trying to build, however, we hope the above-mentioned technologies got you excited and made you think about how you can build an even better product. Let’s now talk a bit about what’s a mobile app made of and how is it made.At appssemble, we only do native development because it allows us to use the latest and shiniest tools from Android and gives us full control over the development of the product so we can ensure a high-quality standard for all the products that we build.What's a tech stack you ask? A tech stack is a set of tools and technologies used for building a certain kind of product. As an analogy to cooking, if an Android application would be an apple pie then the tech stack would be the ingredients that are required for cooking a pie (flour, sugar, butter, apples, etc.). Our job when developing an app is similar to what a cook does, it picks the best ingredients (tech stack) and with it does its magic to create delicious dishes (in our case, mobile apps).At the basis of every tech stack, we have the programming languages used, for developing a native Android application we can use:Kotlin — Google added support for Kotlin in Android in 2017 and it already became the standard language for developing Android native apps. It is part of the modern programming languages with a focus on more concise syntax, better error checking, security, and performance. It is fully interoperable with Java which allows to easily migrate older Java Android apps to Kotlin easily. Picking Kotlin will also reduce the development time and will make the project easier to maintain in a long time.Java — is probably the most popular programming language. It is an object-oriented programming language first released in 1995 and became used because code written in Java worked across many devices. There are a lot of libraries still built in Java for Android for new projects it is not the first choice anymore.One of the most important things about a mobile app is how does it look like. Android offers us, developers, great tools for building the user interfaces and the user interactions:Android XML — the traditional way of building user interfaces on Android is declaring UI components in XML files. This is a mature framework and comes with all the tools and support needed to build rich and complex user interfaces on Android. New user interface components were added over time which made building new UIs increasingly easier.Material design — if you are an Android user you definitely saw material design in action many times. It is a set of guidelines and resources developed by Google with the intent to standardize how the apps look on Android. While we can choose to follow or not these guides, following them would make the app seem familiar, make the user more conformable using it and visually it will feel better integrated with other apps.Jetpack compose — is a completely new, modern toolkit introduced by Google in 2019 for building user interfaces and user interactions. It is not compatible with the traditional XML way of building the UI and being new there are some limitations when using it feature-wise, but also regarding the support and tools available for it. We would not advise starting a big project with jetpack compose but for some proof of concepts, it could be a right fit.OpenGL — is the standard on Android when it comes to rendering complex 2D or 3D scenes in graphic processing or graphic-intense apps such as games or simulators. OpenGL is well established and well documented in the industry with over 28 years since it was launched.The vast majority of apps need some data for them to function, that data can be anything, from user details, friends list, to recipes or images. But where do they come from or where do they reside?APIs / Third-party services — mmost of the apps have a backend server or a service somewhere that handles the data needed for the app. They store and manipulate app-specific entities such as user details, accounts, passwords, balances, photos, etc. For an app to be able to use an external, third-party server, it needs to be connected to a network, so the app won’t function without an active internet connection.What if your app doesn’t really need a server or a backend solution to store all the data? What if your app just needs to use some existing services and store some user data? In that case, there are a number of solutions that allow storing small or large sets of data locally in a performant and secure fashion.DataStore — is part of the new Android Jetpack library and it comes as a modern way of storing on the phone small sets of data, replacing the old SharedPreferences way of doing it. The integration in both new and existing apps is easy and the syntax is simple and concise. Performance is also outstanding when storing and retrieving data from the DataStore.Room — unlike DataStore, Room is a real database. It really shines when working with large amounts of data. If your app needs to work with hundreds of thousands of data points and still feels fast and snappy Room is the right tool to use for storing the data. Room can also be used as a caching system for your app, where a synchronization mechanism will keep your local data in sync with the data on your server. An example of an app that could take advantage of Room would be a navigation app for hikers, as they could easily lose their internet connections.Now that we've talked about technologies, and how to build an app, it's important to also talk about how a mobile app can be tested.Manually — not specific to Android but still one of the most common ways of testing an app is through manual tests. When manually testing an app QA cannot only check the functionality of a feature but can also check how it integrates with other features, if the design is consistent, or if the app handles well all the corner cases — such as receiving a phone call when doing a certain task. They can also validate more accurately the performance and the user of the app on different types of devices with different screen and hardware configurations.JUnit — is the Android unit testing framework that can be used to test the logic of an app. Using JUnit you can write test cases to test both the happy flow logic but also the corner cases. Basically, every Android project comes with JUnit already integrated it is up to the developers to write test cases that test their logic. It also provides a way to integrate instrumentation in the unit tests, to be able to test the performance alongside the correctness of the code.Espresso — is the Android UI testing framework that provides all the tools to write and run UI test cases. It also provides a way to record the actual test cases such that after manually testing once the app espresso can run that test again as many times as needed. This helps identify regressed issues and also reduces the need for manual testing and human error significantly.All of the above-enunciated technologies from Android can be used for developing mobile apps through the Android Studio, the IDE (Integrated Development Environment), offered by Android freely for software development.As we’ve seen, Android is a mature environment that gives developers who want to build apps a rich ecosystem of tools and technologies for development and offers a lot of innovative technologies for the next generation of mobile apps.Are you going to build a native Android app in 2021? We are masters when it comes to Android development. Get in touch and learn more about how can we help you succeed! --- ### How much does it cost to build a mobile app in 2021? URL: https://appssemble.com/blog/how-much-does-it-cost-to-build-a-mobile-app-in-2021 We look at every cost involved in building a mobile app, product definition, development, marketing, and maintenance. When a founder thinks about building an app, his next immediate tough is how much does it cost?The harsh reality is that mobile applications are not cheap, they start from a couple thousand $ and as with almost everything, the sky is the limit. In this article, we'll walk you through the list of costs involved when building an app and help you form a rough idea of the capital you'll need for building an app.Before digging into costs, let's firstly talk a bit about why would you build a mobile app? If you're a founder then probably you want to build an app to build a business around it, or the app is a piece of the puzzle. While indeed the costs of developing an app are high, the rewards, if the app is done properly are worth the time.Since you're here, we are going to assume that you want the app to be developed by an agency and we won't talk about the cost of renting a space for your developers, utility costs, salary, etc., we are going to focus only on the app costs. Let's startProduct StrategyThe first step in building a mobile MVP is deciding what to include in the first iteration and most importantly whom you're addressing with the app. This is a crucial step and under no circumstances do you want to skip this unless you have time and money for some gambling. If you already have a validated idea, if you've talked with customers, gather feedback, and adjusted the feature set accordingly, you might skip this step. Otherwise, you're going to need between $5.000 and $10.000 for this if you're using the help of a specialized agency and the whole process will take around 1 month.Mobile App Design and User TestingThe user experience is one of the most important aspects of developing a mobile app. After all, you're building an app to solve a real problem, and nobody likes clunky solutions. The user experience is not something you get right from the first time, that's why you need to validate your design and user flows with people from your target audience, gather their feedback, and adjust properly. To get this right, you'll need 1 - 1,5 months and between $10.000 - $15.000 for an MVP.Mobile App DevelopmentMost founders want to get to the development phase as early as possible, but this is only a small part of the whole process of building a great mobile app.Abraham Lincoln said, "Give me six hours to chop down a tree and I will spend the first four sharpening the axe.", this is also true for mobile apps where good planning, a validated product strategy, and tested designs will get you there much faster and cheaper than developing and adjusting afterward.We usually spend between 2 to 6 months developing the vast majority of MVPs, a price range for this would be between $40.000 - $150.000.As a rule of thumb, if the whole process takes more than 6 months for getting your MVP to the market, you've probably been introduced to many features and you're taking on a higher risk.Running costsDepending on the functionality of your MVP, you'll have higher or lower running costs. For instance, an app that stores videos and photos from the user will have higher running costs than an app that only manipulates photos or videos locally, as in the first case those would have to be stored on a server somewhere.The running costs are also affected by the technologies used for building the apps, some services can be used freely until you hit several daily users. In addition to this, if the app uses third-party services such as Google Location for instance you'll also need to pay for those.The average running costs of an MVP are between $50 - $250 monthly, however, depending on the number of users and the functionality of the app, those numbers can go high up when you have more users on the platform. In short, the amount you'll pay each month will be directly proportional to the user base your app has, based on the selection of services and technologies, it might even be possible to pay nothing until you acquire a fair amount of users.MarketingYour app is out but is one of the few millions available in the app stores, so you'll need to promote it to get it in front of your audience.There are a lot of ways of promoting an app, App Store advertising, social media advertising, online ads, influencers, etc. DoorDash had around 2900 ads running at a certain point, other apps like Uber or Tinder spend hundreds of millions of dollars so the budget that can be spent here could be unlimited.With MVPs, you're trying to find the product-market fit, and for doing that, you need to gather enough users to gain insightful feedback and to adjust the product accordingly. You should plan for at least $10.000 / month for the initial marketing campaigns.MaintainanceYou've launched the app, congrats! You've marketed it well and users start to use it, but your work just begins. Once the app is out and a large audience is using it, new insightful feedback from the users and details from app analytics comes along and you might need to adjust your product to better fit the needs of the users, or you might need to implement a new feature heavily requested by the users.Fail to do that and you'll slow down the growth of your startup or you'll join the 9 startups from 10 that fail. As a founder, your job should be on learning from the users and adjusting your product until you find product-market fit and stable revenue sources.Depending on the type of assistance needed, help with the analytics, building the roadmap for the future release, or developing new features the cost of maintaining a product can vary between $2.000 to $20.000.So let's sum it up:Product strategy — $5.000 - $10.000 (1 month)Mobile app design and user testing — $10.000 - $15.000 (1 - 1.5 months)Development — $40.000 - $150.000 (2 - 6 months)Running costs — $50 - $250 (monthly)Marketing — $10.000 - $15.000 (monthly)Maintainance — $2.000 - $20.000 (monthly)So for a launched MVP, with all the costs involved for the first month of operation, you would need to pay between $62.050 - $210.250 for a single app on one platform. If a second app (for another platform iOS/Android) needs to be developed, around 75% of the costs for development involved for developing the first one is a good approximation of the costs, so for an MVP for both platforms (iOS and Android), you're looking at a price range between $92.000 - $322.000.If you're looking for a team of mobile experts that would help you take your idea and transform it into a user-validated mobile app, get in touch, we would love to help! --- ### The ultimate guide to developing an iOS app in 2021 URL: https://appssemble.com/blog/the-ultimate-guide-to-developing-an-ios-app-in-2021 We explore the new technologies from Apple and give an overview of what's possible and how can an iOS app be built. You're thinking about building an iOS app but you're not technology-savvy? No problem, we'll walk you through the ins and outs of mobile iOS development for startups.When deciding to build an app, the focus should be on its core functionality, not necessarily the technologies used for building it, so let's look at the things iOS as a development platform excels from a feature-wise perspective.Machine learningiOS is a great platform for developing apps that have ML features. The hardware in the new iPhones is capable of fastly processing large amounts of data and extracting useful information. A new platform comes to every decade and ML on mobile devices has just seen the light of day, there are a lot of unexplored territories and a lot of startups to be built. ML has many implications and has offered a ton of exciting and innovative capabilities that could be integrated into a startup, natural language processing, image recognition, and object tracking are just a few of the things possible. At appssemble, we're experts in ML and AI, and we've even written a summary of what's currently possible in the realm of ML and AI.Augmented RealityThere are no other platforms that are even close to achieving the capabilities offered by iOS to developers for building AR applications. Apple heavily invests in developments in this area and leads the way by a large margin, not only do they offer great technologies for building AR apps, but they also equip their latest models with sensors meant to aid the process of building great AR apps. LiDAR, which was included on the iPhone 12 Pro and iPads, makes the detection of real objects much more precise and blazing fast, which means there are a lot of opportunities for building AR apps. By combining AR with ML, we are technologically capable of achieving exciting things like human pose detection, speed, and trajectory of real moving objects such as golf or basketballs, virtual object placement, and manipulation or accurately measuring real objects.App ClipsOne of the latest technologies introduced by Apple is App Clips, which offers users the possibility of interact with an app before downloading it. It's a great way for startups that operate in the physical world to interact with their customers. For instance, restaurants or mobility startups could offer functionalities such as renting a car or ordering a food dish without needing to download an app for that. App Clips are also great for ticketing or offering information at an event or conference, as the user won't have to download an app to consume or consult digital content but they will able to do it in a user-friendly manner, just like they would use a native app.eSimeSims are not new, however, Apple has opened its doors to apps that could take advantage of those and allow users to lose their carrier and take advantage of new ones with better offers through mobile apps. Apple allows users to install and use eSims as they're pleased, which means is now possible to have different phone numbers every month or to have different plans, based on your needs, the country you're in and what types of services do you use. There are a lot of advances to be made in this sector and there is a huge opportunity for innovation.Cross-platform on macOSIn the latest versions of the iOS SDK, Apple made it super simple to port a mobile app to a macOS one. This means with minimal effort, your iPhone app could also run on desktops and laptops. Previously, macOS developers were pretty hard to find and expensive, as not a lot of macOS apps are being built nowadays, however by porting your iOS app to macOS, you can reach more customers. If you're thinking about building an app that could be useful in a macOS context, such as photos or video manipulation, watching content, or even e-commerce, you could reach a lot of customers. If you wish to be a top-charting app in the App Store without spending a fortune on marketing, this is possible in the macOS store.Tech stackIf you're reading this, then most probably you already know what you're trying to build, however, we hope the above-mentioned technologies got you excited and made you think about how you can build an even better product. Let's now talk a bit about what's a mobile app made of and how is it made.At appssemble, we only do native development because it allows us to use the latest and shiniest tools from Apple, but more importantly, because is the only approved way (by Apple) for building those kinds of software products. So let's look a bit at the tech stack used for building those apps.What's a tech stack you ask? A tech stack is a set of tools and technologies used for building a certain kind of product. As an analogy to cooking, if an iOS application would be an apple pie (pun intended) then the tech stack would be the ingredients that are required for cooking a pie (flour, sugar, butter, apples, etc.). Our job when developing an app is similar to what a cook does, it picks the best ingredients (tech stack) and with it does its magic to create delicious dishes (in our case, mobile apps).At the basis of every tech stack, we have the programming languages used, for developing a native iOS application we can use:Swift — a powerful and robust language developed by Apple in 2014, that was developed with the ideas of security, performance, and fewer bugs in mind. It forces the developers to write code in a way that makes it harder to introduce bugs while developing features of the apps. This is our weapon of choice as it allows us to built more sturdy apps and do it fast.Objective C — developed 30 years before Swift, ObjC is an object-oriented programming language from the days of Apple's beginnings. It offers great flexibility and is great for building apps that should interact with low-level functionalities or C/C++ libraries as it offers excellent interoperability.One of the most important things about a mobile app is how does it look like. Apple offers us, developers, great tools for building the user interfaces and the user interactions:UIKit — is the oldest UI framework in the iOS SDK all the native apps built till 2019 (that were not games) were using it. It allows developers to interact, build and handle all types of user events and to build complex interfaces. Apples have made working with UIKit fast and pleasant by offering developers tools to build UI interfaces graphically. This is by far the most used UI framework on Apple's platform and the one we recommend for the vast majority of apps.SwiftUI — is a new UI framework from Apple, introduced in 2019, its a completely new system for building user interfaces and user interactions. SwiftUI is still rather new, and there are a lot of things that are currently not possible, we would not advise exclusively using it into a new app just yet.Metal — is a framework used for graphic processing or graphic-intense apps such as FinalCut or 3D games. By using Metal, the developers gain access to tools that can interact directly with the GPU in mobile devices and tools for video and image processing.The vast majority of apps need some data for them to function, that data can be anything, from user details, friends list, to recipes or images. But where do they come from or where do they reside?APIs / Third-party services — most of the apps have a backend server or a service somewhere that handles the data needed for the app. They store and manipulate app-specific entities such as user details, accounts, passwords, balances, photos, etc.. For an app to be able to use an external, third-party server, it needs to be connected to a network, so the app won't function without an active internet connection.CoreData — what if you don't want to use a third-party service, and your app just needs data from the user? That's exactly what CoreData is for, it's a local data storage that can store your app's data (photos, videos, text, or other app-specific data). CoreData is also used occasionally as a caching mechanism for the third-part services. If an app only uses the information available on the device, it means it can run without an internet connection. An example of an app that could take advantage of CoreData would be a navigation app for hikers, as they could easily lose their internet connections.CloudKit — sometimes all your app needs is storage, if that's the case and you don't need any complex algorithms on your backend CloudKit is a great choice. It allows developers to fastly build apps in which the users could share data, without the need for a third-party service.Now that we've talked about technologies, and how to build an app, it's important to also talk about how a mobile app can be tested.Manually — not specific to iOS but still one of the most common ways of testing an app is through manual tests. When manually testing an app QA cannot only check the functionality of a feature but can also check how it integrates with other features, if the design is consistent, or if the app handles well all the corner cases -- such as receiving a phone call when doing a certain task. They can also validate more accurately the performance and the user of the app on different types of devices with different screen and hardware configurations.XCTest — is a framework from Apple that allows developers to write unit, integration, UI, and performance tests for their code. It offers a great report of the coverage of the tested code and what can be improved. In addition to other tools or other platforms, it speeds up the UI testing mechanisms by allowing developers to record (like in screen recording) flows that would be repeated and validated when the tests are run.All of the above-enunciated technologies from Apple can be used for developing mobile apps through the Xcode IDE (Integrated Development Environment), also offered by Apple.As we've seen, Apple takes good care of developers who want to build apps for its platforms by offering a rich ecosystem of tools and technologies for development and offers a lot of innovative technologies for the next generation of mobile apps.Are you going to build a native iOS app in 2021? We are masters when it comes to iOS development. Get in touch and learn more about how can we help you succeed! --- ### Why you should do native development instead of cross-platform URL: https://appssemble.com/blog/why-you-should-do-native-development-instead-of-cross-platform Find out more about the differences between cross-platform technologies (ReactNative, Flutter, and Xamarin) and native development, and why you should choose the latter. Should I build a native or a cross-platform mobile app?That's a common question among all the startup founders who want to develop a mobile app, each one of those approaches has its advantages and disadvantages, today we are going to talk about them all and make your decision easier.Cross-platformThere are a lot of cross-platform technologies available that allow building apps for multiple platforms (iOS, Android, Desktop of Web) from a single codebase. Among the most popular ones, we can enumerate React Native, Xamarin, and Flutter, we are going to talk about each one of those as they have certain particularities that we find worthy of mention.React NativeThis is one of the most popular approaches to developing cross-platform mobile apps it uses JavaScript as a programing language and was created by Facebook.React Native works as a mediator between the native iOS and Android platforms, which means that UI components from React Native will be converted to native components by the framework. In simple words, a button from React Native will be translated into a native button on Android, and a native button on iOS.AdvantagesCross-platform — you can build apps for different platforms from the same codebase.A lot of developers — JavaScript is a popular programing language, there is a large number of developers to choose from (a lot of Web developers have started building mobile apps because of this).UI components upgrades — when Apple or Google releases a new version of their mobile OS, usually there are changes to the UI elements since React Native is mapping to native components, you'll get the upgrade instantly.DisadvantagesDeprecated libraries — React Native developers use a lot of obscure libraries which could be deprecated or their maintainer does not update them periodically, which means that sometimes the developers who build the app would have to modify and maintain those libraries.Harder debugging — the way React Native is built makes debugging much harder than for native platforms. In addition to this, when receiving crash logs from the users, those won't be of great value, as they are not mapped to the React Native code from which the app was built.Different looks on iOS vs Android — while mapping React Native components to native ones has advantages, it also has disadvantages, the main one being that you won't have the same pixel-perfect UI on both platforms due to the mapping.XamarinDeveloped by Microsoft Xamarin, uses C# and the .NET framework for building cross-platform Android and iOS apps.Microsoft has its paradigm of developing mobile applications, there is an extra learning curve. For the UI part of an app, Xamarin can use either platform-specific code or Xamarin.Forms which is a cross-platform UI library.AdvantagesCross-platform — you can build apps for different platforms from the same codebase.UI consistency — if using Xamarin.Forms, the UI of the iOS and Android app will look similar, the main difference being on the way navigation from one screen to another is conducted (as there are differences between iOS and Android).DisadvantagesCosts — while Xamarin has a free version with limited features, if you want to take advantage of the full platform, there are licensing costs (around $1.000/year for small businesses at the time of writing).Debugging — Xamarin is known for its bugs as a platform, so when discovering a bug, a developer would have to investigate it on 3 platforms (iOS, Android, and Xamarin).Lack of developers — there aren't too many Xamarin developers available, you'll have a hard time finding one, this is mainly because of Microsoft's paradigm and the associated costs.FlutterOne of the youngest and most promising and popular cross-platform development technologies comes from Google and is called Flutter.Flutter uses Dart as a programing language and allows true cross-platform development (iOS, Android, Web, and Desktop). Flutter has its own engine for the user interface, it uses 2 different design widgets that imitate both iOS and Android's UI components.AdvantagesCross-platform — Flutter allows building apps from the same codebase for multiple platforms, not only mobile, it has support for iOS, Android, Desktop, and Web.Performance — among the cross-platform solution Flutter offers the best performance, as its graphics and visualization engine built into C/C++.Popularity — Flutter is the most popular cross-platform technology according to Github and Stackoverflow questions.DisadvantagesNo free UI upgrades — since Flutter does not map its UI components to native ones when the OS updates and the components are changed, an app developed with Flutter will look the same.Limited support — a lot of libraries and features have limited support, which means there are a lot of native functionalities which can not be used in a Flutter app, when the mobile OS changes, your app won't be able to use all the shiny new things until they are ported to Flutter.Native appsThe only recommended way by both Apple and Google (even that they invest in Flutter) of building mobile apps is using native technologies. On iOS apps can be build using Swift or Objective C as programming languages and while Android supports Kotlin and Java.For building an app that would run on both iOS and Android using native technologies, two codebases are needed, one for iOS and one for Android.AdvantagesPerformance — native apps have far better performance than all the cross-platform approaches as they run directly on top of the OS.Updates — when a new version of the OS is released, a native app will get automatically all the new UI elements without needing to modify the app, and also get access to the latest available APIs and new features of the SDKs (such as improved AR/VR components, access to enhanced security features, etc.).Mature platforms — finding native developers is easy, they usually focus only on mobile development so they have a lot of experience in this particular type of software. Moreover, since both iOS and Android are available for quite some time, there are a lot of open-source libraries, UI components, and tools for making the development process faster.Stability — an app built with native technologies will continue to run on the newer versions of mobile.Advanced tools - — both Apple and Google offer advanced tools for development and debugging.DisadvantagesNot cross-platform — if a company or a founder wants to offer their mobile app on both iOS and Android, it needs to have two separate codebases using different technologies, and libraries.ComparisionThe main reason someone would want to develop an app using cross-platform technologies is the cost. The idea of having a single codebase is appealing to many startup founders, however, we've discovered that going cross-platform does not necessarily mean lower costs.In addition to the already mentioned disadvantages of the cross-platform technologies, they also have some extra ones, such as an increased size of the app(which means it will occupy more space on the phone of the user), and increased complexity as the codebase grows.We've discovered that in cross-platform projects once the codebase starts to grow, and more complex features are added, we would need to write platform-specific code. In addition to this quite often we would also need to write native code, for handling specific cases and APIs. As an example, we needed to write native code for both iOS and Android when we've built a cross-platform app that had an AR/VR component in it, as React Native did not know how to handle the different frameworks used by both platforms.While costs were lower at the beginning of the project, the added complexity made developing new features extremely slow and costly.Cross-platform development is suitable for small applications in which the user interface is not that important, has a limited set of features, and there are no plans for adding more features, for instance, an access app to a conference, or a corporate app that displays company news. Or, for large enterprises which have all their web apps written in React and they can easily transition some of the features on the mobile apps as well.While cross-platform might seem like a good idea and looks good from a cost-wise perspective when starting a new project as compared to native technologies, as time passes and more features are added, new OS versions and SDK appear, cross-platform approaches become more expensive and rigid to adding new features. In addition to this, there is no guarantee that they will work on the next version of the mobile OS, and the user experience they provide is much more inferior to their native counterparts.Besides all the above-mentioned advantages of native development, it is also important to point out that native development tools surpass by far the cross-platform ones. For instance, when designing a native user interface, developers could use tools from Xcode or Android Studio for visually building the UI, which makes the development a lot faster. In addition to this, both development environments offer advanced debugging tools which make finding and fixing a bug much more easily. Furthermore, native platforms also provide out-of-the-box, easy ways of testing the flows or the user interface of the apps.At appssemble, we've decided to build all our apps using native technologies, not only because they are more stable, secure, performant, and run better, but also because it's the only safe, reliable, and approved (by Apple and Google) way of building an app.... and we are not the only ones, Facebook, the company that created React Native, has switched from React Native to native development for their messenger apps, Airbnb has done the same, Udacity as well, and the list could go on and on.We build a lot of mobile apps for startups, and for a startup, it's important to be able to take advantage of the latest SDKs, it's also super important to be able to deliver new functionalities quickly and to be able to build on top of an MVP. We also strong believers that it's important to respect each platform and adjust the user interaction to the platform's guidelines, what works for an Android user might not be that intuitive and user-friendly for an iOS one. After all, a startup needs all the competitive advantage it can get, to attract new customers and turn the existing ones into raving fans, and we believe going native is a major advantage over the cross-platform approaches, from both a user experience as well as from a performance one.As for the costs, in the long run, by doing native development, the costs will be at worst similar, but in the vast majority of cases, the native will be cheaper. A common mistake startup founders make when deciding to go with a cross-platform approach for their MVP, is that they assume that the price for it will be half the price of native apps, this is usually not true, and a more realistic cost would be 75% of the cost of both native apps (as both native apps will use the same backend solution, and most of the business logic is the same, so most of the times is just porting the solution to the other platform).If you're thinking about building an, and we've convinced you that native is the right way to go forward, or if you want to convince us that we're wrong, we would love to hear from you, get in touch and let's talk! --- ### What's the difference between a mobile app POC, Prototype, and an MVP? URL: https://appssemble.com/blog/what-s-the-difference-between-a-mobile-app-poc-prototype-and-an-mvp We go into a detailed explanation of each one of those concepts and how can they help you build your mobile startup. When building new digital products, it's important to match innovation with technical excellence and test the assumptions behind the product often and with the right tools.Proof Of Concepts (POC), Prototypes, and Minimum Viable Products (MVP) are all used to validate the idea of a digital product (mobile app, website, etc.) at different stages.Mobile Proof Of Concepts (POCs)A POC is used when testing the feasibility (technical and integration) of a feature.The purpose of a POC is not only to test the technical feasibility of a feature from a technological point of view but also to show the integration constraints, and to highlight its potential downsides.At appssemble, when we build a POC, we also create a report in which we highlight all the technical, integration, and user experience constraints that we've identified while testing the POCs idea. By doing so, a POC achieves its purpose, that of validating the feasibility of the feature, and presenting all the possible downsides of the approach.Why build a POC?Innovation — POCs are usually built when trying to prove if it's possible to achieve a certain feature using the current technology or the current tech stack. This is especially useful when trying new technologies such as AR/VRIncrease interest — POCs could also help startup founders prove the feasibility of their core feature to a board of investors, or their target customers.Example of a POCWhen building the voicecal app, we had to first test the feasibility of the idea, whether or not could we could use the voice as an input mechanism for calories counting, and if the idea would work in multiple languages. After we've proven our assumption, we've started the development of the app and use all our findings in regards to technology and user experience constraints, to give life to the first version of the app.Mobile PrototypesA POC is used when testing the feasibility (technical and integration) of a feature.A mobile app prototype is used to showcase the user interaction part of the productits purpose is to show how the product will function from a user experience point of view. There are multiple types of prototypes:Paper-based prototypes — this is the simplest form of prototypes, here the focus is on defining and identifying the flows, screens of the app, and the basic interaction between them. This kind of prototype is used in the early stages of a mobile app product, for defining the feature set and the core screens of the app.Wireframes — those types of prototypes are digital and static, they focus on the flows of the app, the types of components used in each screen, and how the flows and screens interact. This type of prototype is usually black and white, it has no colors, images, or illustrations, and it's used for validating the flow of the user in the app and for providing an overview of the functionalities of the app. Wireframes usually contain all the flows and screens of the app and handle the interaction between all flow combinations (what happens if the user has just registered, what should happen if they are trying to make a purchase but have no payment method added, etc.).Interactive / Clickable prototypes — those prototypes are digital and interactive versions of the designs and are high fidelity versions of the end product. Interactive prototypes represent the final UI of the application(images, colors, illustrations) presented interactively -- meaning that the users can interact with certain elements and navigate between the flows. These prototypes can be accessed and interacted with via the computer using a web browser or using mobile devices where prototypes could run "as apps", hence they represent a great way of getting the feel of the app and testing it from a user experience point of view, without the need to write any code.Why build a prototype?Validate and iterate — a prototype is a great way to test and validate user flows with your target audience. Based on an initial prototype, and the feedback gathered from the user, the founders can make adjustments and improve the design and user experience.Convince investors — by showcasing your idea in full, investors are more likely to understand the backbone of what you're trying to achieve and they can see your vision for the product and how it would look like, before actually building it.Optimization — after building a prototype, founders get the full picture of how the app will look and work, after collecting feedback from the users, sometimes they discover that certain features are not needed or they simply don't make sense in the general idea of the app, so they can be removed for saving costs in the development phase.An interactive prototype in Figma. Source Figma.Example of a prototypeWe've built a prototype for the fragrance shop, one of the biggest retailers of fragrances in the UK. We've started with a paper prototype for defining the core features of the product and build a fully interactive prototype of the core features of the app.Mobile Minimum Viable Products (MVPs)An MVP is the first version of the app that allows the founder to test, and validate its idea, usually, used for finding and testing the product-market fit.In other words, an MVP is a version of the app that focuses on the core feature of the product and lets the founder validate their hypothesis and measure things like adoption rate, user satisfaction, and performance.MVPs are a combination of prototypes and POCs, as they focus both on user interaction as well as solving a real problem with the aid of technology.When building an MVP it's important to have enough features so that the app becomes marketable, but should be as minimal as possible, it should solve one problem, and it should do it properly. A good example of an MVP would be the first versions of the Shazam app, it did only one thing, recognizing songs and it did it well, later iterations have added a social part, the ability to listen to the song, add it to your library, see charts, etc., but to validate the hypothesis all they needed was a stripped-down version of the current product.Why build an MVP?Hypothesis validation & feedback — only by building an MVP a founder can truly test their hypothesis and gather feedback. With an MVP, founders can test their go-to-market approach, can gather larger amounts of feedback from their real audience, and can extract metrics like engagement, time spent on the app, or test the viability of their business model.Attract investors — a POC or a prototype could help you raise money, but an MVP can prove to your potential investors that you've achieved product-market fit and that you have traction which are the core things they look at when investing in a startup.Build your audience & get customers — an MVP is a great way of attracting your first customers and testing your product in a real-world scenario. In addition to this MVPs allow founders to get to know their audience better and to build a community around their product.Example of an MVPWe've to build aical to test our idea, that by using Machine Learning techniques we could improve the process of counting calories and living a healthier life. The first iteration of aical -- the MVP contained only the core feature, snapping a photo of your food and tracking the number of calories in your snaps. Once we've got enough traction (over 5000 users) we've included new features, such a bar code scanning, and integration with Siri and graphs.TL;DRPOC - Used for validating the feasibility of a feature from a technology, integration, and user input point of view. The focus is on the technological solution and its advantages and disadvantages. (Technology)Prototype - Used for showcasing the user experience, together with the visual identity/user interface of the app. The focus is on the interface, how does the app look and feel. (User experience)MVP - A first version of the app, with minimal functionality, build around the core feature of the app. The focus here is on both the technology side as well as on the user interaction and user interface. (Technology + User experience)When building a mobile product, all of the three concepts are important, however, sometimes you can skip steps.For instance, if the product you're trying to build, does not present any technical challenges (you don't need to reinvent the wheel) then a POC might not be needed, usually, a team of mobile experts could help you decide whether or not you need a POC.A design can also be validated without necessarily having an interactive prototype. Prototypes are more expensive than static UI/UX designs so a lot of founders choose to skip those as well.As for MVPs, every successful app was at one point an MVP, so if you're going to build a mobile product, you can't skip this phase. You can, but you'll spend a lot of resources on building a fully-fledged product, and most of the times you'll learn that users won't use it the way it was designed or it simply does not get traction or it does not solve the problem in a way that it's helpful for the user.If you have any questions on how to build your mobile product, or what the roadmap for your idea should be, get in touch and we'll help you uncover all the mysteries of successfully building a mobile product. --- ### Digital transformation using mobile apps URL: https://appssemble.com/blog/digital-transformation-using-mobile-apps Learn more about digitalization and how you can transform your business using mobile apps. What's digital transformation?Digital transformation is a broad concept, it's used as an umbrella term for describing various concepts of a business that have been enhanced by technology. In simple words, every process of a business that has been enhanced by the use of software & technology can be viewed as a digital transformation.An example of digital transformation would be a banking app that allows users to perform banking operations, previously possible only by making a trip to the bank.Digital transformation is usually driven by common factors which are industry agnostic:Reducing cost — by automating the process that previously required human interactionImproving the customer experience — by using technology and automated processes more users can be reached and their requests can be solved much fasterIncreasing the security and resilience — by using more technology in the processesHow it helps businesses?Mobile applications are a great way of digitalizing businesses, nowadays, people use their most personal devices -- smartphones, for doing a large variety of operations, from e-shopping to paying bills or getting medical advice through healthcare apps.Some ways in which mobile apps can help you digital transforming your company or startup are:Increase engagement — by using mobile apps for common processes in your business (such as transferring money, purchasing a ticket, or trading stocks) you're getting new ways to reach and target your customers, in addition to this, your services will be available 24/7.More sales — if your business is selling something online, E-Commerce apps have 157% more conversions than mobile web.Better recommendations — by using AI and analyzing the behavior of the user, a business can upsell services related to the user's interests, automaticallyFast and high-quality content delivery — by using the newest high-bandwidth mediums such as 4G or 5G.Automating manual processes — for instance, automatically sending out reminders that you're insurance is about to expire, or engaging with users via custom offers in special cases (such as birthdays).One common feature of the vast majority of digital transformation is the automation of certain tasks and flow in a way that human interaction is removed partially or as a whole. The results of digital transformation are lower costs and more efficiency, hence higher profits.In what areas of a business can digital transformation help?A business has multiple layers that interact towards achieving a common goal. Digital transformation can happen at multiple of those layers.Sales & MarketingBy definition, at the core of every business, we have profit. Companies are trying to acquire more customers and drive up more sales, but to do that, they need to get in front of the customers and their services have to be found easily.A great way of reaching new customers is by targeting your audience and informing them about the company's products and services. This can be easily done by using advertising networks such as Facebook, Instagram, Twitter, or Google Ads and grabbing the attention of your potential customers. By using paid ads, companies can target a real audience and can advertise their product in the audience's news feeds of popular social apps. Potential buyers which express interest in the services provided by the company will be redirected to the company's web page or mobile app where more details and information regarding the products and services can be digested.Digital transformation in marketing is an effective tool as the average US citizen spends as much as two hours and three minutes a day on average using social media, creating a great funnel of potential new customers. This gives companies a huge opportunity to engage with new customers and encourage them to find more about the products and services they are offering, through conversion-oriented pages and flows.Another area in which digital transformation can help the sales process is by using AI and ML learning techniques for improving the customer experience. The experience can be improved by using the latest technological advancements such as AR/VRwhich could help the users see and interact with the product before actually buying it (for instance user could see how a piece of furniture would look like in their home by using AR).In addition to this, the experience of the user could also be enhanced by using intelligent recommendation systems, which use AI techniques for recommending products and services which best fit their profile (just like Netflix does when you're on the home page or after you've finished a movie).Supply chainFor businesses that rely on a supply chain for achieving their goals, digital transformation can help automate the process of ordering and handling supplies.Based on historical data, ML algorithms can be used for implementing smart systems which would handle the supply, by automatically ordering supplies when you're about to run out, making predictions regarding the number of supplies needed for the next periods, or optimizing the logistics of the supply process.An example of digital transformation on the supply chain could be a restaurant that only does food deliveries. With the help of ML, the restaurant will have future projections on how many purchases they will have based on a lot of factors like weather, holidays, size of the city they operate in, previous purchasing patterns, etc., which will result in accurate assessments of the supplies needed for the next period. A smart supply system that is integrated with vendors could automatically order ingredients, packaging items so that the restaurant never runs out and they cook only with fresh ingredients.Low-tech businessesDigital transformation could also help low-tech businesses, for instance, small grocery shops. By offering online-based ordering, through the use of mobile apps, or websites, they can reach more customers and keep their business going, especially in times like the Covid pandemic where a lot of people have relied on delivery services for a vast majority of their purchases. The businesses that offer delivery services are here to stay and they've proven to be very effective at increasing sales.By offering services online, a small business can better nurture its customers with custom offers and loyalty programs that would turn their customers into fans.Digitalization and gamification have been applying to a lot of domains, especially due to the global pandemic. Businesses like on-demand video fitness apps, or e-learning platforms have sprong and gained a lot of popularity in the past few months. Gamification (gamification serves to increase user motivation) is a great tool that can be used to drive up user motivation and engagement and can be applied to a large area of businesses.Why does the digital transformation fail?Unfortunately, there are a few cases in which digital transformation does not live to its promises. We've discovered that the main reason for a failing digital transformation is that the business failed to properly integrate technology in their day-to-day tasks.For instance, a business might start using an advanced invoice system that automatically sends invoices and follows up with the customer based on the signed contract, but they won't integrate their contracts into the platform, so the system becomes an expensive invoice generator tool.For a digitalization process to be effective, the organization that implements it needs to restructure to gain all the benefits of using technology. Companies that fail to integrate the new digital processes in their workflow and restructure the processes around them, don't rip all the benefits of using technology and might create an extra workload which results in diminished profits or more work being made.Digitalizing a business is a symbiosis between technology and implementation. Not all business types can be successfully digitalized, and even those can run into issues while implementing the digital transformation. Those issues are frequently due to the employees who are not well trained in using the technology and understanding all the benefits of how technology can make their jobs simpler.BankingRevolut is one of the most popular digital banks, a lot of customers, especially young ones are using it as it provided an easy way of managing your expenses, transferring funds, converting currency, or investing in stocks. With the rise of fintech, a lot of traditional banks had started a digital transformation process, to keep their customers and attract new ones.Such an example from the heart of Transilvania, appssemble's home, is Banca Transilvania. They are a traditional bank but they have started a digitalization process with great results, their mobile apps have become widely used by both tech-savvy and young people as well as their previous customers which were accustomed to a more traditional way of doing different banking operations.RetailOnline shopping is now more popular than ever, a lot of shops have transitioned their services online (web and mobile apps). This digitalization of such business allowed them to offer their services non-stop and nowadays a lot of stores offer online products which are not available in the physical stores.Many of the premium brands which sold their products exclusively in physical stores such as Burberry, embraced digital transformation, and offer their products online via mobile apps or websites.More than half of the mobile users are online shoppers, having a mobile app for selling your services is a great way of reaching those customers.HealthcareOne of the most active industries from a digitalization point of view is healthcare. A lot of the processes which involved a visit to a medical practice now happen online. Apps such as MDLive allow their users to connect with a doctor and get help without the need to leave the comfort of their home.For the healthcare industry, this is a big shift, as doctors don't have to be in the same geographical area as the patients anymore, technology allows them to help and treat more people.appssemble helps companies implement digital transformations through knowledge and experienceThe knowledge we acquired from working for big enterprises (Bosch, Honda, Deloitte) and startups offered us the tools needed to guide you through the digital transformation of your business. Our team of technical experts and designers builds digital products that make a long-lasting impact on the user and simplify your businesses.We are not just building digital products, we help you all the way through in digitalizing your business. Our core mission is to help customers succeed with the aid of technology, which means we use all the means necessary to ensure that your digital transformation is a success. Get in touch and learn more about how can we help you in your digital transformation journey. --- ### How much does it cost to develop a Clubhouse like MVP? URL: https://appssemble.com/blog/how-much-does-it-cost-to-develop-a-clubhouse-like-mvp There are a lot of costs involved in building a successful MVP, find out more about costs involved in building a mobile MVP like Clubhouse. If you are here you probably already know what Clubhouse is and what it does. But how much would the mobile development cost to develop a similar app? Is it worth it? And would you be able to replicate the success Clubhouse currently has?User InterfaceIf it were to describe the UI of Clubhouse in one word, it would be retro. While the retro current became more and more popular in other industries, like fashion and music, in tech it is not that popular, big tech players are still going for a clean and modern design.The app reminds me of the beginnings of Instagram and Twitter when people were still figuring out how mobile apps should look like and what should they do. Now, let’s see how a cost estimate would look like for the UI/UX design of a similar app (not a copy of the actual Clubhouse design, let’s say we build it from scratch):Logo and app icon — $500Login/Signup flow — $1.000Main screen — $3.200Explore section — $1.500Explore search — $600Clubs explore — $1.500Start a room — $1.300Room — $1.600Upcoming — $640Invites — $640Activity — $320Profile — $1.280Settings — $960Total: $15.040Several improvements could be added to this design, like prettier loading screens and error dialogs, better-looking icons, and overall a more dynamic/live feel of the app, but this is a discussion for another topic.Mobile developmentThe mobile development part might seem complicated at first but remember, we are in 2021 when there are a lot of Saas solutions that we can use so we don’t have to reinvent the wheel every time. From the development perspective, we can split the development process into 4 parts.Building the backend of the appSeveral frameworks could be used for building the backend for an app like Clubhouse, there is no constraint so it is more a matter of preference. For convenience we will assume the backend will be built with your favorite framework in the Go language.Environments setup — $640Login/Signup API — $1.000User profile API — $2.300Rooms API — $3.200Main feed API — $3.800Search API — $3.200Activity API — $1.900Following API — $2.500Upcoming API — $1.600Topics API — $1.600Invites API — $640Total: $22.380Building the UI and integrating the backend API into an iOS appNext, we want to build the iOS app and integrate the backend API. After this step, we will have a fully working app, but without the actual core functionality which is the VoIP part. A cost estimate for this implementation would look like this:Login/Signup flow — $2.240Main screen — $4.800Explore section — $5.500Explore search — $3.200Clubs explore — $3.200Start a room — $2.500Room details — $2.500Upcoming — $1.600Invites — $1.280Activity — $2.000Profile — $4.800Settings — $3.900Total: $34.320Mobile audio streaming / VoIPIn 2021 audio streaming is not a technical issue anymore. While there are still scaling challenges, for an MVP of up to 1 million users, using a ready-to-use free solution like jitsi or a WebRTC server should be enough. This would also imply that we have to support some server costs.If the MVP proves successful like Clubhouse is right now, we can start thinking about building a scalable VoIP infrastructure. For this, there are many solutions from just using more servers to choosing the right codecs, but this is a subject for another topic. Here, for convenience we will stick to a free solution and will estimate just the cost of integrating such a solution:Setting up the servers — $1.600Integrating VoIP in the app — $3.200Total: $4.800Mobile app testingTesting an app like Clubhouse is not a trivial task. Many tests should be done to assure the optimal running of the app. Given this is an MVP we recommend only doing the minimum testing that would assure a proper running of the app and avoid doing automated tests at this stage of the app development. The testing should be done in parallel with the development to fix the possible issues as early as possible.Manual testing of the app — $8.200Load testing of the backend — $2.500Load testing of VoIP servers — $4.000Total: $14.700The total estimated cost for the app development: $91.240 Monthly servers cost: 1000$-5000$ depending on the usageMobile MVP marketingFrom this point on, the focus should shift to marketing and promoting the app. Getting into details about how to do marketing for a Clubhouse-like application would make this already long article longer. We can shortly note the channels that should be used for a successful launch.Since this is an app addressed to pretty much everyone, the main goal of the marketing strategy would be to create some hype around the app and get as many people as possible to talk about it. To do this, the main marketing channel should be social media, tech reviewers, and tech news websites.The goal is to create a snowball effect that would drive enough downloads to put the app on top in the AppStore for its category. Cost for marketing could vary wildly and a better approach here is to set a budget. For an MVP like this a starting budget should look like this:Marketing — $10.000 - $15.000 / monthPartnerships — $50.000 - $100.000 / yearTotal: $170.000 - 280.000$appssemble can help you build VoIP and social MVPsWhile building a Clubhouse like MVP does not pose any technical difficulties and does not involve a cost for R&D or paying for some shiny new tech, replicating their success might be hard to do. The new social media platform came after a year where working from home was the norm and people got used more and more to video or audio conferences instead of face-to-face meetings.Social apps are popular nowadays, especially due to the times we transition. If you want to learn more about how can you build an MVP or you need a cost estimate for your idea, get in touch, we would love to help! --- ### Why should you spend time and money on a mobile MVP? URL: https://appssemble.com/blog/why-should-you-spend-time-and-money-on-a-mobile-mvp Mobile MVPs focus on the core solution that allows businesses and founders to test their hypotheses and adjust accordingly for future iterations. Should you build an MVP?A Minimum Viable Product (MVP) is the best way for a founder or a business to validate their hypothesis by getting in front of their customers through digital marketplaces and test it with a real audience.The process of developing an MVP is costly from both a time perspective as well as financially, to get good results, an MVP should focus on a bare minimum set of features that would allow testing the idea of the product.The psychologist Gerald Weinberg has shown that people are more productive and achieve better tasks when they are focusing on only one task, switching context, and doing more than one thing, heavily affects productivity and the overall performance.When doing 2 tasks, you lose 20% of your productive time when switching contexts, for 3 tasks this number goes up to 40%. This is also true for mobile products, by focusing on a limited set of features, a founder or a business that develops an MVP has a much better chance at success and achieves much better results as he focuses on solving one problem only.What to include in an MVP?Deciding on the roadmap and the feature set of an MVP is a difficult task, especially for a first-time founder, or a business that tries to solve a new problem that is different from what they are used to doing. Before going in and developing an MVP full of useless features that will not provide any usefulness for your user, it's important to plan accordingly and focus on the problem and the right audience.As its names say it, an MVP should be a MINIMUM VIABLE product, which means you'll need to cut and reduce the feature set of the product until you'll reach the core of your main idea. Besides the benefit of having the founders concentrating on solving a problem and doing it innovatively, restricting the feature set also allows faster implementation, hence a faster idea-to-market time and most importantly, lower costs.A good example of that would be Shazam, when they first launched, their app didonly one thing, recognizing the name of the song from an audio recording, and they've done it exceptionally. All the other features like tops of the most searched music, the ability to listen to the full song, or adding it to your library came much later, and only after they've achieved their product-market fit and people start using and loving the product.On the other hand, Quibi, a streaming service born in the pandemic was a mobile streaming service that allowed users to watch bite-sized content on their devices, is at the exact opposite pole. After spending over $1 billion in developing the full product, without any market validation and iterations on the idea, they had to shut it down, 6 months after the lunch as they did not get market traction.The ideal way of starting an MVP is by doing a product workshop, in which you'll work with a team of mobile product experts, designers, and developers for defining your product (tech and design), and roadmap for implementation. Based on the outcome of the product workshop, you'll be able to collect feedback from a group of users in your target audience, adjust the product, and have a clear vision of the action plan, the costs involved, and timelines.Why should you build an MVP?An MVP is the first iteration of your product, is the watered-down, slim version of your grand vision. It should provide a solution to the core problem you're trying to solve, in a manner that's good enough for the users to use and engage with for you to test the hypothesis of the product.Attract investors and stakeholders - An MVP helps you sell your idea to investors or stakeholders (if you're building an MVP for a corporation). It shows them the technical feasibility of your solution, they get a better grasp on what you're trying to achieve, by being able to play around with the app, and most importantly, based on the feedback from your early users, you can show the positive sides as well as the negative one and how that aligns with your growth and future development plans.Better understand your target audience - The feedback, reviews, and app analytics for the MVP provide insightful information on how are they using your product, what are they struggling with, and how can you adjust and modify the product to better fit their needs. Only by incorporating the users' feedback and by paying attention to their needs and how they use your MVP, you'll be able to scale it and make a successful product that users love.Test the market - There are many examples (like Quibi) that did not probably test the market before spending money on a fully-fledged product. An MVP helps alleviate this problem as it will help founders to test the demand for their solution and decide whether or not to further invest time and resources in this endeavor.Perfect your business model - An MVP we'll get you your first customers, based on their behavior, you'll be able to make more informed decisions about your business model, as you'll have a quantitative measure of how many of them become paying customers and what are your operational costs. Mobile MVP usually implements a freemium model, where they make their services free for attracting more users and getting more feedback but will also include extra purchasable content or subscriptions for the customers who want more and are willing to pay.Every successful mobile product has started as an MVP.We know that the start of a new mobile product is one of the most important steps in its lifecycle. There are a lot of resources and books that teach you how to run a successful business but there are limited sources for those who just started or want to start building a mobile product. At appssemble, we are here to help you and guide you through the whole process of building an MVP, picking out the right feature set and the right technologies so that you can get the best setup to test your assumptions and to be able to pivot on the feedback of your early users.If you want to build a mobile MVP, get in touch and learn more about our process for building successful mobile apps MVPs, and how can we help you reach your first customers. --- ### How to build a Live Streaming app - Product, Monetization, Tech, Features & Costs URL: https://appssemble.com/blog/how-to-build-a-live-streaming-app-product-monetization-tech-features-costs The live video streaming market is expected to hit $70 billion in 2021, we look at how can you build a streaming app and what technologies are involved. The live video streaming market is expected to hit $70 billion in 2021 was shown in a study from 2016. With the COVID-19 pandemic crisis, this process has accelerated drastically, and a lot of offline activities have moved online and Satya Nadella the CEO of Microsoft has stated that according to metrics from Microsoft, we had "2 years of digital transformation in 2 months".Video content is the king nowadays, with more than 80% of US users preferring to watch a video than reading a blog post or articles, in addition to this, the viewing rate of videos is 10 – 20 times higher for live content than for prerecorded, on-demand one.Live video streaming is really popular, we find it in Facebook's products, Instagram live stories, or on Twitch where a lot of gamers stream their plays. However, there is still much room for innovation as more and more of our activities are moving online, live training sessions, courses, conferences, or live assistance are just a few of the topics which started to be enhanced by live streaming solutions. In addition to this, due to privacy issues, many companies, and people are moving away from video communication tools from big companies.Smartphones are our most personal devices, and they have great hardware capabilities for creating, streaming, and watching live video content. Today we are going to talk about the technology behind live-streaming apps, what should you consider if you want to solve a problem through live streaming and what are the costs of developing such an app.How to build a live streaming app MVP?ProductNever build on assumptions is our mantra at appssemble, before building a product it's important to understand what's its purpose, and the business model around it.It's important to conduct surveys and talk to the users before building a product, that why we enourage you to conduct a free Discovery session and a Design Sprintbefore developing the product.From a business model perspective, live streaming apps implement a subscription-based model (monthly, yearly subscriptions), but there are also cases where Ads are used as a revenue source.ExperienceWhen building an MVP, the focus is on the core of the product, the main feature only, but that core needs to function remarkably well. When building a streaming app there are a couple of things that make the live streaming experience a pleasant one:The content needs to be available instantly and the streams must have an as little delay as possibleStreaming content should not consume too many network resources - the internet is not cheap in many countries, especially the one from carrier providers, when building a streaming app you should make sure you're not using more bandwidth than you're needingStreaming or watching a video should not drain the battery - unfortunately, this is the case with many apps where streaming, encoding, or decoding live video takes a big toll on the energy efficiency of the devices it runs onPrivacy - we are strong advocates of privacy, the content of the user should be his own and have full control over itLast but not least, the UX/UI represents a major part in the success of the app, the flow of the user as well as how it interacts with the content can be a deal maker or breakerTechnologyThe most popular live video streaming protocols are WebRTC and RTMP/S each with its own strong and weak points. Depending on the scope and budget custom solutions can be built that implement WebRTC and RTMP/S services, those usually cost more to develop but have lower operational costs, or third party services can be used to lower the development time but the operational cost is going to be greater.When developing an MVP what we usually recommend is going with a third-party service provider for the first iteration of MVP, to test the market, user engagement, acquisition, etc., and if the product is successful move onto a custom solution with lower operational costs.WebRTC in mobile appsThis technology allows for an extra layer of privacy as the connection (if possible) is made directly between the users involved in the communication, meaning the video goes straight from user A to user B without using an intermediate server, which results in lower latency, and lower operational costs. In cases where this approach fails, a relay server is used as a middle man for communication.The downside of using this protocol is given by its strong point, in the case of apps where more than 2 participants are live streaming, the bandwidth used for streaming increases drastically.To illustrate this example, let's imagine 3 users (A, B, C) that are engaged in a live streaming session. For this to work, each one of them has to send the stream from his camera to the other 2 users (user A streams its video stream to user B, and also streams it to user C) in addition to this, it needs to download streams from the other two users (user A downloads the video feed from user B and user C) to be able to see them.As you can see, the network usage is affected by this quite a lot, as well as battery usage. Using WebRTC works well for around a maximum of 5 users who stream at the same time, after that point the resources consumed are too heavy for devices that are not constantly plugged into an energy source or have a WiFi connection.ProsLower operational costsIncreased privacyLow latencyConsDoes not work well for more than 5 users on mobile devices - in general, it should be used for apps where communication is restricted to a low number of users, or when only a video feed is sent (the presenter sends the video to all of the participants, the participants are only watchers).RTMP / RTMPS in mobile appsThis protocol is the most used for high-definition streaming, where a delay of 10–15 seconds (from the moment when it was streamed to when the user sees it) is acceptable, this is used for instance when streaming a conference, a sporting event, or a concert in which there is no real-time interaction with the viewers (only trough messages, and other means different than video).The content from the streamer goes to a server that processes it and viewers interact with that server for viewing it, hence the delay. In terms of privacy, in this protocol, the communication always happens through a mediator (third party server).The downside of this technology is that does not allow live streaming between the participants and it's also less advanced from a privacy point of view as the video is processed before viewers can view it. In addition to this, the streamer server knows who are all the watchers of the stream and can represent a single point of failure - in the case where there aren't multiple serversProsHigh-quality videos, that can be modified (eq. applying watermarks)Supports a large number of users - it can be scaled to any number of watchersVideos can be stored and viewed on-demand after the stream has endedConsUsage of third parties for communicationA delay of 10–15 secondsDoes not support real-time communication for all the users involved in the conversationFeatures & CostsEvery MVP is different in its way, compiling a definitive set of features for a live streaming MVP is not possible, but many of the mobile apps which have streaming as their main component have some of the following featuresUser registration / loginUser profileA list of streamers/feeds and the ability to search or filter themStreaming or watching a live streamSubscription mechanismNotfificationsFrom a cost-wise perspective, an accurate estimate for such a project can not be made as it heavily depends on the features set, design, number of users, etc. A ballpark estimate for such an app, assuming no complex design interfaces, heavily relying on native components, which uses WebRTC for communication is given in the following table.The price of the project includes manual QA, development, and project management needed for one platform (iOS or Android).We have a wide experience in building streaming applications, our technologies are used by Bosch, Honda, and a lot of developers through our free SDKs.If you're looking for a partner for building a great streaming app, get in touch and let us guide you through the process. Drop us an email, and let’s discuss more! --- ### An Overview of 2020 from a Mobile perspective URL: https://appssemble.com/blog/an-overview-of-2020-from-a-mobile-perspective Did you worry you spent too much time on your phone these past months? Maybe even for the last year? Statistics say we spent 1.6 trillion hours on a mobile device in the last year. 2020 was THE year for mobile devices, meaning it was the year of the highest mobile use. Did you worry you spent too much time on your phone these past months? Maybe even for the last year? Statistics say we spent 1.6 trillion hours on a mobile device in 2020. But don’t blame yourself too much, it’s not you, it’s Corona, or at least that’s what I like to tell myself. But let’s see the bright side in these unfortunate times, some of us -anxious individuals-, get to work remotely from home, participate in online classes, shop online and avoid stress-inducing situations like not knowing if you should shake hands or give a hug when meeting with friends, or nervously say “You too” to a waiter who wishes you to enjoy your food.All jokes aside, Appssemble’s company culture embraces accountability. Keeping everyone safe is a priority for us, so our company moved remotely from home, where we continue to design and develop native mobile apps, fast & on budget.As I was saying, 2020 was THE year for mobile devices, meaning it was also the year of the highest mobile use. Kind of ironic if you think about it since we lived perhaps one of the most immobile year of our life. Now let’s talk mobile.Average Amount of Time Spent Generally on a Mobile DeviceLet’s see how much time we spent on a mobile device in general. App Annie was the one that said we spent 1.6 trillion hours in 2020 on mobile devices so far, and that’s only in the first half of the year. Impressive, indeed!According to eMarketer, adults (+18 y.o) spend an average of 3 hours, 50 minutes a day on their smartphones, generally speaking, dethroning TV use;and an average of 3:35 minutes in apps and 25 minutes in a browser.The coronavirus has advanced mobile use by 2 to 3 years — accelerating our transition to the world of mobile-first. (AppAnnie, 2020)Habits on mobile devicesSince most things moved into quarantine and remote work, we developed an obvious need of mobile use, whether it is for working, ordering food, paying utilities, education, fitness & health, entertainment or connecting with friends.Smartphones have a clear dominance in the mobile-use statistics, almost everybody owns one nowadays. In 2019, Statista said there were 4.8 Billion people using phones, in 2020 it reached 6.95 Billion and in 2021 it’s expected to get up to 7.1 Billion worldwide. Therefore, our homes will remain the epicentre of our social and working lives, with 43% ‘At-Home’ behaviours linked to mobile use.Next, let’s see both of Apple Store and Google Play’s 2020 habits in different App Categories such as Gaming, Education, Entertainment, Health & Fitness and Shopping.Is there anyone here who didn’t play anything from the Gaming category in 2020 while staying at home? I’m 99.9% sure there isn’t since it’s the most popular category by downloads. Whether it’s an adventure game, arcade, educational, sport or strategy, almost everybody relaxes their mind by engaging in some sort of online game, whether it’s on an app or in a browser. As a result, mobile playtime increased by 62% in 2020. (GameAnalytics, 2020). Top Gaming Apps Worldwide by Download are Among Us, Subway Surfers, Join Clash 3D, Garena Free Fire, Genshin Impactand others.The Educational category is thriving this year giving the fact that we live in the informational era, where everything is accessible, convenient and mobile, straight from the comfort of our home. It’s not so unnatural anymore to be studying online, whether it is for academic purposes or personal development. Top Educational Apps Worldwide by Download are Google Classroom, YouTube Kids, Duolingo-Language Lessons, Photomath, Brainly-Homework Help App and Kahoot! Play &Create Quizzes. We might even include the most popular-by-use video conference platforms: Microsoft Teams, Google Meets and Zoom Meeting.What did we do in 2020 with all this spare time that we had? After a good session of playing and/or studying, we amused ourselves with various choices from theEntertainment category of course. Top Entertainment Apps Worldwide seem to be: Netflix, YouTube, Spotify, Amazon Prime Video, Apple Music, Twitch, TED, Google Play Books and TuneIn.At the opposite side of ‘motionlessness’, we find a healthy category of apps where people liked to spend their time in 2020. The Fitness & Health category. The benefits of exercises are well known, but in order to enjoy the rewards, you need to stick to a consistent and disciplined routine. This is where technology comes into help with apps where you can find a virtual personal trainer, specific exercises or a training partner to keep you motivated to work at home. This category is also known for its versatility, for its multiple subcategories such as Running, Walking, Activity Tracking, Cardio or full-on workouts. According to Forbes, Top Health & Fitness Apps Worldwide by Download are Calm, FitBit, MyFitnessPal, Headspace, Flo, Muscle Booster Workout, Better Me, Fitness Coach, Samsung Health, Home Workout.Customers began using their mobile devices for product testing as soon as they hunkered down at home and 69% of internet users said they prefer searching for feedback on their phones rather than contacting an in-store employee. And I understand that completely! That being said because individuals like to search online, they obviously also like to shop online. Two thirds — 66% of internet users use Shopping applications on their mobile devices, 57% of them being between the ages of 25–34. Top Shopping Apps Worldwide are Wish, SHEIN, Amazon, eBay, AliExpress, Joom, Alibaba and Pinduoduo.Most Popular Apps of 20201.FacebookSince the app is number 1 in the entire world, it’s no surprise that Facebook is one of the most popular apps of 2020. It’s perhaps the most useful app to connect and stay in touch with people. The Facebook family include Instagram, WhatsApp and Facebook Messenger-another favourite one in the App store.2.TikTokAs of Q3(3rd quarter) 2020, TikTok was number 2 in the non-gaming apps for user spending. TikTok has seen a sharp rise in active-users in 2020, almost three times the size since 2018. In 2021, we expect TikTok not only to get the craved-spot in the 1Billion-active-users-club/month but is also aiming to pass 1.2 Billion.3.ZoomThis app is definitely one of the most proeminent new entries in 2020, along with a few other video conferencing applications. Zoom reported more than 30 million daily attendees in April 2020, and in March 2020 there was a daily download of 2.13 million.4.What'sAppIt might not be a new app, but it definitely experienced continued downloads in 2020. As of July 2020, it has topped the most popular global mobile messaging app of the year list, with over 2 billion downloads.5.InstagramThis photo and video sharing app is one of the most popular application among Gen Z and Millennials. Instagram is particularly useful in marketing. The app provides marketers with plenty of opportunities between IGTV, Instagram Lives, Instagram Stories and Reels to engage with their audience.6. Google MeetsAs with Zoom, Google Meet has seen unforeseen download boosts. The app reached over 50 million downloads in May 2020, with users who work from home, turning to the service. During the pandemic, Google Meet became more popular because of the free use for all users.7. YouTubeMore time at home allows users to use YouTube to help consume time. With more than 29.3 million installs, YouTube was the world’s most downloaded streaming app in May 2020.RevenueConsumers Downloaded 33 Billion New Apps in Q3(3rd quarter) 2020Google Play downloads rose to 25 billion, 10% year over year, while the iOS AppStore downloads grew to nearly 9 billion year-over-year by 20%.Non-gaming applications accounted for 55% of all downloads on GooglePlay, while the figure was marginally higher at 70% on iOS.Sports, Tools and Entertainment were the highest at the category level by downloads on Google Play.Sports, Picture and Video and Entertainment remained the biggest download categories on iOS.Consumers Spent a Record $28B in Apps in Q3 2020On the iOS AppStore, spending grew by 20% year-on-year to $18 billion in Q3 2020; spending on Google Play grew by 35% year-on-year to more than $10 billion.On Android, the largest categories were games, social and entertainment by consumer spending. The three largest categories of consumer spending were on iOS, games, entertainment and photo and video.Design & Development trendsDesignIt’s important to bear in mind that the target of the designer must always be the same for these current trends that we have right now, by using new methods and innovations in order to change the user’s lives. Whenever you analyze a specific trend, consider it to make the best user experience in the light of the importance it provides to consumers. And the latest UI/UX Design Trends seem to be the following:DevelopmentWith the growth of mobile apps, it should come as no surprise that opportunities to work as a mobile developer will only increase in the coming years. Burning Glass, which compiles and analyzes millions of jobs across the world, predicts that mobile app developer jobs will rise by 30.7% over the next decade.So here we are at the end, the end of the article, the year and hopefully the end of Covid-19 pandemic and its restrictions. Let me give you a short summarization of the content: we spent 1.6 Trillion Hours on Mobiles Devices in 2020; there are 6.94 Billion people using phones; people enjoyed playing games throughout the year, therefore playtime increased by 62% in 2020; we started using more Fitness & Health apps; people readjusted eCommerce; most popular apps in 2020 are Facebook, TikTok, Zoom, WhatsApp, Instagram, Google Meets and YouTube; the mobile design trend changed; consumers downloaded 33 Billion New Apps and spent $28 Billion in Applications Store. --- ### What are great food delivery apps made of? URL: https://appssemble.com/blog/what-are-great-food-delivery-apps-made-of What makes a food delivery app great? We look at the product side, business models, client acquisition, marketing as well as the implementation side and analyze what makes a food delivery app catchy. Today we are starting a new series at appssemble where we are going to talk about various types of applications, how do their business work, who are their target customers, and last but not least, what does it take to build a great app.The first domain we’ve tackled is food delivery apps, as they are really popular especially now and every few months there seems to be a new app that tries to solve this problem.ProblemFood ordering apps solve a big problem in today’s world, it helps the users get the food they want without wasting time going out to a restaurant, cooking it themselves or leaving the comfort of their home or office. The ability to have a digital menu from various restaurants near you and be able to choose a dish from this large variety makes food ordering apps very popular, especially with the people who work office jobs.DemographicsAccording to this paper (Why do people use food delivery apps (FDA)? A uses and gratification theory perspective) published in November 2019, men tend to use those kinds of apps more often than women (63% men and 37% women), in addition to this, over 85% of the users are aged between 19–30 years old, come from Middle-class families, pursue or completed a graduated or master’s degree and use the app a few times a month (with the vast majority using the app multiple times/week).Business modelFood delivery apps make money from multiple sources, the most common ones are the following, ordered by the percentage:percentage of the order — paid by the restaurant when an order is placed from the app, the vast majority of the income comes from this revenue streamdelivery fees — some companies have their fleet of delivery or they are collaborating with some company which handles the delivery, most of the times, the users pay more than the actual delivery it would cost, so that results in another stream of revenuein-app ads — some apps display ads from the restaurants that have various promotions and want to advertise on the appselling the data regarding user behavior to other companies — knowing what type of user order more, from what restaurants, which dishes, and in what location, it valuable information for advertising companiesservice fees — a large number of apps practice a service fee that is used to make the product better (marketing, development, customer support)MarketingTo make this kind of app popular, you would either have to be in a geographical zone where there aren’t such apps, and you find an increase in the target demographics (young, educated people that come from the middle class), usual cities with big universities. Or spend a lot of money on advertising.Most of those apps spend a huge budget on advertising (millions of dollars) to acquire new users, sometimes the big companies such as DoorDash or FoodPanda also buy other small companies in the same business to take away their market share.Food delivery apps are more common on mobile than on the web, thus their marketing campaigns are specifically tailored for this kind of medium, displaying ads for their app in other popular apps, or in the searches made from those devices. Just for the sake of numbers, we have looked at how much do some of the most popular food delivery apps advertise on the Facebook network, DoorDash has around 2900 running ads, FoodPanda around 1700 while UberEats around 700 and Deliveroo 500at the time of writing.Entering this segment of apps requires as we saw a large capital spend on advertising to convince users to use your app, or to have a superior product that people love to use.ProductThe functionalities of a food delivery app are pretty straight forward, to allow the user to order their favorite food and have it delivered to them. We won’t enter the details about how to restaurants handle the orders and how the apps they use look like, we are going to focus only on the mobile apps in search of finding out, what makes a food delivery app great.Sign upLike all the apps, the ones who let you try them out before asking for your details, delivery address, etc, are more user friendly and create a better experience, among the popular ones, Deliveroo is the only one which does that. Other apps have a pretty straightforward and easy to use sign up process (Uber Eats, Grab Eats) while others seem they are purposely trying to make it harder for the user to use their app. I’m talking about DoorDash where sign-in with Apple does not work properly, and they don’t allow signing up with other phone number country codes than the 3 ones where they operate, for me, as a foreign user this is a big disappointment and I’ll choose their competitors.Main screenThe main screen of the most popular food delivery apps are composed of multiple items:search feature — allows users to search for their favorite foodsfiltering — allows filtering of the offers based on food type, price, time to deliver, or even by dietary options and restaurants hygiene ratingsfood type selector — allows filtering only the restaurants which serve a certain type of food (breakfast, Asian, America, Italian, fast-food, deserts) or various deals and offers.various type of categories — such as “popular near you”, “new on the platform”, “today’s deals”, etc.promotional offersrecommendation based on your previous orderslist of restaurantsAs we can see there is a lot of information to be fitted on a screen, and sometimes the UI of those apps seems crowded, especially when they also have ads from various restaurants in your feed (eq. FoodPanda).It’s common knowledge that more options make you sadder and makes your decision harder to take, some apps, have lists that span over the 6–7 screens only with filtering options — this results in a bad UX as it makes the whole process of ordering food more laborious and takes to much time.We believe that apps in this category should allow the user to order food as easily as possible and helping them decide on what to order based on previous experiences and what happens around you (if you travel to a new city or country for instance, or if there is a new gem in town).Because an MVP brings restrictions when it comes to releasing entire sets of functionalities, it challenges you to think of the real problem the product is solving for its customers and the core value proposition of it.All the apps allow you to enter an address either via searching, automatically inferring it from your current location, or picking a point on the map. Some apps however don’t allow you to search for locations in other countries (for instance if you are in Berlin, you can’t look at restaurants from Paris, and order there) or even worse if you try to see the offers in another country, they ask you to log out and create a new account (I’m looking at you FoodPanda).Ordering processFinding what to eat is a task handled by the main screen of the app, where you can filter and search for the right food, afterwards, you are redirected to a restaurant for configuring your product. The restaurant is responsible for showing you a picture of the product as well as some details, unfortunately, all of the analyzed apps lacked all or multiple of the following details:MVPs are renowned for helping business owners and startup founders test and validating their product idea. Bringing an ideology of only building core functionalities and being cautious with the money invested, and MVP will help founders achieve market fit while decreasing future investments in the product.pictures of the same dishnutritional valuesingredientssize of the dishallergen informationIn most of the apps after you’ve selected your favorite dish, they let you configure it according to the restaurant’s offerings and they also recommend products that go by well with the one you’re about to purchase (desserts, drinks, etc). In addition to this, they also give you a time estimate for the delivery, a breakdown of the costs, and the ability to pay with either credit cards, cash, or technologies like Apple Pay and Google Pay.OrdersAfter an order has been placed, all the apps try to inform you regarding the status of an order, however, those estimates and statuses are pretty far away from reality with most of them according to the reviews in the app. Implementing an accurate tracking system is not an easy task, especially if you combine it with a time estimate and the fact that the food might be delivered by third parties not necessarily the employees of the company which owns the app.Order status while inconvenient is not the major problem with this functionality, the most frustrating one comes from the fact that in most of the apps you can NOT cancel an order from the app, you need to call either the restaurant or the customer support from the app to do that. Not only you can not cancel your order easily, but you can’t event append to it, so if you forgot to order something, you either place a new order (new delivery and service charges) or you call the restaurant or customer support and see if they can help you.This kind of behavior seems outdated in 2020, we understand that there are some technical difficulties, but they should not be a problem for well-established companies such as FoodPanda or Deliveroo.What does it take to build a great food delivery app?TargetOur main focus should be on young persons (aged 19–30) which live in cities that either has big universities or their economy works well and have attended higher education (bachelor, masters, or Ph.D. degrees). Having a clear vision of who is using the app, can make us make better decisions while developing it.Must-have FeaturesThe app should allow at a bare minimum to order your favorite dish from a restaurant nearby and to do that in an easy, straight-forward way. Other must-have features include:easy sign-up, and it should be delayed to the moment when the app has to know all that info (name, address, payment methods, etc.)credit card / cash / Apple Pay / Google Pay paymentsthe ability to search a restaurant or a dishfiltering of restaurants (based on price, food type)option to add instructions for the restaurant stafforder status and ETA’sorder historyhave a fast, friendly, and helpful customer serviceNeedless to say that those features would need to be implemented in a way that the user will experience a consistent, lag-free, and eye-candy manner. A good example of such an app would be Takeaway.com.Should-have featuresBesides everything enumerated in the must-have category, if we want to build a good food delivery app and enhance the experience of the users, it should also include the following features:food recommendation and offersthe ability to explore restaurants in other geographic areasfiltering based on delivery time, price, offers, cuisine, and dietary optionan enhanced order status including tracking of the food and the ability to contact the courierpush notifications regarding the status of the ordersthe ability to cancel the order from within the appshow allergen and nutritional values of the dishesNice-to-have featuressplit the bill — allowing multiple users the order food in one single order delivered to one location would be something that the users would love, I know I wouldappending to an order after you placed it — obviously, you shouldn’t allow the users to modify the order after the restaurant has sent it, however allowing this to happen in a certain time frame, before the food is shipped would be a great enhancement to the status quo.dietary plan & calories calculator — entering your desired calorie intake together with a dietary plan so that the app could show you food recommendation that would help you achieve your daily goalsUnfortunately, I couldn’t find a good example of such an app, but this is also good news since it shows there is still room for improvement in this domain.We’ve seen a trend where more and more restaurants or chains of restaurants move away from food delivery apps that aggregate multiple other restaurants and they build their platforms, this is mainly because of the fees of the platform and the association of their brand with others. User’s however, like diversity and don’t want to have multiple different food apps installed, finding the right balance between diversity, costs, brand awareness, and quality is always a hard task.ConclusionsBeing in the food delivery business is just like in any other business, you would either have to be well-founded or a market that allows it to easily grow. The good news is there is still room for improvement and new ideas, for instance, Apple introduced App Clips, which are opening a new set of possibilities for those kinds of apps. --- ### The benefits of building an MVP for your startup & how to build a Minimum Viable Product. URL: https://appssemble.com/blog/the-benefits-of-building-an-mvp-for-your-startup-how-to-build-a-minimum-viable-product How do you make sure that the product you build can sustain your business while generating income? And how do you do fast, customer feedback-based releases? Technology is taking over the world. Taking a quick look around us, we see digitalisation gaining more and more traction.Even more today, in the light of the pandemic we’re experiencing, global businesses are looking to automatise their processes and replace humans with machines while offering online, technology-based services to their customers — and here’s where digital products enter the scene.But how do you make sure that the product you build can sustain your business while generating income? And how do you fast, customer feedback-based releases?At appssemble, we encourage all of our clients to first build an MVP for their product.What is an MVP?Eric Ries defined an MVP as that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort. This validated learning comes in the form of whether your customers will purchase your product.One of the promises that lay under this definition is that after launching a minimum viable version of your product, you get to observe your customer’s behaviour with the digital product and collect feedback from the way they interact with it.Note how less functionality does not mean poor quality. In fact, it is essential to know that in a relatively competitive digital world, to achieve customer traction, the software you build needs to be more than just a few lines of code well kept into a repository. It needs to create emotion, blend into the everyday environment, solve real-deal problems, and tell you a little story while it does all that.The benefits of building an MVPMVPs had their time of popularity in the startup world. Founders and new product builders all over the world are choosing Eric Ries's MVP to validate their ideas, accomplish the market fit, gather feedback from their customers and, why not, attract new investments. In short, an MVP is a great way to layout your business idea, and see if it works or not without investing a tone of money beforehand, which leads us to our first benefit of building a minimum viable version of your product first.1. An MVP saves you time and money.As a startup founder and new product builder, you can easily fall into the trap of adding too much functionality to your product before getting it on the market to have its first interaction with the users. This means that you can easily invest loads of money into something that hasn’t been tested, hence validated by the users.Ideally, you would want to release the core features of the product, get them out to your beta testers, and continue with the roadmap of your product based on feedback. It not only saves you money but time as well.2. An MVP will bring focus to your core value proposition.Because an MVP brings restrictions when it comes to releasing entire sets of functionalities, it challenges you to think of the real problem the product is solving for its customers and the core value proposition of it.3. An MVP helps you verify the market demand.MVPs are renowned for helping business owners and startup founders test and validating their product idea. Bringing an ideology of only building core functionalities and being cautious with the money invested, and MVP will help founders achieve market fit while decreasing future investments in the product.4. MVP’s provide an ideal framework for iterating the UI and UX of your product.User Experience is crucial for the success of your product. Once you release an MVP on the market, you have the necessary amount of feedback to know what works and what doesn’t about the UX of your product.How to build an MVPBuilding an MVP started with a digital product idea that solves a real problem for its potential users. Once you have identified that you can start thinking of the functionalities of the web or mobile application you want to build.At appssemble, we created a software development process that guides us when building new products and provides a tried and tested framework for building mobile apps in an agile manner and lean-approach.1. Product StrategyProduct Strategy refers to the initial step of building any digital product. It is the right time to think of the problem your mobile or web app is solving for your customers, pitch your idea to friend and family and start collecting feedback, think of a monetisation plan, sketch your user persona and research your market. It’s important to make sure that the product you build not only collects data and delivers functionality but can also be used in your business’s economic advantage.2. Create user stories and flows of your mobile applicationOnce you have identified the problem you are solving for your users, and have a clear idea of your potential users, move on to creating the user stories and flows of your mobile application. A user story should define the action of a user together with the purpose of it, and most of the time it has a structure that is similar to this one:“As a [persona], I [want to], [so that].”Breaking this down:“As a [persona]”: Who are we building this for? We’re not just after a job title; we’re after the persona of the person. Max. Your team should have a common understanding of who Tom is. Make sure you understand how your personal works, how they think and what they feel. Have empathy for Tom.“Wants to”: Here you want to describe Tom’s intent — not the features they use. What is it that Tom is actually trying to achieve? This statement should be implementation free — if you’re describing any part of the UI and not what the user goal is you’re missing the point.“So that”: how does Tom’s immediate desire to do something this fit into his bigger picture? What’s the overall benefit he is trying to achieve? What is the big problem that needs solving?You can find out more about how to create user stories, here.3. Mobile App Wireframing & UX DesignHaving stated the user stories of your (mobile) application should give you enough information and structure to create a mindmap of the entire application flow.Start by sketching the screens of your application, translating user stories into features and screens. Most of the initial wireframing that is done at appssemble looks like this:After sketching the screens of your mobile application, we recommend having a UX designer help you translate everything into a digital format and give you input on your user flows.Once the UX phase is done, and you have your digital high fidelity wireframes in place, create a functional prototype to get an even better idea of the application flow. At appssemble, we use InVision a digital product design platform that helps with new digital product design.Remember that the UX phase is the best moment to iterate on the core functionalities and try out possible new ideas and concepts.4. UI DesignOnce you have agreed on the core functionalities of your app and have an agreed UX flow, you can move on to adding the brand to the User Experience.5. MVP Development (Coding Time)Exitiiiiing! It’s time to give life to your designs. Make sure you find a team of agile software developers that understand your business and know how to make technology work into your advantage while keeping the feasibility and scalability of your mobile application in mind.6. Launch!It’s time to get your product out in the world. Pay attention to the feedback your early users provide, as this will be the cornerstone for further development.Don’t forget to build, measure & learn.While building an MVP, one of the most essential principles you need to follow is the build measure and learn loop. After you launched your product on the market, keep an eye on how users interact with it and collect all the feedback needed to iterate and enhance your product.Curious to see some of the projects that we built and started out as MVPs? Go ahead and check out the appssemble mobile applications portfolio on our website.Struggling to keep yourself motivated during this time? Don't forget that despite everything happening, some of today's greatest startups have been founded during the 2008–2009 recession: Airbnb, Pinterest, Slack, Square, Uber + WhatsApp Inc. All it takes to create a digital product that gets to the heart of the customers is a little bit of attention to your market's current needs and struggles. Spot them and bring on the solution! --- ### What is possible in the realm of AI/ML on mobile applications? URL: https://appssemble.com/blog/what-is-possible-in-the-realm-of-ai-ml-on-mobile-applications Everything is possible, but if you’re just starting in this world, and you don’t have a large team of scientists and developers your options might be a little bit more limited. Luckily, there are a ton of resources and tools available that can be easily used in MVPs or already existing apps. You’re probably thinking of building an app that has an AI/ML component, or you might want to add an intelligent component in your already existing one, but what exactly is possible and how can you do it?IntroductionArtificial Intelligence and Machine Learning are popular terms nowadays which are spread all over the IT scene and there is a trend in trying to apply the concepts of those domains to everything related to IT (building apps, recommending movies, showing ads, finding the best time to travel from one place to another, etc.).Mobile phones are the devices that use AI and ML the most and I’m not talking about a single scope approach where AI techniques are used for solving a certain problem, in a mobile phone AI is used from the hardware (the custom AI chips) to software (Siri, picture taking, recommendations, natural language processing and many more).Now, what’s the difference between AI and ML?AI is the science and all the practices involved in making a computer behave in ways that we previously thought were only accomplishable by humans (such as playing Chess, driving cars, writing poems, etc.). ML on the other hand is a subset of practices in the AI domain that allow computer algorithms to improve through experience (for instance, categorizing music, recommending movies, giving diagnostics, and so on).In the realm of mobile applications, ML is one of the most common braches of AI in use, that is mainly because of hardware considerations (the computational power, energy efficiency, and storage) but not only, mobile phones are devices which are usually used by a single user for day to day tasks and they are meant to solve a multitude of problems not a single one. In addition to ML, there are a lot of other AI techniques used in mobile products such as Computer Vision, Computer Audio, Deep Networks, and so on, however, those are not that widespread.So what is currently possible from an ML perspective in the realm of mobile applications?Well, everything is possible, but if you’re just starting in this world, and you don’t have a large team of scientists and developers your options might be a little bit more limited. Luckily, there are a ton of resources and tools available that can be easily used in MVPs or already existing apps, I’m going to talk about a few of those today.IntegrationFirstly we need to talk about how those tools can be accessed, mainly there are two ways in which the tools can be used and accessedAPI based — those are usually external services that take some data as input and give you back a response based, all the processing happens on a server somewhere, and there is a need for an Internet connection to access those — so they don’t work for offline apps.Device-based — the algorithms and the AI models live on the device, those can be accessed and used usually offline but some of them require an Internet connection as well.There is a third model, which is a hybrid of the two enunciated above in which a model is downloaded periodically from a server, however, those cases are rare and are not that commonly used as the other two.Machine LearningML techniques are heavily used for image processing but not only, but they also apply to other domains (medicine, predictions, etc). The product of every ML algorithm is an ML model that can be used for solving a certain problem. One can think of an ML model as a blueprint for solving a certain problem, once we know how to do multiplication, we can apply the same operation to an infinite number of options.Training a modelBased on the user behavior, for instance, an app could learn from the user’s behavior which action he is most likely to do, an example would be a food ordering application that would make suggestions based on previous behavior (for instance recommend vegetarian dishes and restaurants if it’s lunch to users who eat vegetarian food for launch multiple times). The model and the algorithm is updated every time the user makes a choice, thus resulting in completely different app experiences for different users.The example above recommending the food based on previous orders can take into consideration multiple other parameters such as the period of the year, time of the day, the location of the user, what other users on the platform are trying out, and so on. A model is more than just doing some simple decisions, it can take into consideration a lot more parameters than the human brain and it can take really good decisions regarding what to recommend if it’s configured and build correctly, with high-quality data.For this sort of intelligent algorithm to work well, it needs the right data and it needs some time to learn until accurate predictions can be made. In addition to this, doing this on the user’s device can raise some privacy issues if the model or the data used to compute it leaves the device, so think about it carefully before deciding that you want to use it.Another approach is to distribute the same model for all the users of the app, a model trained to solve a certain, well-defined problem, for instance, identifying the season from the photos taken by the user. This can be achieved by training the model with either your data (if you have enough of it) or by using one of the data sets available on the web. You can find datasets in many domains, mainly used for academic purposes but not only, some examples of the sets available are:Food types setsDiagnostic for certain diseases setsLanguage setsVoices setsUsing a pre-trained modelKnowledge is power, most commonly nowadays data is power because no matter how good coders are your team, won’t be able to implement great ML algorithms without a large set of data that covers as many as the possible causes of the problem you want to solve. Unfortunately finding the right data to train your model can be hard, not only that you need correct data, correctly labeled and written in a consistent format, you also need a ton of it to make your algorithm performant.Luckily there is some good news as well, on the web you will find a lot of pre-trained models that you can use in your app, or even API’s that expose some trained models for solving certain issues as:Recognizing the main object from an imageRecognizing the people, faces, and body parts and body poses from an imageRecognizing brands, names, texts, or food (including the type) from an imageFinding the answer to a question in a textAnother class of intelligent algorithms is the Natural Language Processing which handles text and audio (containing someone speaking) to extract certain content from the analyzed phrases or sentences. This is a central piece in software such as Siri, Alexa, Google Assistant.The good news is that a lot of tools are available that can process natural language data and extract with high accuracy different information such as:The language of the data (English, Deutch, French, etc.)Identifying parts of speech (noun, verbs, adjectives, numbers, pronouns, and many others)Identifying punctuationIdentifying businesses or organization namesFinding similar words or sentencesTraining models for identifying custom items such as names of products, sports rules (ex. offside, goal, handball, etc)Analysing the sentiments of a text (positive, negative, etc.)As you can see, with the aid of those tools we can easily build more complex and intelligent systems, for instance, an app that could take voice commands for completing certain actions, or modifying the score table while watching a football game in the app by only analyzing the sound of the commentators.Please note that we haven’t talked about AR/VR techniques and tools even though they heavily use AI and ML techniques, they will make the subject of a future article. --- ### Augmented & Virtual Reality (AR/VR) in mobile apps URL: https://appssemble.com/blog/augmented-virtual-reality-ar-vr-in-mobile-apps A new platform comes every decade, the smartphone simple client golden era has passed and now makes way for other mediums where the user can be more engaged and the experiences more immersive. A new platform comes every decade, the smartphone simple client golden era has passed and now makes way for other mediums where the user can be more engaged and the experiences more immersive. I’m talking of Augmented and Virtual Reality technologies, of course, as all the big technology companies (Apple, Google, Facebook, Amazon, Microsoft) have made serious commitments to developing new technologies in this domain.Mobile applications are still our most personal and most used device, today we have over 2 billion mobile devices that support AR experiences and the number is increasing, as every new smartphone has AR/VR capabilities. The hardware is advancing constantly (eq. Apple’s new LiDAR sensor) as well as the software (new development kits), making it easier to integrate AR experiences in the apps.AR is being used in a lot of domains already, for instance in the E-Commerce sector where shoppers are more inclined to purchase a product after they’ve inspected it with AR technologies or social apps where besides filters, the users can also add AR objects in their streams. Another domain in which AR is popular is the indoor or outdoor navigation solutions where directions are easier to be followed if they are placed in a real-world environment.Big corporations also use AR/VR either for education or to showcase different tech features of their product, for instance displaying different motor parts or how a certain hardware component works. AR is also used in medicine, for instance, the patients who need to do recovery exercises can speed out their recovery time by also practicing at home with the aid of an app.Due to the current state of the world, the education system is changed, new technologies are used for conveying knowledge and AR does a really good job in this domain as well, as it creates more engaging experiences without necessarily being in a classroom.The big technology companies are all working on smart glasses to augment our real experiences but in the meantime, our way to the future is still through the smartphone.So what is the current status quo in terms of what’s possible from an AR/VR point of view on mobile devices?AI is the science and all the practices involved in making a computer behave in ways that we previously thought were only accomplishable by humans (such as playing Chess, driving cars, writing poems, etc.). ML on the other hand is a subset of practices in the AI domain that allow computer algorithms to improve through experience (for instance, categorizing music, recommending movies, giving diagnostics, and so on).In the realm of mobile applications, ML is one of the most common braches of AI in use, that is mainly because of hardware considerations (the computational power, energy efficiency, and storage) but not only, mobile phones are devices which are usually used by a single user for day to day tasks and they are meant to solve a multitude of problems not a single one. In addition to ML, there are a lot of other AI techniques used in mobile products such as Computer Vision, Computer Audio, Deep Networks, and so on, however, those are not that widespread.So what is currently possible from an ML perspective in the realm of mobile applications?Virtual RealityIn terms of virtual reality, there are a lot of developments from both Google and Facebook where they created special goggles or devices to be attached to mobile phones for experiencing virtual worlds. Complex scenarios still require a lot of processing power, and they are usually used in games and those devices are most popular with kids.In VR worlds, the users usually have additional devices (joysticks, etc.) for interacting with virtual objects. Since we are talking about mobile applications, VR is not that popular and used due to the nature of the device (doesn’t have a lot of power, and additional controllers).Augmented RealityHere, things are a little more evolved, and while companies are interested in VR technologies, a lot more budget and development go into mobile AR at the moment.In essence, augmented reality is adding digital content to real-world anchors and being able to analyze the environment of the user.From an AR perspective, we currently have the capabilities to do the following:placing a virtual object in the real world (it will remain at the same location)scaling, rotating, moving, and animating virtual objectsinteracting with virtual objectsmeasuring real objects through virtual anchorssound effects based on the proximity of the sourceAR is closely related to AI, it’s used a lot in combination with AI techniques to modify the user’s environment and interact with him. An example would be the recovery app I’ve mentioned before where AI would be used to detect the human body pose and AR would enhance the experience by showing different metrics or what needs to be improved to correctly do the exercise. To learn more about AI/ML, read our previous article.From an AR perspective, we also have new sensors (most specifically the LiDAR), which can scan the environment with a higher accuracy making the object placing faster, easier, and more accurate.Smartphones open the doors and the path to a new platform that is yet to emerge and are here to stay. There are a lot of possibilities in this domain and technological advances constantly open new possibilities. Just like in the years that followed the release of iPhone the market of mobile apps has exploded, this is what will happen with the AR and VR apps as well.Do you have a mobile project which could benefit from AR or VR, or have general questions regarding those technologies on mobile devices? Drop us an email, and let’s discuss more! --- ### How going MVP-first can save your startup a lot of money. Market validation for startups. URL: https://appssemble.com/blog/how-going-mvp-first-can-save-your-startup-a-lot-of-money-market-validation-for-startups What makes the differences between unicorns and startups that end up failing, and why do some of the startups fail? We are taking you through some of our best practices when it comes to building and launching mobile startups. In our work of building digital products for startups around the world, we get to see how a lot of them thrive, while others fail. But what makes all the differences between unicorns and startups that end up failing, and why do some of the startups fail? In this series of articles, we are taking you through some of our best practices when it comes to building and launching mobile startups.42% of startups fail because there is no market need, 29% because they run out of cash, and 19 % of startups fail because they can’t build the right digital product team. There are many other reasons to add to this thread, but for now, let’s keep our focus on the first one — 42% of startups fail because there is no market validationWhat is market validation?Market validation is a process that helps you determine whether your product is of interest for your market. It starts with writing down your app concept, conducting a series of interviews with potential users, and lastly, testing the market with aMinimum Viable Product.At appssemble, we created a digital product development process that covers the entire flow of building and shipping digital products, from product strategy and business analyses to launch and maintenance, while offering businesses a trusted way of validating their new product idea. Having a process in place is a great way to make sure there’s a tried way of building startups, but since there’s no universal success recipe, we often have to put our process aside, adapting to specific product needs and scenarios.The solution.The business analyses phase of building a digital product should start with writing down the product concept. Find a pen and a piece of paper, and start writing down your answers to these questions:Who is my customer? — We hope your answer won’t be everyone because if it is, we are in big trouble. When it comes to gathering data about your potential customers, there is no such thing as getting too specific. Just make sure you are collecting all relevant information about your prospective users in one place.At appssemble, we like to have what we call a creative mind-melting session with our clients. We sit, talk and document all details about their users in complex user persona profiles. We pay extra attention to address their pain points and how the digital product we build can solve their problems.There are several tools you can use to start creating your user persona profiles right now. Make my persona from HubSpot is one of the tools we recommend the most.What problem am I solving for my customers? - In our jobs, we often see entrepreneurs fret about the features they are launching and taking the decision with a product-first mindset, then spending time thinking why their product is not getting any traction. You now know who your customer is, so our advice is to think of the problem you are solving for your customer first. If you can’t put your finger on your customer’s problem, you won’t succeed in solving it. Look at it from a user standpoint and make sure your customer sees value in having this problem solved.How does my product solve the problem? Only after defining the problem you are addressing, you can move on to discussing the product. You want to translate the solution you provide to your users into functionalities that will be integrated into your app — which brings us to another important thing.Choosing to build an MVP.A minimum viable product is the first version of your digital product, containing a minimum amount of features to delight users and collect valuable feedback from the market. At appssemble, we like to call it Minimum Lovable Product because besides validating a need and helping you get valuable feedback from the market, an MVP should also get to the hearts of your users.In our effort to reach market validation with the digital products we build, we often advise stakeholders that work with us to go MVP-first. This means that when we sit and look at the product they want to develop, we prioritise on the features that are the core of the app, cutting down on all those bits and pieces that don’t necessarily influence the market-fit aspect.We like to think of the MVP as a great way to test all the assumptions you made about your clients while in the strategy phase, and to evaluate the value customers assign to your product. If you are keen on following a build-measure-learn loop and resist the urge of adding new features to your product before even testing what you first put on the market, you’ll soon find our how going MVP first can save you a lot of money.Take a quick look at some of the mobile apps built by appssemble that started out as minimum viable products.Product development does not end after launch.An important phase in your process of reaching market validation is getting the app you build into the hands of the users, as soon as possible. Once the product is out there, you are standing face to face the with the opportunity to improve your product.Pay attention to their reactions and pain points, make sure that the entire user experience makes sense for them, and be fast when it comes to improving the app. --- ### A step-by-step guide into how we built a $ 1M calorie counting & diet mobile app in less than four weeks. URL: https://appssemble.com/blog/a-step-by-step-guide-into-how-we-built-a-1m-calorie-counting-diet-mobile-app-in-less-than-four-weeks We present a walk throughout the process of building a counting calories app that received funding offers in the first month after its release. We tackle every step of the process from idea to design and implementation. Aical helps users keep track of their daily nutrients intake and adjust their diet. With aical, you don’t have to fill unfriendly forms and search for your food to monitor your nutrients intake. The artificial intelligence algorithms within the calorie counting app, estimate your intake of calories, fat, carbs, proteins, and fibre from just seeing a photograph of your meal. All you have to do is snap a picture of your food, scan a barcode from a product you are consuming, or tell Siri what you ate. Simple as that.We started building aical with the aim of creating a calorie counting & diet application algorithm that would deliver nutrition reports, better and faster. We went MVP-first, with the goal to develop a mobile application that would provide the best experience for the users while collecting the user feedback from the market to validate our idea. We invested over $50K in building the first version of the mobile app. Within three weeks, we had already had buying offers ranging $230K. Here’s a look into how we did it:Help people create a healthy lifestyle while keeping track of their diet.The challenge.Aical was envisioned as simple to use, and human-centric mobile application that keeps track of your calories throughout the day. Since we were building a subscription-based business model, we knew we had to make it as simple as possible to use, so as to perfectly blend into the lives of our users. Hence, we took a daily activity like taking pictures and snapshots with your mobile phone and taught of making it the core of the application. As a user, you could take a picture of your meal and the algorithm would interpret the portion size, ingredients and nutrients for you. Easy, huh? Yes, but then we took pictured out our soups and realised how much of a challenge it is to be able to extract exact information on the ingredients in a soup bowl. Another problem we identified was that besides the main meals, users frequently enjoy a small snack during their day.The solution.At this point, we knew we had to come with a few other solutions for logging food into the calorie counting mobile app. Thinking of the many life scenarios users could be in while enjoying their meal, we came up with more ways of keeping track of calories and nutrients: scanning the bar code on a product, manually logging your food, and telling Siri what you ate.Building aical, the AI-powered calorie counting & nutrition iOS app.Mobile App Business and Product Strategy. We started with the business-critical side of the calorie counting & diet mobile application. Although the problem we aimed to solve was pretty clear from the very beginning, we wanted to be sure that before getting into building the app, we have a clear vision of the buyer personas, as well as real-life scenarios of users interacting with the mobile app.Moving on to the functionality side of the application, we went through a feature prioritisation phase, in which we created a roadmap of all the features the minimum viable version of the digital product would contain.We brought the platform we were going to make the first release on into discussion and looking at a few stats, numbers and the users we are going to target, we decided to go iOS first.UX Design & Mobile Prototyping. Having the users personas of the mobile applications defined, provided a robust framework for creating the user flows and engineer pathways for users to interact with the application. We started with paper and pen, sketching all the app scenarios we could think of, on paper.UI Design. Following the same principle of simplicity, we aimed to offer aical a clean look. We used white and black, with pink as an accent colour.Mobile App Development & Testing. The development of the aical mobile app lasted for about one month. Following an Agile approach and building in a Lean manner, development was done in one-week sprints. The architecture of the mobile app paid a great deal at this stage. We had a cross-functional team of designers, developers and testers continuously collaborate and iterate on the app functionalities.Launching aical. Before getting the mobile into the App Store, we made sure to have the right analytics tools in place, craft an eye-catching description and make sure we have a bug-free mobile application, ready to interact with the users. We launched a few advertisement campaigns, and the first month of having aical on the App Store brought us, 9000 users, out of which 150 were premium subscribers.Takeaways.Taking a quick look at a few numbers, you see that 40% of new startups and digital product fail within their first month of activity. The same numbers tell use that few startups reach market validation in their first days of activity. Building aical showed us how if you are looking to reach a high ROI with your app, going MVP first and testing the idea with the core functionalities of a mobile application can save you loads of money. It gave us a better understanding of how to get the most out of the data your app collects and to make sure that the money we invest in building aical is solving real deal problems for our users.Looking to build your next mobile app? We hope that this story of how we build a $ 1m calories counting mobile application inspires you to bring your idea to life and launch a new product on the market.