[DawnCrawford]

I appreciate that you're focusing on practicality instead of chasing the latest technology. Sometimes the simplest solution is exactly what customers are looking for.

 

[TimothyGonzalez]

The annual fee seems perfectly reasonable if it includes updates and maintenance. I'd actually be more worried if there wasn't any ongoing support available.

 

[JenniferLam]

I think there's room for this product because many existing solutions still require developers to configure everything themselves. A managed service has its own appeal.

 

[AmandaHall]

The fact that you've already built and tested it for your own SaaS gives me more confidence than if it were just an idea. You've already solved many of the problems future customers will face.

 

[DianaHorton]

One suggestion would be to include analytics integration by default. Most SaaS founders want to track installs, retention, and user behavior inside the app.

 

[BrittanyRogers]

I'd probably buy something like this if it reduced the entire mobile app process to just a few simple steps. Convenience is worth paying for.

 

[BrittanyPatterson]

Your pricing feels fair, but I think you could even offer different plans depending on the level of customization and support clients need.

 

[ChristinaRogers]

Push notifications and native billing are the features that really stand out to me. Those are usually the biggest reasons people build mobile apps in the first place.

 

[jriley312]

I think many founders overestimate the importance of fully native apps. If users can accomplish everything they need inside a fast webview, that's often good enough.

 

[aallen]

I'd be curious to know how updates work after the app has been published. If website changes automatically appear in the app, that's a huge advantage.

 

[Cassandra Scott]

It might also be worth offering migration support for people who already have outdated mobile apps they'd like to replace with your solution.

 

[Ruthrivera]

I can definitely see this fitting well within the indie hacker community. Most people there are trying to maximize results while keeping development costs under control.

 

[LoriMoore]

One thing I'd suggest is creating a sample app that potential customers can download. Experiencing the product firsthand is much more convincing than reading about it.

 

[abaker649]

I think the biggest selling point isn't the technology itself—it's the time you're saving founders. That's the message I'd focus on when marketing the product.

 

[tle782]

Look at the monthly expenses as well, not just the income.

 

[Jessecline]

If your onboarding process is smooth and you handle the technical setup, I think many non-mobile developers would happily pay for the convenience.

 

[vsherman295]

One feature I'd want is the ability to update the app without constantly submitting new versions to the app stores.

yes you are right

I think your biggest challenge will be marketing rather than building the product. There are plenty of founders who need this—they just have to discover it.

means gud thought

Have you tested the app's performance on older Android devices? That could be important for some customers.

yes

I'd love to see a live example in both app stores before making a purchasing decision.

yes

 

[vsherman295]

Have you measured the performance compared to a traditional native app? If scrolling and navigation feel smooth, I doubt most users would even notice it's webview-based.

yes

 

[vsherman295]

I appreciate that you're focusing on practicality instead of chasing the latest technology. Sometimes the simplest solution is exactly what customers are looking for.

tq so much

One suggestion would be to include analytics integration by default. Most SaaS founders want to track installs, retention, and user behavior inside the app.

very wll

 

[vsherman295]

all you thoughts are goo and many more helpful for my works