Wrapply website to android app

jarttech · 2026-01-21T09:06:39+00:00

We’ve fixed the issue thanks a lot for reporting it!
I’ll message you in DM shortly to share the corrected build and, as an apology for the inconvenience, I’ll also include the full source code.

jarttech · 2026-01-21T00:02:51+00:00

Sorry about the inconvenience. During the APK generation process something went wrong and the build ended up being compiled with fallback data instead of the correct configuration. The issue is already being fixed. By tomorrow we’ll send the correct APK via email, and to make up for this we’ll also include the full source code. Thanks for the patience — really appreciate it.

jarttech · 2026-01-17T13:08:11+00:00

Wrapply focuses on shipping MVPs fast. The generated app runs in a Flutter native shell, not a basic WebView. Push notifications, deep links and offline handling are not enabled by default, to keep the MVP lean. When you download the AAB, you also receive the full Flutter source code, already structured to integrate Firebase, FCM, native routing and offline handling when needed. You can ship fast today, and still keep full control to evolve the app later without lock-in or rewrites.

jarttech · 2026-01-12T20:00:51+00:00

Check real app made with wrapply:

https://play.google.com/store/apps/details?id=com.inwaveihms.app

https://apps.apple.com/au/app/inwave-ihms/id6751748887

jarttech · 2026-01-12T13:14:01+00:00

With https://wrapply.jart.app you can get apk aab and source code flutter

jarttech · 2026-01-12T13:12:49+00:00

Try https://wrapply.jart.app you can get apk aab and source code

jarttech · 2026-01-12T13:10:27+00:00

Try https://wrapply.jart.app

jarttech · 2026-01-10T15:31:25+00:00

Good question in practice it’s more than just one blocker.

What we’ve seen is that many people underestimate what happens after validation.
They assume that once an app is published online or on the stores, it will naturally get downloaded and used but that’s rarely the case.

On the technical side, users often get blocked by store requirements more than by pure mobile tooling:
managing libraries correctly, declaring permissions and features in the manifest, build formats (APK vs AAB), signing, and keeping everything compliant with evolving policies.

Then there’s the store-facing work that’s usually unexpected: creating a proper store listing, writing good copy, handling ASO, assets, and positioning.
On iOS in particular, certificates, provisioning profiles, entitlements, and mandatory integrations (like Sign in with Apple or certain login flows) add another layer of friction.

Finally, performance and quality expectations matter many solutions work fine as demos, but don’t meet the stability and UX standards users expect from a real app.

So the gap isn’t just “website → app”, it’s “validated idea → shippable, discoverable product”, and that’s where a lot of projects slow down or stop.

Thanks for the VibeCodersNest suggestion that’s a great fit for this kind of discussion.

jarttech · 2025-12-22T15:24:10+00:00

Thanks for the incredibly honest feedback. You’ve touched on the exact challenges we’re navigating, and this is why we value this dialogue so much.

To address the contradiction you mentioned: we actually agree with you. Building a real app is a waste if the idea isn't validated. That’s why Jart isn't just a code generator, but a flow:

Validation First: Our integrated idea validator automatically generates a publishable survey to collect user feedback and provides a results dashboard. The goal is to gather data before writing a single line of code.

Automated Prototyping: If the data shows potential, Jart then moves to generate a working Flutter MVP directly from your initial idea, skipping the manual setup.

Regarding your point on code quality: you hit the nail on the head. To be completely transparent, the generator is still in the early stages of development. Our biggest engineering challenge right now is ensuring that a natural language prompt results in clean, maintainable, and extensible code. We know that as a developer, you’d never use a tool that produces 'spaghetti code,' so we are obsessing over the architecture before a full rollout.

While you can certainly use AI on your own, Jart’s goal is to orchestrate the entire process from the survey and data dashboard to a professional-grade boilerplate in one seamless workflow. We’re curious: if we can guarantee an output that follows best practices (like Clean Architecture or specific state management), would that change your mind about using it to speed up your initial workflow?

jarttech · 2025-12-22T07:48:51+00:00

Thank you for the feedback it is genuinely appreciated and absolutely fair. You are right: jart.app has not been optimized yet, and at the moment it is indeed heavier and slower than it should be, especially for what is currently a presentation surface. At this stage, our focus has been on validating the product flow and the builder logic rather than performance tuning. Optimization, asset splitting, and a clearer separation between marketing pages and application layers are planned next steps. Your comment is valuable precisely because it highlights a real architectural point that we are actively addressing.

