Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Absolutely. Good documentation and responsive support would be important if I turn this into a real product.Make sure the apps perform well. If scrolling, navigation, or loading feels slow, users will immediately notice.
A demo could be useful. It would give people a chance to understand the experience before deciding whether it fits their product.I like the concept because it helps founders validate their mobile presence before investing in fully native applications.
I appreciate the detailed feedback. Reliability and simple maintenance will definitely be priorities if I move forward with it.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.
Yes, that’s important. I want the final apps to feel polished rather than simply looking like a website inside an app.The pricing seems fair. Spending a couple hundred dollars is much cheaper than hiring a mobile developer.
That’s an important question. I’m looking at ways to make updates as simple as possible so customers aren't maintaining separate versions manually.I'd want to know how updates work. If my website changes instantly reflect in the app, that's a huge benefit.
Exactly. Solo founders and small teams are probably the main audience I’m thinking about.I think your target customers are solo founders who want to launch quickly without maintaining multiple codebases.
Thanks. Since the idea came from a problem I experienced myself, I’m trying to keep the product practical rather than overcomplicate it.I like products that solve real problems you've faced yourself. That usually leads to a better user experience.
Biometric login is an interesting feature to consider. I’ll keep it on the list as I decide what should be included.One thing I'd like is support for biometric login like Face ID or fingerprint authentication.
Thanks for the detailed feedback. Saving development time while keeping the service reliable is really the main value I’m trying to create.Overall, I think this has real potential. You're helping founders save both time and development costs while making it easier to reach users on mobile. If the product is reliable, easy to use, and backed by good support, I believe many indie developers and small SaaS businesses would see it as a worthwhile investment.
Yes, that’s the audience I had in mind too. Solo founders and small SaaS teams are much more likely to benefit from a simpler approach like this.I think your target audience should be startups, indie hackers, and solo SaaS founders. Large companies usually have dedicated mobile teams, but smaller businesses often need a simpler solution like yours.
That’s a good point. Handling certificates, signing, and publishing could be a valuable premium service for customers who want everything taken care of.If your service also handles certificates, app signing, and publishing, I think many people would gladly pay extra. Those steps can be confusing, especially for developers with no mobile experience.
Very good to be do with you/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:
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.
- 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
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.
I'd really appreciate any thoughts or criticism. Thanks!
- 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?
That's a good point. App store approval and keeping everything compatible with future updates are definitely important. Clear support for these things would make the service more trustworthy for solo founders.I think this could be a useful option for solo founders who want a mobile app without maintaining separate codebases. The pricing sounds reasonable, but app store approval and long-term compatibility would be important factors for me.
I agree. Reliable updates and help with the app store submission process would add a lot of value. Most solo founders want a simple solution that saves time, not another thing to manage.This sounds like a practical solution for solo founders who want a mobile app without maintaining multiple codebases. The pricing seems reasonable, but reliable updates, push notifications, and app store approval support would make it even more appealing.
That's a fair concern. Showing examples of apps that have been approved on both stores would help build confidence. Even though approval can never be guaranteed, being transparent about the process would make the offer more convincing.One thing I'd want before buying is proof that apps built with your platform consistently get approved by both Apple and Google. That would remove one of the biggest concerns potential customers might have.
Not a bad idea at all!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:
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.
- 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
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.
I'd really appreciate any thoughts or criticism. Thanks!
- 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?