The framework and design is almost done an I’m moving to launch on web only MVP to test if this is a viable product. I’m wondering if I should create three separate projects of the same thing and design each one to meet the needs of the different platforms (iOS, android,web) I can see a few problems with this approach but am wondering if there are benefits.

  • What’s your dev stack, hosting & front/backend?

    parent

  • it does depend on your framework/project's expected production environment.. but .. its fairly easy to whip up an SPA -- Single page app -- that can handle things like retrieving data from external places -- extra step, but, good work around for a quick publish. what i have personally found to be easiest -- make everything i need published as mobile apps in app store or something as a PWA-- you should have your ai make your project into a PWA --Progressive Web App-- ensuring universality across device types, with all necessary facets to make it fit screens correctly by default, update everywhere when i change something, and doesnt require more than the 1 codebase.

    parent

  • It would be harder to work on as a vibe codex project, depends on you and how different you want each, how you redo code across projects...

    If this was a big enterprise project it would have a had a "core" project with anything in common and/or specs and such that are cross project comms... It's a lot of extra work to do this right, it sounds good on paper, but it's a ton of work. Google famously has a mono repo for everything, suppose. Some things become easier and faster like CI many things become slower, more work

    parent

  • Most teams keep a single domain model and backend while allowing platform-specific UI layers to diverge only when UX constraints force it

    parent

  • Web first is usually the right call for quick validation. Are you planning to add React Native or something cross platform after the MVP proves out?

    parent