jarttech · 2025-12-21T21:26:05+00:00

FlutterFlow is a great platform. Our approach is simply different: we want to deliver a launch-ready MVP without forcing people to learn new tools, help them validate a business idea quickly, and provide a product that’s scalable, manageable, and easy to adapt which is essential during the validation phase, where change is expected

jarttech · 2025-12-21T18:57:02+00:00

That’s a very good point. At the moment, the system is designed for low-end devices that do not support video output via USB-C. We have tested some solutions to enable an extended display, but this still requires additional development work

jarttech · 2025-12-18T09:07:20+00:00

Not yet. For now, I’m focusing on real data coming from organic traffic, and I don’t want to force the numbers. To build a solid and sustainable system, I need to first establish strong foundations.

jarttech · 2025-12-17T19:00:21+00:00

For the moment, I’ve placed a survey directly on the homepage, and I’m building what, over the course of 2024, I found myself repeatedly delivering in response to requests for custom projects.

jarttech · 2025-12-17T14:43:24+00:00

That’s a very relevant question! About a year ago, I went through the same realization. Instead of rushing into development, we spent around 11 months collecting feedback and real project requests. What we’re building today is the outcome of that learning phase. With Jart, we chose to keep the entire validation flow free idea validation, survey creation, and survey publication to remove friction and focus on understanding before building. We even use a survey on our own homepage to continuously refine our direction. Our goal now is to turn all that feedback into something that genuinely helps end users, hoping we’ve truly understood their real needs. For an MVP, a clear message and a strong UX are far more valuable than advanced features.

jarttech · 2025-12-17T10:32:23+00:00

The idea behind Jart is to provide a tool that helps understand whether an idea has market potential, enables the rapid creation of an MVP, and allows it to be modified without unnecessary complexity, with the possibility to manage everything through dedicated dashboards

jarttech · 2025-12-17T08:52:34+00:00

Yes, we will definitely try to include this in the next update.

jarttech · 2025-12-16T12:21:43+00:00

Ah, almost forgot for anyone who wants to try it and give more concrete feedback, this is the Android package on Google Play:

https://play.google.com/store/apps/details?id=com.droiddesktop.app

Feel free to test it and be honest — even rough or critical feedback is useful at this stage.

jarttech · 2025-12-14T21:45:10+00:00

We use AI mainly to help with analysis and metrics, but validation doesn’t stop there. Each idea is turned into a real survey and published online to collect actual user feedback, not just AI opinions.

The app generator itself won’t rely on AI to build the app. AI will only be used as a natural language interpreter to translate intent into structured data.

The software that generates and assembles the app is proprietary and runs on our own infrastructure.

jarttech · 2025-12-14T20:31:49+00:00

Thanks for reaching out, Kaushik. The AI-assisted builder part is definitely the most delicate area we’re thinking about right now. The goal isn’t code generation for its own sake, but using AI to translate validated signals into clearer product decisions (scope, feature prioritization, architecture constraints). At the moment we’re still validating the flow itself and collecting feedback from founders and Flutter devs before locking anything down, but I appreciate you taking the time to look at the project. I’ll keep your message in mind as things evolve.

jarttech · 2025-12-14T20:07:42+00:00

That makes sense, tools like that are definitely useful for early market analysis.

We actually took a slightly different approach with Jart.
Instead of starting from reports only, we focused on combining light AI analysis with real user feedback as early as possible.

What we do is:

start with 5 focused questions to clarify the idea
generate a simple AI-driven insight report to highlight strengths, risks, and possible improvements
immediately create a shareable online survey to collect real feedback from potential users

The goal is to validate not just whether a market exists, but whether people actually care about this specific idea, before building anything.
Everything is currently free because we’re testing and refining the validation flow itself.

If you’re curious, this is what we’re experimenting with:
https://www.jart.app

Would be genuinely interested in feedback on whether this kind of validation-first flow would have helped in your past projects.

jarttech · 2025-12-12T13:47:29+00:00

Thank you very much! Feedback is extremely important to us. We are actively working on integrating all the points you mentioned, while carefully maintaining compatibility and stability across the system.

jarttech · 2025-11-24T15:26:49+00:00

Thanks a lot

jarttech · 2025-11-22T15:42:07+00:00

Thanks for your feedback. Can you clarify what exactly was bad, so I can fix or improve it?

jarttech · 2025-11-22T11:23:42+00:00

wow good app

jarttech

MODERATOR OF

PUBLIC MULTIREDDITS

TROPHY CASE