Top
Best
New

Posted by 0xblinq 2 days ago

I built the same app 10 times: Evaluating frameworks for mobile performance(www.lorenstew.art)
231 points | 150 commentspage 4
IlikeKitties 2 days ago|
> The web is mobile. Build for that reality.

Ugh. That thinking is what gets you things like mandatory login via apps for your desktop. And not every application makes sense on a phone. And some Web Applications just require low latency high bandwidth internet to work properly.

masklinn 2 days ago||
> some Web Applications just require low latency high bandwidth internet to work properly.

But the vast majority do not. And this haranguing is an opportunity / defensible position to put more efforts and resources into performances. If nothing else, think of it as a Trojan horse to make software suck less.

IlikeKitties 2 days ago|||
>If nothing else, think of it as a Trojan horse to make software suck less.

My experience has been that the proliferation of mobile devices has made my desktop experience consistently worse and I struggle to come up with an example where it didn't.

exe34 2 days ago|||
> But the vast majority do not. yeah and that's why they are shit and barely work.

Even a php app without decorations would be faster and better for most applications.

HelloUsername 2 days ago||
> That thinking is what gets you things like mandatory login via apps for your desktop.

"the web is mobile" = strictly "apps" ?

koolala 2 days ago||
Can Marko run static without a server? Can any of these?
mpeg 2 days ago||
All of them can, but you get most benefit of a full-stack javascript framework if you are indeed running server js. But you can build statically in any of them (assuming you are not using any server-only features) and deploy as plain html/js.
aetherspawn 2 days ago|||
Yeah, Svelte can.
jakewins 2 days ago||
Can’t most of them? Certainly React and Angular can as well.
mulhoon 2 days ago||
Nuxt can too
tripu 1 day ago||
“Next-gen frameworks [Marko, SolidStart, SvelteKit, Nuxt] deliver instant performance. […] The real performance story isn't splitting hairs over 3ms differences, it's the massive gap between next-gen and React/Angular.”
lorenstewart 17 hours ago|
A maintainer refactored the Analog app, so it's doing much better than before. The post has been updated.
muzani 2 days ago||
I'm surprised there's no mention of Flutter. If the goal is mobile performance, Flutter would be top of mind - you can build to both native apps and web.
h33t-l4x0r 2 days ago||
150kb downloads almost instantly, even on 3G. Most websites have an image bigger than that somewhere on their homepage. It's not worth changing how I work.
troupo 2 days ago||
See Performance Inequality Gap https://infrequently.org/2024/01/performance-inequality-gap-...

Your attitude is exactly why our supercomputers struggle to display even the simplest things with any kind of performance, and why pure text takes multiple seconds to appear

panstromek 2 days ago|||
JS can be 100x or even 1000x times more expensive to process than images. JS also blocks the main thread, while images can be processed in the background (and on GPU).
sgt 2 days ago|||
If it was only 150kB for most sites. Usually that's followed up with multiple assets, API calls, often chained. Making the site slow.
mpeg 2 days ago||
The app in the article is a relatively simple demo app. These are the build times and sizes from a real relatively large react SPA I help maintain

  dist/assets/app.css   98.33 kB │ gzip:  17.69 kB
  dist/assets/app.js    1,050.14 kB │ gzip: 244.88 kB
   built in 15.41s
At these sizes, an islands/resumable based approach can trim a ton of loading time on mobile
pbreit 2 days ago||
Seems overly concerned with bundle size which I'm not sure really ever matters? Certainly smaller is better but is it that big of an impact?
panstromek 2 days ago|
Yes, it matters a lot, especially on mid/low end devices.
kburman 2 days ago||
Any reason to not include native application given how important mobile experience was.
mkl 2 days ago||
Reasons are given near the end:

> Here’s where this gets bigger than framework choice. When you ship a native app to the App Store or Google Play instead of building a web app, you’re not just making a technical decision. You’re accepting a deal that would’ve been unthinkable twenty years ago. Apple and Google each take up to 30% of every transaction (with exceptions depending on program and category). They set rules. They decide what you can ship. They can revoke your access tomorrow with no recourse. You have no alternative market. You can’t even compete on price because the fee is baked into many transactions.

PeterStuer 2 days ago||
Appstores complicate lifecycles by orders of magnitude.
antiloper 2 days ago||
> ... all deliver instant 35-39ms performance. The real differentiator? ...

Thanks ChatGPT for your valuable slop. Next article.

bschwindHN 2 days ago|
(I'll be that guy since the article emphasizes a good mobile web experience so hard)

You might want to fix your horizontal scroll on mobile. I should basically never have a full page horizontal scrollbar on a page that is mostly just text.

More comments...