Now Modelence App Builder has support for creating native mobile apps. Just like web apps, describe what you want and get a fully working mobile app, working in sync with your Modelence auth and backend.
Replies
Best
Appreciate the straight answer, most tools in this space quietly pretend the last mile doesn't exist. EAS getting you to a real signed build is the bulk of the pain gone. The one thing I'd keep watching for AI-generated apps is App Store review itself: Apple's 4.2 minimum-functionality rule tends to flag apps that read as too templated or thin. Does the generated output vary enough structurally to clear that, or is dodging it mostly on the person doing the customizing?
@dipankar_sarkar good point, the UI and visuals are custom generated for each app, and while there may be some general patterns, there is no single template that keeps repeating.
Report
How does the generated code stay maintainable when you need to add something the prompt didn't anticipate, do you end up rewriting large parts of it?
Same prompt generating both web and native from a shared backend is the part that stands out - most builders treat mobile as a bolt-on. Since it's real code on an open framework, what happens when someone hand-edits the native app directly and then goes back to prompt a change - does it merge cleanly or is that where things get messy?
Replies
Appreciate the straight answer, most tools in this space quietly pretend the last mile doesn't exist. EAS getting you to a real signed build is the bulk of the pain gone. The one thing I'd keep watching for AI-generated apps is App Store review itself: Apple's 4.2 minimum-functionality rule tends to flag apps that read as too templated or thin. Does the generated output vary enough structurally to clear that, or is dodging it mostly on the person doing the customizing?
Modelence App Builder
@dipankar_sarkar good point, the UI and visuals are custom generated for each app, and while there may be some general patterns, there is no single template that keeps repeating.
How does the generated code stay maintainable when you need to add something the prompt didn't anticipate, do you end up rewriting large parts of it?
Loomal
Same prompt generating both web and native from a shared backend is the part that stands out - most builders treat mobile as a bolt-on. Since it's real code on an open framework, what happens when someone hand-edits the native app directly and then goes back to prompt a change - does it merge cleanly or is that where things get messy?