[tle782]

The annual fee seems reasonable if it includes ongoing maintenance, notification services, and compatibility updates.

 

[Brittanyharris]

One feature I'd love is an easy dashboard where I can manage notifications without touching any code.

 

[RebeccaHarris74]

Don't market it as "just a webview." Focus on the business value—launching mobile apps quickly and reducing maintenance.

 

[cjohnson522]

If the onboarding process is simple, I think many non-technical founders would also be interested.

 

[DianaHorton]

I'd probably pay if the service handled certificates, app signing, and store submissions. Those are the parts many developers dislike.

 

[aallen]

Consider offering different plans. Some users may only need the app wrapper, while others would pay more for full publishing support.

 

[ShellyNorris]

THANK YOU LOTTS AND SO MUCH for each and everyone who have replied to my post.. It means a lott for my carrier and doubts..

 

[KevinHall5]

The product makes sense because maintaining separate iOS and Android apps can become expensive very quickly for small teams.

 

[JuliaThompson7]

I think documentation and good customer support will matter just as much as the technical features.

 

[Tracysantana]

Make sure the apps perform well. If scrolling, navigation, or loading feels slow, users will immediately notice.

 

[smccarthy2231]

A free demo or trial version would help potential customers see the value before committing to the setup fee.

 

[ehamilton478]

I like the concept because it helps founders validate their mobile presence before investing in fully native applications.

 

[JodiChang]

Overall, I think you're solving a real problem. If the apps are reliable, easy to maintain, and accepted by both app stores, I can definitely see solo founders and small SaaS businesses being interested at your proposed price point.

 

[StephanieSmith]

I actually think this fills a gap for a lot of indie founders. Not every SaaS needs a fully native app, especially in the early stages.

 

[Lindseyclarke]

I'd be interested if the app looked polished and users couldn't easily tell it was based on a webview.

 

[ChristineMccullough]

The pricing seems fair. Spending a couple hundred dollars is much cheaper than hiring a mobile developer.

 

[VictoriaMiller]

I'm a solo developer building and running my own SaaS, and I've run into the same problem I think a lot of small teams face.

These days, having a website alone doesn't really cut it. A huge chunk of users are on mobile, so people expect an iPhone app and an Android app too. For someone working alone, keeping a website plus two separate apps up to date is a lot of extra work.

To solve that for myself, I built a native webview app for both iOS and Android. It's essentially my website wrapped inside a properly designed mobile app, so it feels much more like a real native app than just opening a browser.

I also added a few things that made it much more useful:

• Google Pay and Apple Pay integration
• Push notifications
• Store-ready setup for both Google Play and the App Store
• A mobile experience that feels much cleaner than using the website directly

I know webviews aren't a new idea, and there are already tools that do something similar. But after using this myself, I honestly think they're underrated. For a lot of SaaS products, they're a practical way to get into the app stores without maintaining three different codebases.

Now I'm thinking about turning what I built into a product for other founders.

My initial idea is around $200 for the setup, then roughly $40 per year to cover things like messaging infrastructure and ongoing maintenance.

I'm interested in getting some honest feedback.

• Is this something you would find useful?
• Would you pay for it if you were running a SaaS?
• Does the pricing sound reasonable?
• Is there anything you'd want included before you'd consider buying it?

I'd really appreciate any thoughts or criticism. Thanks!

yes doing may

 

[Cynthia Lucas]

If you handle app store submissions, that alone would make the service much more valuable.

 

[Chloes Bush]

I'd want to know how updates work. If my website changes instantly reflect in the app, that's a huge benefit.

 

[hrichards759]

I'm a solo developer building and running my own SaaS, and I've run into the same problem I think a lot of small teams face.

These days, having a website alone doesn't really cut it. A huge chunk of users are on mobile, so people expect an iPhone app and an Android app too. For someone working alone, keeping a website plus two separate apps up to date is a lot of extra work.

To solve that for myself, I built a native webview app for both iOS and Android. It's essentially my website wrapped inside a properly designed mobile app, so it feels much more like a real native app than just opening a browser.

I also added a few things that made it much more useful:

• Google Pay and Apple Pay integration
• Push notifications
• Store-ready setup for both Google Play and the App Store
• A mobile experience that feels much cleaner than using the website directly

I know webviews aren't a new idea, and there are already tools that do something similar. But after using this myself, I honestly think they're underrated. For a lot of SaaS products, they're a practical way to get into the app stores without maintaining three different codebases.

Now I'm thinking about turning what I built into a product for other founders.

My initial idea is around $200 for the setup, then roughly $40 per year to cover things like messaging infrastructure and ongoing maintenance.

I'm interested in getting some honest feedback.

• Is this something you would find useful?
• Would you pay for it if you were running a SaaS?
• Does the pricing sound reasonable?
• Is there anything you'd want included before you'd consider buying it?

I'd really appreciate any thoughts or criticism. Thanks!

yes, as a solo developer..