No mention of writing apps in React Native?
They didnt mention any frameworks actually. Normally I expect company web blogs to include some introspection into tools evaluated or used by them, but I guess this is more of a fluffy piece.
The web apps that will eat mobile
21–30 of 105 posts
Re: The web apps that will eat mobile
#22There are two ways to write mobile app... 1. Write native app's for both the platforms, pay once and cry once. 2. Write web mobile apps, realize how sub par the experience is, rewrite in native. Pay twice, loose competitive advantage, and cry twice. This is what, 3rd or 4th iteration of web app's are going to take over mobile cycle?. My first instinct about any blog that promotes this turd is, either their business d…
As with web apps and applications in general there's a wide gamut of different app categories. There's also frameworks such as Ionic that provide native or near-native capabilities and experience through native bindings.
Re: The web apps that will eat mobile
#23Re: The web apps that will eat mobile
#24Web app can be easily blocked by government. Look at telegram in Russia. Native app still useful without vpn.
This doesn't even make sense. Blocking is blocking of network connection. Native apps still need that to talk back home
Telegram uses push notifications to update its server ips.
Re: The web apps that will eat mobile
#25These apps seem to solve a developers’ problem, not a users’ problem.
Re: The web apps that will eat mobile
#26the problem noone mentions with PWAs is that simple users do not know what A2HS means. They dont know what a PWA is so in the end we are talking about a web page that is mobile friendly.
As soon as we can "install" PWAs natively and launch them like an app from our phones they will go unused.
The way the browser is currently being used to serve PWAs on mobile doesn't make any sense. No one wants to bookmark a website onto their phone and then have it load up inside a browser. It's clunky and dumb.
Not sure why this is taking so long but it is holding back the wide spread use of PWAs.
Re: The web apps that will eat mobile
#27Progressive Web Apps have the potential to be massively disruptive to apps as we know them now... and that's before the near-native speeds that WASM will bring are factored into the equation. After making the mistake of going all-in on Xamarin in 2014 I realized, much to my chagrin, that the future of mobile is HTML, CSS, and JavaScript. Sure, there are cases where certain features require vendor-native apps for now,…
> A completely different question is whether vendors like Apple will refuse to support something like this because it circumvents the need to deliver via the app store (and the $$$ they collect through the Apple Developer Program) but there's no reason background services and processes can't be implemented in JavaScript. I could see Apple et al resisting, but wouldn't a store still be useful for discoverability and g…
I would take an app search engine -- or several of them -- or a curated lists of "new and interesting PWAs" that anyone can create and maintain versus a gatekeeper (or a collection of gatekeepers with differing standards) who demands to be paid before you can appear as an eligible entity for the platform.
Re: The web apps that will eat mobile
#28Web app can be easily blocked by government. Look at telegram in Russia. Native app still useful without vpn.
This doesn't even make sense. Blocking is blocking of network connection. Native apps still need that to talk back home
Native apps can be a bootstrap shim for a more distributed back-end. PWAs are not going to be loading off onion nodes or ephemeral distributed networks any time soon. Native apps, especially those that can side-load or update without the app stores, will always be more resistant to these sorts of attacks.
Re: The web apps that will eat mobile
#29Earlier quoted context omitted.
People openly booed Steve Jobs in 2007 when he announced that the iphone would only support webapps. Obviously Apple changed their tune, but it would be funny if they started dragging their heels in the other direction.
Apple didn't have the app store and it's 30% rake of all transactional revenue at the time. Jobs was somewhat notorious about being adamantly opposed to something one day and then announcing to the world that Apple had created a best-in-class product that he previously said they would never make. I seem to recall him saying they would never make a tablet device -- that it wasn't so critical to surf the web on the toi…
Also don't forget his famous comments on no one will watch video on small screens and no need for big phones. I don't think any of his comments were lack of insight, rather it was him playing the market until he was ready.
Re: The web apps that will eat mobile
#30Unpopular opinion here, but I just don't see PWAs living up to the hype. Yes, there are lots of technical advantages, they're catching up to native apps in capabilities, and there is reduced friction by bypassing app stores. However, the ingrained user behavior of downloading apps from the app store, trust of knowing what you're downloading by doing so (yes, even on Android), and browsability on mobile falling behind searching the app store from a ux standpoint make me think there are still some big barriers to PWAs taking the mobile world by storm. Yes, they'll have their place, but I don't see them living up to the hype often promised by their evangelists.