Live data from Hacker News

Tiny PWAs and why I keep building them

justinribeiro.com

71–80 of 178 posts

Re: Tiny PWAs and why I keep building them

#71
Holy crap it's scary that he's building his own speedometer like that. GPS based speedos aren't all that accurate. Ballpark, sure, but not accurate. There are also many circumstances under which GPS won't work.

In many countries a car without a functional speedometer is not allowed on the road, for safety reasons.

Re: Tiny PWAs and why I keep building them

#72

There are only two real things limiting PWAs in my opinion: 1. Lack of support on iOS. I presume it’ll stay this way for a while (years!). Mobile Safari finally has service workers, but really, that’s about it. No support for “Add to Home Screen” (technically it’s there, but doesn’t work the way it does in other browsers), and a lot of other APIs. 2. The Web is missing some APIs that would really let it compete with…

> I presume it’ll stay this way for a while (years!).

It turns out iOS 12.2 will be "one heck of a release for Progressive Web Apps…"[1]

[1] https://medium.com/dev-channel/progressive-web-app-progress-...

Re: Tiny PWAs and why I keep building them

#75
post #39

I'm amazed there's a jurisdiction in a developed nation where driving a car with dead dashboard is legal.

That was my first reaction. If I was pulled over in Ireland with no dash the car would be impounded . And the speedometer is great but what about the other info? Fuel gauge? Mileage? Battery Charge? Engine faults?? Geolocation won't help with any of those. That said I do love the PWA approach to things and I think more people should embrace it. Just... not for this.

Really doubt you are legally allowed to use GPS based speedometer in place of actual one either.

Re: Tiny PWAs and why I keep building them

#76

Earlier quoted context omitted.

Can you share a link? People reading your comment have no way to know how to learn more about your project, or even whether it is relevant to the topic at hand. The most relevant result I could find for "linux on the web" was https://linuxontheweb.appspot.com/ which doesn't seem to be relevant at all.

I think that is the one actually because the looking at the post history [1] of the person you are responding to I find that the most recent post they made in the past was one titled “Linux on the Web” [2], which leads to that very URL that you found. He also posted a comment in the thread with some more details: > It makes heavy use of the HTML5 Filesytem for local storage, as well as Native Client for vim, python,…

[deleted]

Re: Tiny PWAs and why I keep building them

#77

If you want to see more PWAs, then go to the PWA Directory maintained by Google: https://github.com/GoogleChromeLabs/gulliver Interesting, there is one speedometer there, created 2-3 years ago. The source code is even available in GitHub. It seems that it isn't easy to find PWAs? https://pwa-directory.appspot.com/pwas/5079866537934848

The best thing that Google could do to support pwas would be to build a good search for them.

Re: Tiny PWAs and why I keep building them

#78

There are only two real things limiting PWAs in my opinion: 1. Lack of support on iOS. I presume it’ll stay this way for a while (years!). Mobile Safari finally has service workers, but really, that’s about it. No support for “Add to Home Screen” (technically it’s there, but doesn’t work the way it does in other browsers), and a lot of other APIs. 2. The Web is missing some APIs that would really let it compete with…

Regarding 2, one point of distributing PAWs via the respective stores is that when their origin is validated, they are also native apps and have full access to all device APIs.

See PWAs on Windows 10, or the recent TWA support on Android.

Re: Tiny PWAs and why I keep building them

#79
post #32

> “surely there is a app for that!” A quick look leads to speedometer apps with ads and 30MB download weight, and simple screen light that also have ads that weight in at 5MB. I’m finally groking what rms has been banging on about for so long. It is completely unacceptable that we are running software that does this to the user. Users need to be empowered and able to run code that they can control.

Exactly. If more people's reaction, instead of searching an app store for a privacy respecting screen light, was to sit down and write: let on true; and were able to easily upload it somewhere on a phone and run it locally from a shortcut on the screen. We'd have hacker culture encouraged right there.

Upload? Come on, just load it as dataURI, bookmark it and you have offline "application" at your disposal. And as a bonus, here, have this "distributed app store" you can even print on paper [1].

[1] http://zxing.org/w/chart?cht=qr&chs=350x350&chld=L&choe=UTF-...

i.e. QR-coded dataURI document

    data:text/html;charset=utf-8,Screen light

Re: Tiny PWAs and why I keep building them

#80

> A quick look leads to speedometer apps with ads and 30MB download weight, and simple screen light that also have ads that weight in at 5MB. I don’t see why this means PWAs are better than apps. There’s nothing stopping you from writing an app instead of a PWA in this case.

Pls. God no.. Why this obsession with apps when a simple PWA does almost all you need. Apps are akin to what the windows app were a one and half decade back. Like web apps blew 99% of thick client app to oblivion the same is going to happen soon to the mobile apps. It isn't without reason, why Apple isn't too keen with this development (they were one of the last to implement web workers and PWA in their browsers). I…

It was Microsoft's embrace of PWAs that finally made me change how I see them.

Apparently it is still unknown to most HNers that PWAs can also use native APIs, depending on how they are distributed.

Post reply on HN