Live data from Hacker News

Tiny PWAs and why I keep building them

justinribeiro.com

91–100 of 178 posts

Re: Tiny PWAs and why I keep building them

#91
post #12

Earlier quoted context omitted.

Firebase has a pretty feature complete free tier.

Good point. Looks like the Firebasee free tier hosting limit is 10 GB/month, so if his speedometer is 1.7 KB, and PWAs only need to be downloaded once by each user, that's ~5.8 million new users/month for free. So basically free forever.

> forever

Google doesn’t have the best track record in the forever department :)

Re: Tiny PWAs and why I keep building them

#93
post #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.

Typical complacent American always living under fear

Re: Tiny PWAs and why I keep building them

#95
post #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.

And many countries are authoritarian shitholes who care more about revenue generation than protecting people. People don't need a speedometer to drive safely.

Chicago is a good example. Nobody follows the speed limit, especially on the express ways (often 30+ over). Going with the flow of traffic is key.

Re: Tiny PWAs and why I keep building them

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

You can already do this. You just need a site to host it on.

Re: Tiny PWAs and why I keep building them

#97
post #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.

How inaccurate is GPS? It seems like for his purposes a variance of even +/- 5 mph could be tolerated given one can generally sense approximately what speed they're traveling and can also compare themselves to other cars on the road.

problem is usually line of sight to satellites, it varies a LOT and usually leads to variance in calculations.

Re: Tiny PWAs and why I keep building them

#98
post #94
post #92

Your car dashboard is broken. Instead of fixing it, you write an app that provides a lousy workaround. Is this meant to be a bad example?

How is it lousy? You seem jealous

goodluck sticking to speed limits by relying on a gps based speedometer...although seeing as how you're on the chamber of commerce in a tiny town that must not be a problem for you

Re: Tiny PWAs and why I keep building them

#99
post #57

Introduce acronyms before you use them. I'll say it again for the people in the back. Introduce acronyms before you use them.

PWA is not an acronym. It's an initialism.

I'll say it again for the people in the back.

PWA is not an acronym. It's an initialism.

Re: Tiny PWAs and why I keep building them

#100
post #62
post #21

Earlier quoted context omitted.

The other, largely unspoken, downside to PWAs are that the user cannot block the tracking and ads in them when launched natively. Even though they might run on your android where you have firefox mobile with all the adblocking extensions enabled, and run that PWA in the browser. I'm sure this might be another reason why PWAs are being supported by the advertising industry platform suppliers.

Speaking of Firefox, there was Firefox OS which appeared to be a stillborn child. It's app distribution model likely was close to PWA's. There's also Chrome OS which has lived longer than its foxy twin, and is going to be incorporated into Android according to wiki. I think PWA is about tooling, like Google's chrome dev tools or Workbox, and frameworks. The good side of it is sharing the codebase/API between app and…

doesn't that live on as KaiOS. kai is heavily controlled by some indian company(to the point where you can't even publish apps on it's store without that company's approval) but atleast it's alive
Post reply on HN