Solo dev, native app on both stores, Claude as the main developer: the rules I wrote after it handed me empty functions
retained text
I'm Cesare. I come from IT, but before this project I had never built a mobile app. For about ten months I've been building orbiTome alone: an app to organize outings with people you know. You drop a marker on the map, invite your friends, meet there. It's live on iOS and Android in 5 languages, free to download with optional in-app purchases. How the work is split. I use FlutterFlow for the screens and Firebase for the backend. Claude writes most of the custom code: the Dart actions and widgets inside FlutterFlow, the Cloud Functions, the database rules. I decide what to build, I test on real phones and I check what comes back. What went wrong. Early on I trusted it too much. One day I got a file with the notification functions that looked complete. The functions were empty. I caught it before the deploy. From there I started writing dated rules into a handoff document that every new chat reads first: - Code always comes from the latest project export, never from what the model remembers from earlier in the chat. - A function counts as delivered only when something outside it calls it. - A backend change counts only when I see it in an export made after the deploy. - Files that hold everything, like translations and app state, are rewritten whole: full copy checked before, reread after. - Deploy order is fixed: database rules, then indexes, then functions, then app code. The handoff document matters more than any single prompt. Each chat starts from it, not from my memory or from Claude's. What I'd like to compare: how do you stop the model from building on a version of the code that no longer exists? Do you keep a handoff file too? https://www.orbitome.com/?utm_source=reddit&utm_medium=post&utm_campaign=claudeai
document fetched 2026-11-19 00:23 · canonical https://reddit.com/r/ClaudeAI/comments/1xzavme/solo_dev_native_app_on_both_stores_claude_as_the