Subscribe
Sign in
Nativizer — Convert any web application into native iOS & Android apps
Nativizer is a tool that converts your existing web applications into native iOS & Android apps, automagically. It works with any responsive web-sites, regardless of the platform they have been built on. Simply fill out the form and we'll get it ready in 24
39
Replies
Best
@mickc79 Hi Mick, thanks for the supportive comment, our offering is aimed at users like you! :) Yes, sure please reach out to native@zeroqode.com and we'll be happy to help. Another helpful way to discuss this is our forum https://forum.zeroqode.com where we are very responsive. Thanks!
Is this scalable? It kind of seems like it's a product offering from a studio or agency, rather than an automated tool in itself, given that a number of 'plug-n-play' 'add-ons' say "Custom development will begin immediately, and is expected to complete with [sic] 2-3 weeks".
In-app purchases seem to be only listed for iOS – is support coming for Android?
Would be interesting to see actual API documentation beyond the brief descriptions offered, to see what the JavaScript APIs are like.
Edit:
I'm guessing it's also not possible to easily support things like iOS Haptic Touch context menus, dynamic type font sizing for accessibility, Siri shortcuts/Google Assistant actions, home-screen quick actions or widgets either, as this is just to quickly turn a web app into an app that can be distributed through native platform stores (I hesitate to say 'native'). Seems like larger businesses using this would eventually graduate on to React Native/Flutter/or true native apps, but perhaps that isn't a problem as long as they've paid for a Nativizer app in the first place.
@iamsebj thanks, it's not totally automated but requires minimum involvement from us if it's just a simple wrapping or one of the basic add-ons. The in-app purchases or some others are more complex and yes, those are more like an agency work. At the moment in-apps are only for iOS, perhaps we'll be able to add Android later on.
Is Apple gonna accept these apps? My understanding is they started rejecting non native apps that just opened a web view.
Has the policy changed?
@massimocw hey Massimo! Yes, Apple is accepting these apps.
Apple does not like apps that are simply a natively packaged version with no added native functions, that is available via the browser on your smartphone.
If there is added value (like push notifications, or any other native feature that would otherwise be not available via browser) in packaging your web app to native app - Apple does accept the wrapped applications.
Hey, Product Hunters! 👋
Today we present Nativizer - a tool designed to convert any responsive website into a native iOS and Android app. 📲
You don't need to be a coder to use solution to wrap your website into a professional native app! 🎁
Moreover, it comes with a ton of additional add-ons that you can plug-n-play to your app.
📪 Native push notifications
💰 In-app purchases
🖥 AdMob
👩❤️💋👨 Social logins,
🗺 Geolocations
to name a few, can be easily integrated.
The benefit of using a native wrapper solution over building native apps from code?
♻️ Updates on your website immediately appear in your app
👨🏽💻 You won't need to code 2 new apps completely from scratch
🚀 Fast time to market - get your app wrapped in 24 hours and submit it to the stores!
No coding. No trouble. It just works!
If you have any question, feel free to ask - we'll be around all day!
Thanks a lot for all the support
and much ❤️
Levon
Founder @ Zeroqode
@coconidodev it's a little more intricate than that. Unlike many other webview solutions, we guarantee ours (including all the components that we advertise) to work as it should. And when compared to the costs of building native apps from scratch, $790 for 2 apps is not really much. One doesn't have to pay us $650 if they want to go through the publishing with the stores themselves, it's only if the user absolutely doesn't want to get involved, then we would help.
@coconidodev are you a developer? Do you build native apps? if so, which stack are you normally using?
The pricing seems way to expensive. 800$ for a webview.. I still have to build the PWA/web page and everyone can make a web view wrapper as it basically requires 10 lines of code (at least for Android). Also the addons don't seem to be worth the money
@simolation Hi Simon, thanks for your comment. Did you actually try to build a webview app? Did you try integrating push notifications, or QR scanner or in-app purchases? Once you try you'll realise that it's much more than just 10 lines of code. Yes, there are webview wrappers that you can buy for $25 or even get for free, but don't tell me I didn't warn you :)
@levon377 I am a mobile & web developer so I have indeed build more than webview apps. The webview is even less than 10 lines though. Adding fcm is not difficult as well as you only have to register it within the app and get the device key. For sending messages you still have to do it on the backends/web-apps side. Adding a QR-Code scanner is also not that difficult when using a library like zxing for what you are charging 3500$.
I mean the idea is great but the pricing is way to high (as you still have to develop your web-app by yourself that does all the real difficult stuff).
I also think it is expensive but the technology would be very useful and interesting if it was able to "convert" HTML tags into native implementation of elements. My question is if this could potentially transform web apps into native apps besides just landing pages.
@felipe_otalora hey Felipe! Thanks, that's exactly what this thing does actually :)
Not necessarily translating HTML tags to native elements, but this is far beyond making a "native landing page" :) why would anyone even need a landing page natively? :)
Typical use case is that if you have a web app that is already functional and responsively running on multiple devices (in device's browsers), and you want to add a native app (say, you need push notifications), but you don't necessarily want to invest into a whole new codebase (2 potentially, for iOS and Android), then that's the solution.
You convert your whole responsive web app (not only a landing page) to a native app, and whenever you need to do a change\fix a bug, you do it once for 3 different user types - web, iOS & Android.
Makes sense? :)
@matelikeskarate yes, exactly, but it's not that easy from a technology point of view as it may seem. There are tons of intricacies that are required for the app to look and function just as a native app. Plus the native add-ons that seamlessly integrate into the web app to make it feel native. And by the way lots of apps in your phone are built like that. Most of the banking apps (like Sillicon Valley Bank), Stripe etc use the webview technology for building their native apps. Progressive Web Apps is another evolution step for native app development.
@matelikeskarate @levon377 I agree with Poplop. These are not native apps. A native app has a native UI set and a completely different level of performance. These are progressive web apps.
@matelikeskarate @dossey_richards progressive web apps are not published on appstore and google play. Apps built with our solution are. And the UI can be made look like native. Check Stripe's apps for example or many banking apps - they are actually webview apps not built from ground up with native languages
@matelikeskarate @levon377 Your solution takes a web app and then displays it an in-app browser. That is not native. And it won't allow for anywhere near native performance. Also, there are many progressive web apps that are in the app store. Cordova turns them into the files necessary. (The Ionic Framework, MeteorJs and etc are all also great frameworks to do so). I have nothing against PWA's. But they are not the same as native apps.
@matelikeskarate @dossey_richards I think we should define native app first. Here is what I see by googling it: "A native application is a software program that is developed for use on a particular platform or device." So if our solution allows using the website on a particular platform or device (in our case it's iOS and Google play) - then we can call it native.
As a developer it is perhaps a solution for a person out of knowledge, but $4500 to implement a faceid or touch id sdk, is almost the price of an app developed from 0, and more I must have my website.
That is to say a Webview with super powers for 31000 Dollars I consider maybe this out of the market reach.
Perhaps it is useful but its values I consider beyond the scope of the current market.
With frameworks like Flutter that are native and have a high range exponential growth, achieving iOS and Android apps
@david_villegas we experimented with flutter and other framework, they are good when you want to build something simple, but for more complex apps we always faced some issues that were super complicated to work around. Usually noone needs all the superpowers for $31000. And the base app (For android+ios) costs just $790 which is well within the market reach IMHO. As well as the most demanded push notifications feature and some others which are also affordable.
@david_villegas and if you think about it faceid or touch id is really very very specific use case.
@chrisfr Thanks for the words of support, Chris, appreciate it! Yes, our offering is not cheap because we provide a product that no other webview package can match in terms of add-ons and native like features. Those who understand the difference know that the price we charge well worth it.
Here's what an app with all options costs:
Total Price: $31,890
( 11 add-on's included )
@itsbrex that's correct, but you don't need all the options, right? :) Most of the time users need just the basic wrapping with push notifications. The more specific a use case is the more add-ons might be required (or just different ones).
Very deceptive saying that this product converts your website into native code. The product seems to be implying that your website will be converted to iOS (Swift) and Android (Java/Kotlin) components. This is not the case. It is just a service that wraps your website into a webview and includes a couple of additionally libraries for notifications etc.
@beefjerkydev Hey Will!
Thank you for your feedback :)
But I don't think we said "converts website to native code" - we said "converts your website to native apps", which is exactly what is does.
Yes, you understand the point of it correctly - the essence of the service is to extend the use of your existing web application to Apple and Google stores, plus add some purely native functionality to it - such as Push Notifications and\or other Native-Component interaction\synch libraries, and voila :) you have (up to) 3 applications in 3 major distribution channels.
The alternative to that is design, testing and launch of 3 different code-bases, and I'm not even talking about maintenance :)
Songbox