Earlier quoted context omitted.
> You can find tons of purely local apps tha[t] monetize themselves with a[d]s. How do they do that without hitting the internet?
It's "local first", not "local only".
Sorry, a "purely local app" isn't "local only"?
Local-first software (2019)
101–110 of 308 posts
Re: Local-first software (2019)
#102Self hosting (which is often adjacent to local-first software) is fine. I've done it for years. But it is a nightmare when it goes wrong: the conclusion I've reached is that it is out of reach to regular people who don't want the Byzantine support load that could accompany something going wrong. They want turnkey. They want simple. They aren't interested in operating services, they're interested in using them. The FL…
This is the business model I want to have: I work on a stack of fully open source software and package them in a turn-key server that you own. You can use it on your own for free if you’re knowledgeable and I offer a subscription where I’m the sysadmin of the box you own and that I built for you. I do the maintenance, the updates, etc. There’s no lock-in because you can stop the subscription anytime or even just pick another sysadmin that would know the stack. The only reason you’d keep me around would be that the service I offer is pretty damn good. Would something like that appeal to you?
Re: Local-first software (2019)
#103Earlier quoted context omitted.
The entire thing is because of subscription revenue. It’s self reinforcing because those companies that get subscription revenue have both more revenue and higher valuations enabling more fund raising, causing them to beat out companies that do not follow this model. This is why local first software died.
I remember seeing somebody summarize this as "SaaS is a pricing model" or "SaaS is financialization" and it totally rings true. Compared to normal software pricing, a subscription gives you predictable recurring revenue and a natural sort of price discrimination (people who use your system more, pay more). It's also a psychological thing: folks got anchored on really low up-front prices for software, so paying $2000…
It's the missing middle. A manager can just expense $25/mo, while $2000 requires an approval process, which requires outside sales, which means it really costs at least $20,000.
Re: Local-first software (2019)
#104Yes a thousand percent! I'm working on this too. I'm sick of everyone trying to come up with a use case to get all my data in everyone's cloud so I have to pay a subscription fee to just make things work. I'm working on a fitness tracking app right now that will use the sublime model - just buy it, get updates for X years, sync with all your devices and use it forever. If you want updates after X years buy the newest…
How do you plan to do the syncing without some sort of cloud infrastructure?
Something like Syncthing, perhaps?
Re: Local-first software (2019)
#105Anything with online dependencies will necessarily require ongoing upkeep and ongoing costs. If a system is not local-first (or ideally local-only), it’s not designed for long-term dependability. Connected appliances and cars have got to be the stupidest bit of engineering from a practical standpoint.
The entire thing is because of subscription revenue. It’s self reinforcing because those companies that get subscription revenue have both more revenue and higher valuations enabling more fund raising, causing them to beat out companies that do not follow this model. This is why local first software died.
Pretty much greed being a universally destructive force in the world as usual.
When Apple joined the madness, all hopes where lost (that was a long time ago now, sight)
Re: Local-first software (2019)
#106Yes a thousand percent! I'm working on this too. I'm sick of everyone trying to come up with a use case to get all my data in everyone's cloud so I have to pay a subscription fee to just make things work. I'm working on a fitness tracking app right now that will use the sublime model - just buy it, get updates for X years, sync with all your devices and use it forever. If you want updates after X years buy the newest…
How do you plan to do the syncing without some sort of cloud infrastructure?
right now its in webrtc
Re: Local-first software (2019)
#107Most of that stuff was very much over engineered in the last two decades.
The backend for my personal notes, tasks, bookmarks, calendar and feeds are files in directories synced with Syncthing across devices.
I ended there after going from one app to another and being tired of all this.
It is self hosted with no server backend (beyond a Syncthing on a NAS or VPS, optional). It is very reliable and works without Internet connection.
I could have put everything in sqlite too and sync it one way or another, but it seemed already too complicated for my requirements.
I can't share it beyond my close relatives but I had the same problem with people using Google or Microsoft before.
Re: Local-first software (2019)
#108Earlier quoted context omitted.
haha, 100% real. not a native speaker though, so sometimes i catch myself mimicking that LLM tone from all the exposure to them. appreciate the feedback, will definitely work on developing a more authentic writing style from now on. but yeah, you're right to be concerned, i'm seeing bots everywhere too.
Persona: You are a tech enthusiast on the forum Hacker News. Your tone is curious, positive, and slightly formal. Primary Task: Read the top comment. Identify the core project or idea the user is passionate about. Generate a brief, supportive reply that does the following: 1. Briefly affirm their main point. 2. Ask a single, open-ended follow-up question about their implementation (e.g., tech stack, architecture, a s…
Also suddenly stop using capital letters for, IDK, added texture?
Re: Local-first software (2019)
#109[dead]
Re: Local-first software (2019)
#110Earlier quoted context omitted.
Persona: You are a tech enthusiast on the forum Hacker News. Your tone is curious, positive, and slightly formal. Primary Task: Read the top comment. Identify the core project or idea the user is passionate about. Generate a brief, supportive reply that does the following: 1. Briefly affirm their main point. 2. Ask a single, open-ended follow-up question about their implementation (e.g., tech stack, architecture, a s…
Also suddenly stop using capital letters for, IDK, added texture?
Good point. And 1-2 typos and common grammar mistakes.