I have been going regularly to the Edinburgh Festival Fringe and their app is always terrible. Connectivity is very spotty since the city is swarmed with way more people than usual and the older buildings can kill your signal.
So I've been working on https://fringeflypost.com/, an event tracker with maps, search and filter, scheduling, and sharing with friends that's offline first. It syncs down a locally stored sqlite database and caches assets pretty aggressively.
(You don't actually need to sign up, and you can just jump into the list of shows directly here https://fringeflypost.com/shows).
As someone who used to pride myself on being able to make complex graphical designs a reality, it has definitely put me into a little bit of an identity crisis. But ultimately I think it just pushes you to find the things that are still hard for AIs, which in turn continues to differentiate your work from what everyone can now generate.
Feels similar to the move away from realism to impressionism as the camera became available.
I'm glad to see more positive takes on client-side rendering. Unless SEO and crawlability are important for your site, server side rendering is such an overprescribed solution. If I put my tin-foil hat on, I'd say it gets a lot of attention because it's a lot easier to charge people for server time spent in SSR that you just don't have in CSR.
Bottom line is, if your app's content is behind a login screen, just use client side rendering. It is way lower complexity and a way better user experience.
The author touches on this in the last section, but I'd reframe this a different way. The natural conclusion for a company who wants to funnel you to the app is, "the web version is a-OK? Let's make the web version worse."
I'd rather see this framed as, "if you don't have a high functioning web version, I don't need to use your service." Gimping my preferred medium will lose me as a customer. If enough people draw that line, "enshittifying" your web app should hurt your metrics, not help. That way maintaining a good web version is looked at as a long-term necessity, not a top of funnel.
I cannot get apps on my iPhone from anywhere else but the App Store. While they are dominant, Valve isn't locking anyone in even on their own hardware.
I'm willing to bet that many people produce code with Claude code that you would not be able to distinguish from a skilled human. Every tool has its uses and misuses.
As a home owner in Austin, I want my friends to be able to afford homes too and not feel like they have to move to have a yard and a family. Bring on the new construction.
> AWS doesn’t charge you in mysterious ways. It charges you in specific, predictable ways that nobody taught you to look for. That’s a knowledge gap. The purpose of this post is to shed some light on this.
Or it's a UX gap. If this is such a common complaint that's causing meaningful reputation damage, surely there'd be a better way to communicate this in the product? I think it's fair to assume that there's less interest in building features that encourage users to spend less money.
Reading what they're offering, the stand-out to me is making publishing the applications easy for others on your team to use. That would he a pain point for non technical users.
Most organizations I've set Sentry up for tunnel the traffic through their own domain, since many blocking extensions block sentry requeats by default. Their own docs recommend it as well. All that to say, it's not trivial to fully block it and you were probably sending telemetry anyway even with the domain blocked.
"South Korea is second from bottom on our list in terms of the proportion of people saying their country “is heading in the right direction”, with only 15% stating so. A similar sentiment is also felt about the economy. Pessimism is usually the standard for South Korea; however, their economic indicator score has been particularly low in recent times, with just 8% believing the economy is “good”."
Drop me a line at hn at wbobeirne dot com.