5 ms·
I'm more interested in the future of "you probably don't need a native app". It feels like browsers are closing the gap pretty well with things like IndexedDB,
by tyingq 8y ago
I'm more interested in the future of "you probably don't need a native app".
It feels like browsers are closing the gap pretty well with things like IndexedDB, offline features, WASM, etc. Still a ways off, but seems like it's getting there.
I do worry, though, that it's not really in Apple's or Google's best interest to move that along.
- IloveHN84 8y agoNative will always be the best solution... Because it's native.
- tyingq 8y agoTechnically best doesn't always win the market. I'd love not writing 3 versions of every piece of functionality.
- AnIdiotOnTheNet 8y agoHow's that working out when there's more than one browser you have to account for? What's the difference between polyfill or some framework, and something like Qt or SDL? Or I suppose we could just all use chromium, but we could also just all use Windows.
- tyingq 8y agoI have to write it for the web already. Writing a native Android and a native iOS app is additive if the web version is "good enough". There's no scenario where I only have to write two native apps. Perhaps there is for other people.
- AnIdiotOnTheNet 8y agoConsider that maybe there are uses for software where the web isn't necessary and isn't even the first choice. You're a hammer, so everything is a nail. The reality is that the web is a horrible choice for a whole lot of things. It's a document platform with parts of an application platform shoe-horned in and bolted on, and the result looks like a garbage fire to people who come from the land of native software.
- tyingq 8y agoI'm not sure I understand why browsers getting closer to native apps ruins anything for anyone else. You're still able to hammer your nails however you want.
- ken 8y ago> What's the difference between polyfill or some framework, and something like Qt or SDL? As a user, I usually can't even tell when they're using a polyfill on the web (except when they stop, like GitHub did with type=date). (As a developer, I often can't tell the difference, either. Some of them are that good!) So long as you generate HTML/CSS/JS, it doesn't matter to me how you do it. That's as 'native' to the web as you can get. I can spot Qt a mile away. A lot of the visuals look wrong and a lot of the controls don't behave right. It's frustrating to use, and I always slow way down and double-check my work because, e.g., popup menus show the 'accept' animation even when you cancel them.
- AnIdiotOnTheNet 8y ago> I can spot Qt a mile away. A lot of the visuals look wrong and a lot of the controls don't behave right. You mean it has no respect for your native toolkit... just like the web?
- deleted 8y ago[deleted]
- tyingq 8y ago"just like the web" How true is that? I was under the impression that for Android and iOS, Chrome used the native widgets for most things.
- tedunangst 8y agoHow many SPAs use native controls with minimal styling?
- leadingthenet 8y agoYou're just externalising the time you save as a cost to your users.
- deleted 8y ago[deleted]
- tyingq 8y agoIt's equally possible you're doing the same thing by forcing users to download a native app. It's kind of hard to talk about in the abstract. Some things work better in an app, for other things it adds nothing notable.
- mycall 8y agoHave you tried Angular+NativeScript? one piece for all (minus UWP).
- WrtCdEvrydy 8y ago> not writing 3 versions of every piece of functionality. React Native and ReactJS are a move in the right direction. I wonder if we'll get React NativeJS
- tomduncalf 8y agoNot sure exactly what you mean by React NativeJS but perhaps React Native for Web (https://github.com/necolas/react-native-web https://github.com/necolas/react-native-web) is along the lines of what you are thinking? Works remarkably well. It’s already used for Twitter’s mobile site
- Midnightas 8y agowxWidgets would help with that.
- criddell 8y agoI'm sure it's nice for you, but users like me aren't happy that every mouse move and page load is cataloged and studied and shared with partners. At least with a native app I can add a firewall rule to restrict it's ability to use the internet.
- jhall1468 8y agoUsers like you represent a tiny, tiny minority. The majority of people couldn't care less about google tracking their mouse movements.
- criddell 8y agoI'm guessing you don't live in the EU.
- noisem4ker 8y agoThe majority of people are not aware that someone is tracking their mouse movements.
- deleted 8y ago[deleted]
- pmlnr 8y agoExcept when all your content comes through the pipe, in which case native is just a glorified iframe.
- hombre_fatal 8y agoNative has downsides too, like having almost zero control over the client and being unable to link other people like you can on the web. Just a bunch of silos by design. Native is only a trade-off that has great performance at other expenses.
- saagarjha 8y agoNot always. There are times when you don’t want to download an app for every little thing, though the opportunity to be able to do so is nice. There’s a reason we have browsers and not just everything coming through in its own individual app.
- collyw 8y agoWeb is best because it is platform independent.
- the8472 8y agoResource consumption will be worse, doubly so when they make an app out of the SPA via electron&co.
- tonyedgecombe 8y agoIt's in Googles interest as everything they deliver is through the browser. Not so much for Apple or Microsoft though. Personally I will be quite sad if I end up loosing so much control over my computing environment.
- tyingq 8y agoWell it would cut into revenue from the PlayStore. I suppose it's plausible that keeping people in the browser is a good enough trade-off for Google.
- jtdev 8y agoI can’t imagine that the Google Play Store is a huge revenue generator, relatively speaking of course.
- tyingq 8y ago$24.8 billion in 2018[1]. [1]https://www.statista.com/statistics/444476/google-play-annual-revenue/ https://www.statista.com/statistics/444476/google-play-annua...
- deleted 8y ago[deleted]
- jon-wood 8y agoThat’s much higher than I’d have expected. I wonder how much of it comes from games and their in app purchases, a segment that is unlikely to take much of a hit from moving other apps to the web.
- simple_phrases 8y agoNative apps allow Google to collect much more information than they can via the browser. They also allow for a wider range of advertising opportunities.
- syntheticcdo 8y agoThis is the only reason we have an SPA to begin with-- small team writes a single frontend and deploy to web, iOS and Android via Cordova, Windows via Electron, and (previous) Chrome OS via the now deprecated Chrome App APIs. If we didn't need to support the full experience on all these devices, SPA would be way overkill.
- elizabeth_olu 8y agohttps://www.elizabethblog.com.ng/2019/02/two-people-were-killed-while-13.html https://www.elizabethblog.com.ng/2019/02/two-people-were-kil...
- skybrian 8y agoI look forward to a similar article saying "You probably don't need WebAssembly." I mean, it's neat and all, but most websites aren't CPU-bound.
- tyingq 8y agoI didn't view WASM on its own as the big differentiator. But, it is one of many things that's closing the gap between native apps and web apps. As you mention, it's useful in some situations.
- superkuh 8y agoAs browsers close the gap they simply become the OS but slower, more abstracted, and with less security. And they stop being good browsers. It's the old emacs situation come round again. The only positives are to corporations and institutions with profit motives to decrease dev time and increase ability to spy on users and extract rent from them.
- expertentipp 8y ago> As browsers close the gap they simply become the OS but slower, more abstracted, and with less security Browsers are forced to implement standards like CORS, single-origin policy, and multiple levels of SSL certificate validation and thus are more secure than most of native apps. How do you know whether that mobile app is not signing in over HTTP? In a web browser it's obvious instantly. > motives to decrease dev time and increase ability to spy on users and extract rent from them. Literally the worse what can happen over web browser is tracking based on various forms of fingerprinting. Native apps? MAC addresses, SSIDs, serial numbers - EVERYTHING is available for the native app to send ANYWEHERE, even over HTTP.
- jomohke 8y ago> they simply become the OS but slower, more abstracted, and with less security. I agree with slower, at least for computational tasks, but not security. Do you feel safer installing an organisation's native app than using their web app? > The only positives are to corporations and institutions with profit motives... What advantage does the web give to corporations that native apps don't? You mention spying, but the native mobile app ecosystem is filled with tracking and analytics code (and it's easier to hide it). The only corporation-level difference I can see is that native apps are heavily tied to a specific company's platform, while web apps aren't. This is a huge positive to the web - I've felt free to change platforms many times. A second huge and underestimated positive of the web is backwards compatibility (ie. lower maintenance headaches). A complicated internal web app I wrote eight years ago is still running despite not being modified. The websites and lousy javascript I wrote as a kid in 1999 still run exactly the same as in 1999. Spacejam.com is unmodified from 1996. Yet I have many native apps from two years ago that no longer run correctly due to OS updates (especially on mobile).