Live data from Hacker News

Why the future is local app

getapps.cafe

51–60 of 77 posts

Re: Why the future is local app

#51
post #3

The future is you pay $1000 for a "cloud terminal" with 4 GiB of RAM and maybe 128 GiB of storage, and all of your apps live, metered, in the cloud. Arbitrary operating systems, and even arbitrary application binaries, are not allowed, in order to comply with laws and regulations, as well as non-legally-binding policies set by credit card companies in response to pressure groups, on what you may compute and what you…

So why can i still run all my decentralised apps? Where's this magical shutdown the government is going to do? Are they going saturate the airwaves to destroy mesh networks or hunt every mesh node on the planet? Go home with your nihilism.

Because Google hasn't yet rolled out full blocking of unapproved APKs.

Re: Why the future is local app

#52
post #9

This really matters in map apps when you're on the road. Apple Maps is all very nice with transit planning but without a solid net connection it lies there mutely. Organic Maps (and others) that use downloaded OSM data work well with nothing more than GPS. You can get a transit plan (trains & trams & buses, and the transfers among them) without up-to-the-minute arrival info.

> “Apple Maps … without a solid net connection it lies there mutely.”

Worse, without a net connection you can’t even get the phone to start a route.

Re: Why the future is local app

#53
post #38

Earlier quoted context omitted.

Yes, and Organic Maps and Maps.Me do the same - download entire countries or regions. It is SO tremendously useful when traveling. Have not tried CoMaps yet.

Maps.me, Organic Maps and CoMaps are all the same family. Maps.me used to be an open source project, when they took it closed source and tried to commercialize it, the last open source version was forked and is now known as Organic Maps. Then the Organic Maps maintainer started acting sketchy, introduced a paid partnership with Kayak and generally not behaving in a very community minded way. Organic Maps was forked a…

What's the secret sauce for transferring one's own annotations and notes among all these apps ?

Re: Why the future is local app

#54
post #39

Earlier quoted context omitted.

Well, thanks to evergreen and auto updating systems, there's no guarantee that X app will be the same today and tomorrow. It's probably what I hate most about Android- apps shouldn't need an update as often as they do.

It is really like some vendor breaking into your house and changing your furniture because "it looks better now". Should be illegal.

Couldn't log in to the NHS app because of an update last week. The update?

"Resolve login issues by improving forgotten password messaging"

Hold up a whole queue in a pharmacy to change some fucking text lol.

Re: Why the future is local app

#55
post #46

Earlier quoted context omitted.

You're not wrong, but this feels like an equivalent to range-anxiety in electric cars. The area you can download is still pretty large - whole cities, big chunks of countryside. I'd put money on the fact its good enough for most people's uses.

> I'd put money on the fact its good enough for most people's uses. I don't know anyone (and I mean exactly zero) who ever used the offline feature of Google Maps. Online is good enough for people who almost always have an Internet connection. What happens when they don't is that they don't have access to the map. People who care about having offline access (because they live in a place where they don't always have I…

> People who care about having offline access (because they live in a place where they don't always have Internet or just because they care) don't bother using the Google offline feature. They use proper offline maps instead.

Have lived in Alaska. Used offline Google maps. Worked perfectly for years and years.

Re: Why the future is local app

#56
post #50
post #26

Earlier quoted context omitted.

> it would be best if developers all over the world boycotted proprietary platforms entirely. Note that Linux and Android, from your list, are open source. > For true cross-platform, you need to develop for 5 platforms I would argue that anyway , you should develop for multiple "kinds of devices". Writing the same code for a desktop computer and a smartphone is fundamentally a mistake: I don't want to slide big butto…

Android is closed-source but with some open-source components, for only some of which they'll actually follow the license and give you the source code.

AOSP means "Android Open Source Project". You can get the sources of Android, modify them, and build the whole OS. The Android SDK is open source as well.

GrapheneOS is based on Android precisely because Android is open source. They couldn't do that with iOS, or Windows, or any proprietary OS. Same for LineageOS.

Honestly it seems like you don't really know what you are talking about here?

Re: Why the future is local app

#57
These are all arguments I made during the "screw it, move it all to the cloud, don't think, just do!" years of the mid 2010s to early 2020s. It's so frustrating to only now see people bringing these legitimate points to light, after everyone has lost so much money yeeting it upstairs and forgetting about it until the bill drained them dry.

Re: Why the future is local app

#58
post #56
post #50

Earlier quoted context omitted.

Android is closed-source but with some open-source components, for only some of which they'll actually follow the license and give you the source code.

AOSP means "Android Open Source Project". You can get the sources of Android, modify them, and build the whole OS. The Android SDK is open source as well. GrapheneOS is based on Android precisely because Android is open source. They couldn't do that with iOS, or Windows, or any proprietary OS. Same for LineageOS. Honestly it seems like you don't really know what you are talking about here?

AOSP isn't Android. Nor is the Android SDK.

Also you can totally fork iOS, in binary form, on the dark web, and run it somewhere that isn't an iPhone.

Re: Why the future is local app

#59
post #46

Earlier quoted context omitted.

You're not wrong, but this feels like an equivalent to range-anxiety in electric cars. The area you can download is still pretty large - whole cities, big chunks of countryside. I'd put money on the fact its good enough for most people's uses.

> I'd put money on the fact its good enough for most people's uses. I don't know anyone (and I mean exactly zero) who ever used the offline feature of Google Maps. Online is good enough for people who almost always have an Internet connection. What happens when they don't is that they don't have access to the map. People who care about having offline access (because they live in a place where they don't always have I…

Really? I'm genuinely surprised.

I've used it plenty for things like driving trip to remote places with poor signal (e.g. where you'll want to be able to get directions back to civilisation) and foreign cities (when you're on a phone contract with bad overseas data prices).

Re: Why the future is local app

#60
post #58
post #56

Earlier quoted context omitted.

AOSP means "Android Open Source Project". You can get the sources of Android, modify them, and build the whole OS. The Android SDK is open source as well. GrapheneOS is based on Android precisely because Android is open source. They couldn't do that with iOS, or Windows, or any proprietary OS. Same for LineageOS. Honestly it seems like you don't really know what you are talking about here?

AOSP isn't Android. Nor is the Android SDK. Also you can totally fork iOS, in binary form, on the dark web, and run it somewhere that isn't an iPhone.

Ok teach me. What is Android?
Post reply on HN