News for hackers. Stuff that matters.
Re:Tiny PWAs and why I keep building them by wffurr on Sunday February 03, 2019 @06:45AM (#19069091)
What happens to your PWA page weight when you add tracking and ads to it?

How do I find your ad-free hobby project in the sea of search results for "speedometer" PWAs on the open web?

What makes sure you will keep paying the, admittedly modest, hosting costs for the app?

I think it's great you can make "tiny PWAs" but I think the article is glossing over the incentives and discovery problem that leads to 30MB ad-infested utility apps on the play store.

Re:Tiny PWAs and why I keep building them by chippy on Sunday February 03, 2019 @07:46AM (#19069302)
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.
Re:Tiny PWAs and why I keep building them by oneeyedpigeon on Sunday February 03, 2019 @08:26AM (#19069446)
That's not a downside versus native apps, though.
Re:Tiny PWAs and why I keep building them by enz on Sunday February 03, 2019 @09:16AM (#19069644)
I've "installed" this PWA via Brave on Android. So it now runs upon the Brave engine when I launch it, I suppose. I hope Brave continues to block trackers when executing "installed" PWAs.
Re:Tiny PWAs and why I keep building them by Klathmon on Sunday February 03, 2019 @09:26AM (#19069686)
I didn't think it worked like that, but I could be super wrong.

Last I saw things launched from the home screen or in a webview from another app use the "Android System Webview" as it's rendering engine.

IIRC there was some work done to make that runtime swappable, but I'm not sure how far that went.

Re:Tiny PWAs and why I keep building them by callahad on Sunday February 03, 2019 @10:21AM (#19070017)
It's possible. E.g., PWAs installed via Firefox on Android use Gecko, not the system WebView.
Re:Tiny PWAs and why I keep building them by enz on Sunday February 03, 2019 @06:36PM (#19072916)
Thanks for confirming. It is indeed great if things works that way!
Re:Tiny PWAs and why I keep building them by Klathmon on Sunday February 03, 2019 @12:58PM (#19071087)
Oh wow that's awesome I had no idea, thanks!
Re:Tiny PWAs and why I keep building them by Eli_P on Sunday February 03, 2019 @10:29AM (#19070055)
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 website. The bad side is you may bet on the stillborn/transient tech and will have to rewrite or monkey-patch everything.

And ads were never the only business model, it's developer's choice. There are apps for Android w/ decent prices and w/o annoying banners. PWA is no different.

The convergent evolution leaves nothing untouched. I think if proliferate rate of web frameworks continues to grow exponentially, we'll have to deploy docker images right into the browser. I mean, it was a joke. Was it?

Re:Tiny PWAs and why I keep building them by ergothus on Sunday February 03, 2019 @02:21PM (#19071568)
I was completely distracted from your point when you mentioned the "foxy twin" of the "stillborn child". I know foxy had a double entendre here, but...uh...disturbing choice of words.
Re:Tiny PWAs and why I keep building them by kkarakk on Sunday February 03, 2019 @12:04PM (#19070707)
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
Re:Tiny PWAs and why I keep building them by oneeyedpigeon on Sunday February 03, 2019 @06:56AM (#19069128)
He describes it as an app essentially for his own use - there IS no business model. He’s not going to need to add tracking or ads.
Re:Tiny PWAs and why I keep building them by RodgerTheGreat on Sunday February 03, 2019 @11:21AM (#19070418)
Viewing the source of the reading light and speedometer reveals that both include google analytics tracking code.
Re:Tiny PWAs and why I keep building them by oneeyedpigeon on Sunday February 03, 2019 @11:27AM (#19070459)
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.
Re:Tiny PWAs and why I keep building them by mort96 on Sunday February 03, 2019 @02:40PM (#19071707)
The HTML includes this:

    <script async="" src="https://www.google-analytics.com/analytics.js"></script>
    <script>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');</script>
The network pane in my browser, when disabling ublock, looks like this: https://s.mort.coffee/d/img/scr-2019-02-03-74462.png
Re:Tiny PWAs and why I keep building them by oneeyedpigeon on Sunday February 03, 2019 @03:32PM (#19071994)
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 by oskarla on Sunday February 03, 2019 @07:52AM (#19069321)
> How do I find your ad-free hobby project in the sea of search results for "speedometer" PWAs on the open web?

https://appsco.pe

Re:Tiny PWAs and why I keep building them by pjmlp on Sunday February 03, 2019 @12:38PM (#19070945)
That's cool, thanks for sharing.
Re:Tiny PWAs and why I keep building them by jstanley on Sunday February 03, 2019 @07:07AM (#19069173)
> What makes sure you will keep paying the, admittedly modest, hosting costs for the app?

I thought the point of a PWA is that it is installed on the phone. So it doesn't need any hosting.

For the initial distribution, IPFS would be a good fit. It ensures a.) That even if the original developer is compromised you still don't get a malicious app, and b.) That even if the original developer stops hosting it, it's still available as long as anyone in the world is hosting it.

Re:Tiny PWAs and why I keep building them by rthomas6 on Sunday February 03, 2019 @06:58AM (#19069138)
Hosting static content can be done for free. Looks like he's using Firebase, but I believe you could host it on Netlify/Github Pages for $0, since there's no server side work being done.
Re:Tiny PWAs and why I keep building them by avip on Sunday February 03, 2019 @07:03AM (#19069153)
Firebase has a pretty feature complete free tier.
Re:Tiny PWAs and why I keep building them by rthomas6 on Sunday February 03, 2019 @07:13AM (#19069196)
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.
Re:Tiny PWAs and why I keep building them by avtar on Sunday February 03, 2019 @11:46AM (#19070584)
> forever

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

Re:Tiny PWAs and why I keep building them by etaerc on Sunday February 03, 2019 @12:25PM (#19070849)
No, he's saying you can build this stuff on your own and don't need to grab it from anywhere.
Re:Tiny PWAs and why I keep building them by z3t4 on Monday February 04, 2019 @06:21AM (#19075433)
If it has offline support you can simply save it to your computer, or use "add to desktop" in iOS and Chrome browser.