Would you buy it??

R

rmg97

Newbie
Joined
Dec 23, 2025
Messages
10
Reaction score
3
I’m a solo dev running a SaaS business. As many of you know, these days having only a website isn’t enough. You also need iOS and Android apps. Traffic is roughly split 50/50 between mobile and desktop, and maintaining multiple codebases is a big pain for small teams or solo developers.

Because of that, I built a webview setup for Google Play and iOS. It’s basically a native wrapper around my website, styled like an in-app experience, that can be submitted to both stores and gives users a more native feel. On top of that, I integrated Google and Apple payments directly into the webview and added push notifications.

I know this concept isn’t new, and I’m aware there are frameworks that try to solve the same problem. Still, I feel the webview approach doesn’t get enough respect for how practical it is.

I’m pretty proud of what I built, and I’m considering turning it into a product. The idea would be a one-time setup price around $200, plus an annual renewal fee (maybe ~$40) to cover messaging services like Google Pub/Sub and Apple’s yearly developer costs.

So I’m curious what you think:
Do you see value in this?
Should I build it out as a business?
Would you buy something like this?
Do you think those pricings are fair?

Thanks for reading.
 
Advertise on BHW
Honestly, I dont see value in that, im sorry. The pricing doesnt seem fair. Lots of people would react the same way
 
BreeLik said:
Honestly, I dont see value in that, im sorry. The pricing doesnt seem fair. Lots of people would react the same way
Click to expand...
That's ok, I'm looking for honest opinions! Thanks for replying!
 
It’s a practical solution for solo SaaS founders who don’t want to maintain multiple codebases. The key question is demand, though: are enough founders actively looking for this, or are they fine staying web-only? I’d validate that before building it out fully.
 
Webview apps get rejected a lot if they add no real native value. Many devs know this risk so 200 might feel high.

If you handle store approval and updates for them then maybe it sells.
 
There is definitely value in it. Many solo founders and small SaaS teams struggle with maintaining separate mobile apps, so a simple webview-to-app solution that handles payments and push notifications can save a lot of time. The key will be making the setup extremely easy and ensuring it passes the guidelines of the Apple App Store and Google Play. Your pricing also sounds reasonable for indie developers, $200 setup and a small yearly fee is much cheaper than building native apps. If you package it well and show real examples, there’s definitely a niche market for it.
 
Pricing seems a bit tough! Perhaps the setup fee may be reduced to then be marketable and more palatable.
 
Depends on the native value you’re adding. Webview wrappers get rejected if there’s no real native touch, so you’ll need to actually pass reviews and keep updates. If you can handle approvals, payments, and push reliably, the $200 setup + ~$40/yr could be a solid deal for solo devs. Validate demand first and show real examples; policy gates are the real bottleneck.
 
The product idea is ok, but I think the pitch shouldn’t be “webview app” because people instantly think rejection / cheap wrapper. Sell the outcome instead: “turn your SaaS into store-ready mobile apps with push + payments + approval support”.

If you can include some kind of review-safe template, screenshots, store wording, and maybe help fixing rejection reasons, then $200 is not crazy. Without that it feels like a codecanyon wrapper with extra steps, and people will compare it to cheaper stuff.

I’d prob test it manually first with 5-10 SaaS owners before building a full product around it. If they pay and you get them approved, you’ve got something.
 
I think the tech side is the easy part here, the real bottleneck is apple's guideline 4.2. they reject plain webviews all day long. @Campaigns By Mike is right about selling the outcome... nobody wants to buy a webview but they will pay to get their saas on the app store.

tbh if you can actually guarantee approval or help them get past the reviewers, then $200 is actually too cheap. maybe do a manual service first for a few clients, charge them like $300, and see what the rejection rate looks like. if you can get them approved consistently, you have a real business. otherwise it's just going to be a support nightmare with people demanding refunds when apple rejects them.
 
The tricky part is not building the wrapper, it’s filtering which SaaS apps are actually suitable for it. A dashboard/tool with logged-in users, notifications, account pages etc has a better chance than “website in an app” with 3 pages.

@rmg97 I’d probably not sell it as fixed $200 for everyone at first. Do it as a done-for-you service, review the site first, then quote. Some apps will need extra native bits, better onboarding, screenshots, wording, rejection handling... and that’s where the value is. $200 is cheap if approval/support is included, expensive if it’s just a packaged webview zip.
 
rmg97 said:
I’m a solo dev running a SaaS business. As many of you know, these days having only a website isn’t enough. You also need iOS and Android apps. Traffic is roughly split 50/50 between mobile and desktop, and maintaining multiple codebases is a big pain for small teams or solo developers.

Because of that, I built a webview setup for Google Play and iOS. It’s basically a native wrapper around my website, styled like an in-app experience, that can be submitted to both stores and gives users a more native feel. On top of that, I integrated Google and Apple payments directly into the webview and added push notifications.

I know this concept isn’t new, and I’m aware there are frameworks that try to solve the same problem. Still, I feel the webview approach doesn’t get enough respect for how practical it is.

I’m pretty proud of what I built, and I’m considering turning it into a product. The idea would be a one-time setup price around $200, plus an annual renewal fee (maybe ~$40) to cover messaging services like Google Pub/Sub and Apple’s yearly developer costs.

So I’m curious what you think:
Do you see value in this?
Should I build it out as a business?
Would you buy something like this?
Do you think those pricings are fair?

Thanks for reading.
Click to expand...
Webview is extraordinarily popular;

For instance, Canva's phone app, is basically a webview wrapper over their website.
 
the tech side of this is pretty commoditized tbh, you can find wrappers on codecanyon for twenty bucks. the real value is getting past the app store reviewers, especially apple. if you sell this as a flat self-serve product for $200, you are going to get killed with refund requests the second someone gets hit with a 4.2 rejection.

i would turn it into a done-for-you service instead. charge $500 and handle the actual approval process and back-and-forth with apple for them. if you can guarantee they get live, SaaS founders will gladly pay that and you avoid the support nightmare.
 
Advertise on BHW
You must log in or register to reply here.
Sign up now!

Main Menu

Home Main Forum List Black Hat SEO White Hat SEO BHW Newbie Guide Blogging Black Hat Tools Social Media Downloads

Marketplace

Account Selling Content / Copywriting EBooks / Methods Hosting Misc Proxies For Sale SEO - Link building SEO - Packages Social Media Social Media - Panels Web Design More

Making Money

Affiliate Programs Hire a Freelancer IM Journeys Making Money Pay Per Click Site Flipping Want to Buy

BlackHat World

Dispute Resolution Forum Suggestions & Feedback Introductions Lounge
Back
Top