Internal
Competitors
Who OneDrop competes with, what they build on, how they do mobile, and where OneDrop differs.
Who OneDrop competes with, what they build on, how they do mobile, and where OneDrop differs.
Internal. This page is hidden from the docs navigation and search. The facts about other products are from memory as of October 2026: re-check them before quoting them anywhere public. The decisions behind it are in REQ.md under Competitors.
The main fight: someone describes an app and gets a running one.
| Product | Web app | Backend | Mobile |
|---|---|---|---|
| Lovable | React + Vite single-page app | Supabase | None, or a PWA |
| Bolt.new (StackBlitz) | React/Vite and others, run in the browser (WebContainers) | Supabase, Bolt Cloud | Expo (React Native) |
| Base44 (owned by Wix) | React + Vite single-page app | Its own: data, auth and Deno functions behind an SDK | Not Expo: its own native web-view shell that opens only the published app’s URL. The editor builds the IPA and AAB and you upload them yourself (Builder plan and up). Web changes ship without a store update. No offline mode, HealthKit or in-app purchases (docs, checked 2026-10-04) |
| Replit Agent | Any stack, in a real sandbox | Its own database and hosting | Expo, published with EAS |
| v0 (Vercel) | Next.js | Vercel and its integrations | None |
| Google AI Studio “Build”, Firebase Studio | React, from Gemini | Cloud Run, Firebase | Firebase Studio can do Flutter |
Smaller ones: Create.xyz/Anything, Same.new, Tempo, Softgen, Mocha, Rocket.new, Emergent, Macaly, Figma Make.
Pattern: nearly all of them generate a client-only React app that talks to a hosted backend through an SDK. Mobile then comes almost free, because the same SDK runs in an Expo app or a wrapped web app.
Rork, a0.dev, Vibecode and Bolt’s mobile mode. All of them build Expo apps: models write React Native well, and EAS handles signing and store submission.
Claude Code on the web, OpenAI Codex, Cursor background agents, Devin, GitHub Copilot coding agent, Jules. They’re aimed at developers, run in sandboxes you can’t reach, and hand back a pull request or a screenshot, never a live app you can use while it’s being built.
The closest threat to the self-hosting pitch:
Most are tied to one stack, run only on your own machine, or have stalled.
Dokploy, Coolify, CapRover, Railway templates, Render, Fly. They compete with hosting and remixing open-source apps, but assume you know DevOps. OneDrop adds the agent on top.
The default app is Inertia + Laravel, chosen as the more responsible stack: one app to deploy and run, no API layer, each page’s data in its first HTML response, and server routing gives the agent fewer places to break things. A mobile-first Expo app on a Laravel API was ruled out for that reason. The cost is that Inertia pages have no JSON API for a native app to call.
Decided (not built yet): every app is an installable web app (PWA) by default, and a native store app is a mode the user turns on, using the preferred route below. See REQ.md → Competitors for the details.
Ways to add native mobile:
| Route | How it works | Trade-off |
|---|---|---|
| Expo + a Laravel API (preferred) | The agent adds an Expo app and routes/api.php with Sanctum beside the Inertia pages | Real native apps, as Replit and Bolt make; one codebase and one deploy |
| Capacitor shell | A native app that loads the deployed web app | Least work, works with Inertia as it is, but Apple rejects apps that are only a website (guideline 4.2) |
| NativePHP for Mobile | Bundles the Laravel app and PHP onto the device | Best fit for Laravel, but new and hard to run in a sandbox |