fevangelou
Joined 13 years ago
Joined 13 years ago
Supports multiple languages (more to be added - auto switch enabled) and is built with pure Vanilla HTML, CSS & JS — zero external frameworks, libraries or build tools.
As a PWA, it can also be installed on any device for quick access.
Zero ads, seamless updates.
P.S. This was purpose built, out of pure necessity, as it got frustrating having a simple app that is kid-friendly to draw on any device.
Thank you for building and sharing this.
For RSS/Atom feeds presented as links in a site (for convenience to users), developers can always offer a simple preview for the feed output using: https://feedreader.xyz/
Just URL-encode the feed like so: https://feedreader.xyz/?url=https%3A%2F%2Fwww.theverge.com%2...
...and you get a nice preview that's human readable.
We're already seeing some ad networks using initialization scripts to bootstrap their ad setup, with dynamically constructed secondary scripts that have a high fetchpriority (so they supposedly load faster than others).
For reference, modern news/media sites may load multiple ad networks (3-4 on average perhaps) in order to optimize ad performance (revenue) or inject different kinds of ads or sponsored content. If we take Google's Ad Manager (or similar) as the base network to serve ads (own or third-party), many times we see additional networks like AdSense, Taboola, Outbrain, Vidverto (to name a few) or other local ad networks that do some sort of header bidding, ad injection, sponsored content display, in-read ads/videos and so on.
I don't see why some won't abuse this spec to force-inject their stuff earlier than other ad networks and of course at the expense of a site's performance...
Which is crucial Netlify is called out for this. Hiding behind the "fine print" is pathetic, not a way to do business.
As someone who's worked primarily on news/media sites for the last 15 years, I can totally relate and agree on all your points.
I would also argue that there are non-code issues that could easily be resolved. Bundling fonts for example. Decide on the top 100 with support for all or almost all characters, based on usage etc., and bundle them in the browser. That would shave possibly hundreds of KBs of each page's size.
On the flip side, stuff like lazy loading could become standard and use the attribute only to force-load content. Or stuff that is used on every freaking site (eg togglers as native html tags).
I'm hopeful though.
So yeah, sometimes niche markets can be profitable. And it doesn't have to be millions of dollars in VC money obviously to be invested.