The web apps that will eat mobile • Hacker News Board

Re: The web apps that will eat mobile

#11

Post by xamarinthrw » Tue, Jun 05, 2018, 2:14 PM UTC

mikece wrote: post #2

Progressive 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,…

Can you tell us a bit about your Xamarin experience?

I want to create an app where the users would be regular mom and pop- my primary users would be windows and Android and a few iOS (iphone).

Would you recommend I go the Xamarin way?

Who is xamarin good for and who not?

Re: The web apps that will eat mobile

#12

Post by djanogo » Tue, Jun 05, 2018, 2:15 PM UTC

There 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 depends on selling this solution or the person is huge web guy and never really worked on complex native apps.

Re: The web apps that will eat mobile

#13

Post by tvorog » Tue, Jun 05, 2018, 2:16 PM UTC

Web app can be easily blocked by government. Look at telegram in Russia. Native app still useful without vpn.

Re: The web apps that will eat mobile

#14

Post by xamarinthrw » Tue, Jun 05, 2018, 2:17 PM UTC

djanogo wrote: post #12

There 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…

> turd

> conflict of interest

> ~simpleton

Says the guy that deliberately says: "both the platforms". Talk about ingrained propaganda

Re: The web apps that will eat mobile

#15

Post by bigato » Tue, Jun 05, 2018, 2:19 PM UTC

mkirklions wrote: post #8

No mention of writing apps in React Native?

it's out of fashion already :-p

Re: The web apps that will eat mobile

#16

Post by shapiro92 » Tue, Jun 05, 2018, 2:19 PM UTC

the 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.

Re: The web apps that will eat mobile

#17

Post by xamarinthrw » Tue, Jun 05, 2018, 2:19 PM UTC

tvorog wrote: post #13

Web 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

Re: The web apps that will eat mobile

#18

Post by chii » Tue, Jun 05, 2018, 2:21 PM UTC

djanogo wrote: post #12

There 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…

> realize how sub par the [mobile web app] experience is

why is this a given?

Re: The web apps that will eat mobile

#19

Post by berns » Tue, Jun 05, 2018, 2:23 PM UTC

> Dramatically, a huge change has happened again thanks to a move from Apple. This time with Safari.

A few paragraphs later:

> -There’s still no Web Push or Background Sync on iOS (and it will take time).

And here is a response from Apple[0]:

> As we indicated we were doing last year, we’ve implemented the core ServiceWorker spec - https://w3c.github.io/ServiceWorker/ - in trunk WebKit. Web Push is a different spec that we’ve made no comment on one way or another.

[0]: https://bugs.webkit.org/show_bug.cgi?id=182566

Re: The web apps that will eat mobile

#20

Post by Cthulhu_ » Tue, Jun 05, 2018, 2:24 PM UTC

shapiro92 wrote: post #16

the 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.

With a popup asking to be added to the home screen. A lot of mobile websites I visit (usually if my HN reader app can't parse the content) either have one of those, or have it hidden somewhere in the other popups - sign up for our newsletter, agree to our cookies, fixed headers, etc.