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
Sharing one codebase and backend between web and mobile from a single prompt is the part that would actually save time, most "AI app builder" mobile support I've seen is really a wrapped webview. Since it's on Expo, does the builder handle the native module gaps that Expo doesn't cover out of the box, and can it get you to a signed build ready for TestFlight/Play internal testing, or does that packaging step stay manual?
@galdayan Good eye, and yes, that is exactly the difference: it is real native via Expo/React Native sharing one codebase and backend, not a webview wrapper.
On packaging: we use EAS to build and store the submission, so most of the pipeline is automated and you do get to a build. The last steps for signing and publishing (especially to the App Store) still need some manual work, but Modelence handles most of the flow around it, so it is not a fully manual packaging step
Report
The Expo choice is smart, that's the fastest path to real iOS and Android from one codebase. The question web builders never have to answer but mobile ones do: where does the wall hit at ship time? Getting to a running app in Expo Go is the easy part, getting through signing, provisioning profiles, and App Store review is where most no-code mobile tools quietly hand you back a raw project. Does Modelence take you through EAS build and store submission, or stop at the code?
@dipankar_sarkar Good question, and it is exactly the wall most no-code mobile tools hit.
Modelence takes you through EAS build and store submission, not just the code. The build, provisioning, and submission pipeline is automated through EAS, so you get to a real build rather than a raw project. The one place it is not fully hands off is the final signing and publish, especially App Store review, which still needs a few manual steps (Apple keeps that gated no matter what). But everything leading up to it is handled, so you are not dropped at the code and left to figure out the rest
Report
The generated code actually looked like something I'd write myself, not a mess I'd need to rewrite from scratch. Deploying from the prompt was honestly the part that surprised me most.
@uyanbal77090 Deploying straight from the prompt is one of the fun features, glad you noticed and liked it 🙌
Report
Spun up a quick project to test it and the auth and database were already wired together when the build finished. Nice surprise that I could actually poke around the generated code instead of it being a black box.
Love that the generated code is actually inspectable and editable instead of trapping you in a black box, that ownership angle feels rare in this space.
Built a small side project in like 10 minutes and was honestly surprised the auth and db hooks just worked without me babysitting them. Code was clean enough to actually tweak afterward.
Finally an AI app builder that doesn't leave me stranded on the backend. Prompted a full-stack app and got auth + DB + monitoring wired up from day one. Code is clean TypeScript, no black box. Still early but this actually feels production-ready, not just a demo.
Congrats on the launch! 🚀 One question, if I generate an app with Modelence and later decide to host it on my own infrastructure, how easy is it to migrate? Is it completely vendor-independent, or are there any Modelence-specific dependencies?
@vikranth_reddy_bollam you can deploy the code anywhere; the code of your application is in a single monorepo, and it runs in 2 commands (both locally and on any other infrastructure). There are no hard dependencies, but there are some Modelence cloud services that your application might use: at this point, we have an email service (for sending emails) and cloud storage. Both are interchangeable with alternatives; we created them for convenience so you don't have to pay for multiple third-party tools.
Congrats on the launch, Aram, Eduard, and team! 🎉 I put the builder through a real test this week — described a CRM pipeline tracker, and it came back with auth, MongoDB, and a working kanban board already wired together. Then one Publish click and it was live on a production URL. As someone who built and sold a SaaS before, that last step is the one that matters — most tools hand you a prototype and wish you luck. This one ships. Excited to see mobile get the same treatment.
Replies
Sharing one codebase and backend between web and mobile from a single prompt is the part that would actually save time, most "AI app builder" mobile support I've seen is really a wrapped webview. Since it's on Expo, does the builder handle the native module gaps that Expo doesn't cover out of the box, and can it get you to a signed build ready for TestFlight/Play internal testing, or does that packaging step stay manual?
Modelence App Builder
@galdayan Good eye, and yes, that is exactly the difference: it is real native via Expo/React Native sharing one codebase and backend, not a webview wrapper.
On packaging: we use EAS to build and store the submission, so most of the pipeline is automated and you do get to a build. The last steps for signing and publishing (especially to the App Store) still need some manual work, but Modelence handles most of the flow around it, so it is not a fully manual packaging step
The Expo choice is smart, that's the fastest path to real iOS and Android from one codebase. The question web builders never have to answer but mobile ones do: where does the wall hit at ship time? Getting to a running app in Expo Go is the easy part, getting through signing, provisioning profiles, and App Store review is where most no-code mobile tools quietly hand you back a raw project. Does Modelence take you through EAS build and store submission, or stop at the code?
Modelence App Builder
@dipankar_sarkar Good question, and it is exactly the wall most no-code mobile tools hit.
Modelence takes you through EAS build and store submission, not just the code. The build, provisioning, and submission pipeline is automated through EAS, so you get to a real build rather than a raw project. The one place it is not fully hands off is the final signing and publish, especially App Store review, which still needs a few manual steps (Apple keeps that gated no matter what). But everything leading up to it is handled, so you are not dropped at the code and left to figure out the rest
The generated code actually looked like something I'd write myself, not a mess I'd need to rewrite from scratch. Deploying from the prompt was honestly the part that surprised me most.
Modelence App Builder
@uyanbal77090 Glad to hear that!
Modelence App Builder
@uyanbal77090 Deploying straight from the prompt is one of the fun features, glad you noticed and liked it 🙌
Spun up a quick project to test it and the auth and database were already wired together when the build finished. Nice surprise that I could actually poke around the generated code instead of it being a black box.
Modelence App Builder
@agackesen72622 Thank you for the feedback
Love that the generated code is actually inspectable and editable instead of trapping you in a black box, that ownership angle feels rare in this space.
Modelence App Builder
@kaan_uzune6287 Thank you for the feedback!
Love that it gives you the code instead of hiding it behind a black box, that's a really thoughtful choice for a builder like this.
Modelence App Builder
@kumsalukh1 Thank you for the feedback!
Built a small side project in like 10 minutes and was honestly surprised the auth and db hooks just worked without me babysitting them. Code was clean enough to actually tweak afterward.
Modelence App Builder
@nazmiye6byt Thank you for the feedback!
Finally an AI app builder that doesn't leave me stranded on the backend. Prompted a full-stack app and got auth + DB + monitoring wired up from day one. Code is clean TypeScript, no black box. Still early but this actually feels production-ready, not just a demo.
Modelence App Builder
@rick_borduur Thank you for the feedback!
Congrats on the launch! 🚀 One question, if I generate an app with Modelence and later decide to host it on my own infrastructure, how easy is it to migrate? Is it completely vendor-independent, or are there any Modelence-specific dependencies?
Modelence App Builder
@vikranth_reddy_bollam you can deploy the code anywhere; the code of your application is in a single monorepo, and it runs in 2 commands (both locally and on any other infrastructure). There are no hard dependencies, but there are some Modelence cloud services that your application might use: at this point, we have an email service (for sending emails) and cloud storage. Both are interchangeable with alternatives; we created them for convenience so you don't have to pay for multiple third-party tools.
Modelence App Builder
Congrats on the launch, Aram, Eduard, and team! 🎉 I put the builder through a real test this week — described a CRM pipeline tracker, and it came back with auth, MongoDB, and a working kanban board already wired together. Then one Publish click and it was live on a production URL. As someone who built and sold a SaaS before, that last step is the one that matters — most tools hand you a prototype and wish you luck. This one ships. Excited to see mobile get the same treatment.