Ask HN: Why mobile software infrastructure never belongs to its owner?
Thread
Unofficial Hacker News client; not affiliated with Y Combinator.
Ask HN: Why mobile software infrastructure never belongs to its owner?
Unofficial Hacker News client; not affiliated with Y Combinator.
coreyp_1 · · focus · HN ↗
Do you mean, for example, Jellyfin, which reaches out to my home server and is for my personal use? Because that works.
Or do you mean why don't we just write our own apps which talk to our own infrastructure?
Or do you mean that it's just hard to have your own/personal infrastructure? Or that most apps don't support your own infrastructure?
Or are you referring to the fact that the mobile platforms lock down things such as push notifications so that it absoultely must go through them?
Can you be a bit more specific?
rezvovmobile · · focus · HN ↗
[dead]
brudgers · · focus · HN ↗
How would changes to it comply with regulatory requirements?
Is it as reliable as the existing system?
Those answers are perhaps where the reasons lie.
rezvovmobile · · focus · HN ↗
[dead]
xp84 · · focus · HN ↗
rezvovmobile · · focus · HN ↗
[dead]
LarryMade2 · · focus · HN ↗
Best bet is to do mobile web development, most of the parts can be under your control and those that aren't (the phone) are beholding to web standards which can't change too radically.
rezvovmobile · · focus · HN ↗
[dead]
ebcode · · focus · HN ↗
rezvovmobile · · focus · HN ↗
[dead]
austin-cheney · · focus · HN ↗
For example I just wanted a WinAmp like experience to play MP3 files using my phone while doing dishes. These MP3 files are on a home file server. I looked at the applications on the app store and they were all shit, even the ones that cost money. I suspect the reasoning is because these applications are crippled in favor of Apple preferred, or in house, solutions.
So, I wrote my own music app. Its just a web page that I can run in a web browser. This allows me to completely bypass iTunes and the app store. Here are the steps I had to jump through to get this to work:
1. The playlist must be static and assembled in advance. There is a JavaScript file system API to get a file list from a directory. It works in desktop Safari but is disabled in iOS Safari. So, I wrote a Node.js app that does this and outputs a JSON with the necessary data.
2. iOS Safari will not load JSON files beyond a certain trivial size. It claims to be a memory issue, which is stupid, because I can bypass this too by using multiple JSON files each containing only 500 records of data. So, my Node.js app has a "split" option to produce multiple data files and my static webpage app requests the local JSON files one by one.