Nick Bess

Nick Bess

Web designer

Badges

Tastemaker
Tastemaker
Gone streaking
Gone streaking
Gone streaking 5
Gone streaking 5

Recently Supported

Explaining Ukraine Podcast
Explaining Ukraine Podcast Explaining Ukraine, its politics, society, and culture🇺🇦
Fuelfinance Cloud-based financial department for startups
Mozilla VPN
Mozilla VPN A VPN from the trusted pioneer in internet privacy.
Remote Health
Remote Health Global health insurance for remote teams and individuals
Square Online Store
Square Online Store Build your own online store with Square
Loop Earplugs Avoid hearing loss without looking like a dork
Smalls: Food for Cats Cat food except actually healthy
Ask The Caterpillar
Ask The Caterpillar A chatbot that provides easy access to info about drugs

Forums

Is It Crazy to Build a Local App in a Browser-First, AI-Driven World?

Every day, the PH feed is packed with shiny new SaaS tools most of them browser-based, many of them AI-infused. It s exciting, no doubt. But compared to a time not so long ago, something seems missing: local desktop apps.

They re rare now, and it makes me wonder are native apps still worth building, or have they quietly slipped into the realm of nostalgia?

After all, web apps offer clear benefits for both users and makers or investors. Users don t have to install anything, updates are seamless, and their data is accessible from any device with a browser. For investors, the advantages are just as compelling: a single tech stack, easier user onboarding, lock-in effects, and plenty of levers for driving growth and virality.

How did you build a local-first react native app?

I'm curious how people build local-first apps. I don't need full CRDT support, but more just syncing with a "parent" db (both pulling new data and pushing locally created records).
I see tinybase which feels maybe a bit more powerful than what I need (?).

I also see livestore which feels scary to build on something that new.
Is there a non-hack way to use sqllite and sync to a postgres db?
Basically my criteria in order of importance would be:
1. stays out of my way (easy to deploy, migrate, use)
2. has leverage with types (a standard linter tells me I'm blowing up the app with the code I just wrote)
3. stable (I would ideally just learn a "goto" tool and use that on all projects going forward)

Nicolas Garcin

12mo ago

Code or no-code? Or code for no-code :)

Would you rather: Build with no-code or code it yourself? Be honest: Are you team no-code for speed or team hand-coded for control? Personally, I think no-code is the future, that's why I am writing code for Paage.
View more