Live data from Hacker News

The web apps that will eat mobile

kruschecompany.com

41–50 of 105 posts

Re: The web apps that will eat mobile

#41
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…

I wrote a PWA and got it published in 3 app stores[0]. I found this to be a pretty good mix: I can access native mobile features while using modern web features and rolling out instant updates without app store approval.

[0]: http://debuggerdotbreak.judahgabriel.com/2018/04/13/i-built-...

Re: The web apps that will eat mobile

#42

These apps seem to solve a developers’ problem, not a users’ problem.

As long as people wants new apps quickly (now) and cheaply (free) the developers problems are _very_ important. Making those problems smaller or disappear makes it quicker and/or cheaper to develop apps and the companies paying for the apps will like that.

Re: The web apps that will eat mobile

#43
post #32
post #18

Earlier quoted context omitted.

> realize how sub par the [mobile web app] experience is why is this a given?

A proven experience since Symbian introduced the Web Runtime in 2011, with a few dead OSes pushing for a Web only experience?

There is such a thing as "good enough". The cheap plastic solution tends to win when that happens. We weren't there in 2011, maybe we're not there in 2018, but the writing's on the wall.

Re: The web apps that will eat mobile

#44

These apps seem to solve a developers’ problem, not a users’ problem.

It's also false gold for the developer, it seems like less work but PWA's (in my experience) are almost always a worse experience for the User and require far more work to get them up really usable, if it's possible at all. Lot's developers are trying to sell this technique because they can't be bothered to learn something new. The reality is that it's a worse experience at the end of it for both the developer and the user.

Re: The web apps that will eat mobile

#45
post #15

No mention of writing apps in React Native?

it's out of fashion already :-p

According to this article, yes, it is. On the other hand it is a really, really easy to convert a react native app to a web app with react so it might have been a very good choice of technology anyway.

Re: The web apps that will eat mobile

#46
Web apps have a bright future, with only Safari lagging behind. (Did you know Steve Jobs originally envisioned AL mobile apps to be web based?)

I have emailed Jonathan Davis (web-evangelist@appl..) from Safari several times over the last few years asking when Push Notifications will finally be supported. Without this, websites need to rely on email as a retention mechanism.

But here’s the thing with all this. It’s a lot to build and support all these operating systems, where things constantly change. Even more to have an integrated unified solution.

Take for instance onboarding. New people click an invite link and go to your site. First you want an instant social experience. That’s easy enough: just have each invite have a unique link confirming that phone number or email, and when they arrive show them all the friends who uploaded hashes from their Contact list where they are found. And show all the content they have already engaged with. But wait, phone numbers only have 10^7 possibilities roughly, so that’s a trivially reversible space. SO now go read about the state of the art from Signal and others and figure out your own more secure solution.

And after this you want the user to download the native app so you can send notifications to them, they can upload their Contact list and find their friends, invite people easily etc. Seems easy: just redirect them to the store.

But wait. You want attribution for campaigns, and you want to resume sessions. How to do it? Well you could use SFSafariViewController to get the web cookies but that’s been deprecated in iOS so now you need to to use SFAuthenticationSession.

Wouldn’t it be nice if there was a project that would take care of all this shifting stuff for you so you can focus on building the core of your app?

Well that’s why I started Qbix initially. We keep adding free open source plugins to solve these individual problems:

https://github.com/Qbix?tab=repositories

Go ahead and grab them, we plan to maintain them as the OSes change since we use them in our ow apps.

But this is literally the tip of the iceberg. Most of the questions have to do with social and communty features like roles, permissions, realtime sync, offline notifications, user authentication across apps, payments, and so on.

If you want something that will let you develop new web based apps at record speed or support turning existing websites/apps into social apps with accounts (think turning git into github) without reinventing the wheel you are welcome to the code

https://github.com/Qbix/Platform

It is licensed under AGPL so if you want to keep your code private and not open source it to your website visitors then you’d have to contact us for a license, which at this point is probably like $100 a year regardless of users. But for FOSS projects and weekend stuff it’s totally free, to promote the improvements of the ecosystem.

Here is the vision long term: https://www.youtube.com/watch?v=pZ1O_gmPneI

Oh also we aren’t happy with the state of mobile browsers when it comes to supporting content addressable routing, verification of resources, encrypted web push notifications secure access to contacts by websites, and so on. So we are building the Qbix Social Browser:

https://projects.invisionapp.com/m/share/TKHYMVSJNW2

Re: The web apps that will eat mobile

#47
post #35

Earlier quoted context omitted.

I very much agree, we evaluated PWA vs native recently and found PWA(on iOS) to be a really poor decisions. We likely build one for Android as the experience is better there but it's very poor on iOS and unlikely to get better anytime soon(next 1-2 years).

At this point, isn't Apple actively delaying PWAs? It seems like it, based on their recent sluggishness in adopting web standards in Safari.

Web "standards" for PWA's are pushed out willy-nilly by Google. Just because it is preferable for Google to push towards everything on the web, it does not mean that all browser vendors should create new APIs that were declared "as standard" in their draft version and pushed out into Chrome.

Service Workers, for example, are just a working draft and somehow not having the spec implemented is considered as lagging.

PWAs are fine for some uses. However I think it would be better for everybody if the vendors were extra cautions when creating and approving these standards as these APIs tend to crystallise and browsers end up supporting a lot of deprecated cruft. I was young when MS was doing the same thing with IE6 but I still remember the pain in the ass making anything remotely compatible was. And back then we were not talking about access to stuff like microphone or background activity.

Re: The web apps that will eat mobile

#48

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

Depends on the user, I might be an outlier but my "ingrained behavior" is to not download an app unless I absolutely have to.

Same. We are not normal users. For a native app and PWA for childcare centre management I worked on: the PWA flow just confused parents. I’m really hoping that’ll change in the future

Re: The web apps that will eat mobile

#49
post #38
post #29

Earlier quoted context omitted.

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.

Come on, so even his mistakes were not mistakes?

Basically yes. This is his famous "reality distortion field."

Re: The web apps that will eat mobile

#50
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…

After writing enough front end work, I'm not exactly afraid of writing native apps for multiple platforms.

I dont want to, which is why I chose react native JS for this round of development. But the big deal IMO is getting the back end of the app developed and working.

Beautifying is annoying and time consuming, but I dont need to learn anything new.

Implementing a backend that is secure required learning a framework and massive testing.

IMO pretty is easy, but I havent made anything for IOS, so who knows.

Post reply on HN