Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Tiny PWAs and why I keep building them

justinribeiro.com

Post reply on HN
Print view View original

131–140 of 178 posts

Re: Tiny PWAs and why I keep building them

#131

Post by oneeyedpigeon »

mort96 wrote: post #125
oneeyedpigeon wrote: post #87

Earlier quoted context omitted.

Where do you see the google analytics code in the speedometer? It's true that the site his example is running on includes GA, but I can't see anything in the source other than a reference to an analytics build which uses a file that only exists if you choose to create it.

The HTML includes this: window.ga = window.ga || ((...args) => (ga.q = ga.q || []).push(args));ga('create', 'UA-130560367-1', 'auto');ga('set', 'transport', 'beacon');ga('set', 'anonymizeIp', true);ga('send', 'pageview'); The network pane in my browser, when disabling ublock, looks like this: https://s.mort.coffee/d/img/scr-2019-02-03-74462.png

That's on the actual site, isn't it? I acknowledge it's there, but the person I originally replied to claimed it was in the source, which I don't think it is.

Re: Tiny PWAs and why I keep building them

#132

Post by hutzlibu »

memonkey wrote: post #129
hutzlibu wrote: post #128

Earlier quoted context omitted.

That is because of bad usability of the browsers, though. Default should be for example some icon indicating that the website wants more permission ... and then if I feel like it, I grant more permission. Til the point of fully trusting and giving all access. But a website is a website I just read and will never get more permissions from me. But a pwa ... like a game, I would grant more permissions. This is something…

Isn't this usability issue on part of the website developer/ux designer too? What you point out is right, but it can also be implemented in a way where you're not outright just calling the function to pop up that little notification asking for [insert api] permission. It might be a better solution where the ux designer/developer has some sort of button the website that then calls that function for a slightly better e…

" It might be a better solution where the ux designer/developer has some sort of button the website that then calls that function for a slightly better experience"

But this would be up to the websites then. They could do this now, but they aggressively push for all the permissions they can get in the hope at least some click (accidently) yes.

I do not want popups to click away all the time. I want to decide that I like notifications from site x if they offer that.

Re: Tiny PWAs and why I keep building them

#133

Post by lioeters »

leeoniya wrote: post #81
thosakwe wrote: post #53

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…

> 2. The Web is missing some APIs that would really let it compete with native apps. absolutely this. i have no idea why the Contact api [1] work has been discontinued. my current conspiracy theory is that it would have allowed many communication apps to no longer require native apps and cloud-stored address books. like selecting a file to upload, i dont see why i can't select a contact to use/upload from a locally a…

Regarding your conspiracy theory, it sounds like this could be a realistic worry, of a conflict of interest among those influencial in developing web standards. The "missing APIs" may be those which would provide more competition to various walled gardens.

Re: Tiny PWAs and why I keep building them

#134

Post by jstanley »

denniskane wrote: post #43
jstanley wrote: post #33

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.

Did you try the "desk.os" link that is link number 3 on that page... https://linuxontheweb.appspot.com/desk.os ? I can really only guarantee that things work on a relatively recent version of Chrome (like within the last few stable releases). The version that is live now is a couple weeks old. I'm working on some really cool features for the modular synth app right now. I'd love to start sharing this stuff with you g…

How can you use this to implement a speedometer that runs on your phone?

Re: Tiny PWAs and why I keep building them

#135

Post by avhon1 »

varjag wrote: post #39

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

Where I live (Indiana, USA) the authorities would only find out I had a dead dashboard if I got into an accident and they discovered it while investigating. There are no vehicle inspections, ever. As long as I continue to drive without causing incidents, my vehicle's condition is of little significance to anyone except me.

Re: Tiny PWAs and why I keep building them

#136

Post by curiousgal »

oosjc9a5 wrote: post #116
thosakwe wrote: post #53

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 am very happy that the web has no more APIs. I'm already tired enough of telling my browser that I don't want any website to send me notifications, to access my location, to access my camera, my microphone. And God knows what goes behind my back. Enough is enough!

I remember reading about USB access at one point, that'd be fun!

Re: Tiny PWAs and why I keep building them

#137

Post by paulgb »

CharlesW wrote: post #72
thosakwe wrote: post #53

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

It’s a shame they haven’t budged much on push notifications. I know they have a reputation because they are used so much for spammy purposes, but I see that as a UI problem rather than a problem with push notifications themselves. I think if iOS got push notifications we’d start to see non-spammy use cases, e.g. one-click waitlist notifications and no-install turn-based games. One fun use I've found (I have an Android so push is supported) is getting messages with the loss at each training epoch in Keras (see the side project in my profile.)

Re: Tiny PWAs and why I keep building them

#138

Post by avhon1 »

roryisok wrote: post #66
varjag wrote: 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.

I'm comfortable with driving without any of those things -- my motorcycle, for example, only has a speedometer and a non-resettable odometer. (It's like that from the factory. Many street-legal motorcycles are similarly equipped.) You know how much fuel you have by knowing the capacity of you vehicle's tank, how many hours or miles you have driven, and your pre-existing (or found on the internet) knowledge of you vehicle's fuel consumption.

My car's battery gauge has never worked, not in the 20+ years that my father and I have owned it. (I don't know if it worked for the one person that owned it before him, or if it never ever worked.) The only time it would have been helpful is the one time the alternator died. OP has an electric hybrid, so it's a bit more useful to them, but still not critical.

The "check engine light" is helpful to people who know little about their vehicle, telling them "please take me to a mechanic!" Otherwise, they seem to be more annoying than helpful -- the family minivan that said "I need an oil change!" because changing the oil yourself didn't reset the counter, or the endless O2 sensor replacements the SUV wanted. You could learn much more, and with less annoyance, by sticking an inexpensive ODB2 reader into your car once in a while.

Re: Tiny PWAs and why I keep building them

#139

Post by thosakwe »

lioeters wrote: post #133
leeoniya wrote: post #81

Earlier quoted context omitted.

> 2. The Web is missing some APIs that would really let it compete with native apps. absolutely this. i have no idea why the Contact api [1] work has been discontinued. my current conspiracy theory is that it would have allowed many communication apps to no longer require native apps and cloud-stored address books. like selecting a file to upload, i dont see why i can't select a contact to use/upload from a locally a…

Regarding your conspiracy theory, it sounds like this could be a realistic worry, of a conflict of interest among those influencial in developing web standards. The "missing APIs" may be those which would provide more competition to various walled gardens.

I'm not really a fan of conspiracy theories, BUT when you consider that 2/3 of the biggest browser vendors also control mobile platforms, you can kinda start to rationalize it.

Re: Tiny PWAs and why I keep building them

#140

Post by judah »

CharlesW wrote: post #72
thosakwe wrote: post #53

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

Things are slightly better in iOS 12.2 (e.g. web share, slightly better PWA restore to fore), but lots of things are still missing or broken [0].

[0]: https://medium.com/@firt/pwas-on-ios-12-2-beta-the-good-the-...

Post reply on HN