Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Developing for Android is like being a demonetized YouTuber

gbl08ma.com

Post reply on HN
Print view View original

31–40 of 118 posts

Re: Developing for Android is like being a demonetized YouTuber

#31

Post by chaisoftware »

Arnt wrote: post #29
chaisoftware wrote: post #28

Earlier quoted context omitted.

> then Android's built-in file picker starts up This is not a good thing for VR apps. Unless there's a VR system file picker in the works that I'm unaware of..

I'm curious. Suppose you're a VR app and you invoke a picker to open a... I don't know... you want to open a sound file. How should the picker's UI be to fit into your general VR interface? If a sound file is particularly badly suited, then some other kind of file (but in that case I'm interested in why that's easier/better than sound).

Not sure I understand the question exactly. Generally, a file picker UI could look exactly the same in VR as it does out of VR, just projected on a flat surface.

The crucial point is to remain inside the stereoscopic VR view since exiting VR is very disruptive.

Re: Developing for Android is like being a demonetized YouTuber

#32

Post by pragmaticlurker »

cm2187 wrote: post #22
IloveHN84 wrote: post #18

Here people is complaining about Google bad policies..but have you ever seen/read/experienced changes in iOS ecosystem? All the new SDK versions must support newer devices while deprecating old versions of iOS. At least, you pay a fee of 25$ and it's on you (or Google). Paying 99$/year and still experiencing some strong frustration at each newer release and change is much more for fetishism

I compare that to Windows which has been around two decades longer than iOS and Android and which APIs have remained remarkably stable and backward compatible. It is possible to do it. It is just more work.

Agree, but Microsoft has another target, such as big Enterprises clients

Re: Developing for Android is like being a demonetized YouTuber

#33

Post by gmueckl »

fattire wrote: post #16

Android's Storage Access Framework is really underrated. Just ask the user to choose a document (file or image or whatever) by firing an intent-- then Android's built-in file picker starts up and you don't have to deal with implementing any of that UI experience. After the user picks the file, a content:// URI is returned back. https://developer.android.com/guide/topics/providers/documen... Best part-- along with the…

So how would a file manager work then? I have used several file managers over the years that allowed me to conveniently manage files locally and remotely. E.g. extract the downloaded zip file locally, edit ome of them, copy these 20 selected extracted files via SCP and delete these three folders.

Granted, I only do that on a phome in a pinch but having these features saved me more than once. I dom't want Android to become as restrictive and underpowered as iOS feels to me.

Re: Developing for Android is like being a demonetized YouTuber

#34

Post by Tsubasachan »

cm2187 wrote: post #22
IloveHN84 wrote: post #18

Here people is complaining about Google bad policies..but have you ever seen/read/experienced changes in iOS ecosystem? All the new SDK versions must support newer devices while deprecating old versions of iOS. At least, you pay a fee of 25$ and it's on you (or Google). Paying 99$/year and still experiencing some strong frustration at each newer release and change is much more for fetishism

I compare that to Windows which has been around two decades longer than iOS and Android and which APIs have remained remarkably stable and backward compatible. It is possible to do it. It is just more work.

Not anymore. Windows as a service is starting to break things now.

Re: Developing for Android is like being a demonetized YouTuber

#35

Post by indigo945 »

cm2187 wrote: post #22
IloveHN84 wrote: post #18

Here people is complaining about Google bad policies..but have you ever seen/read/experienced changes in iOS ecosystem? All the new SDK versions must support newer devices while deprecating old versions of iOS. At least, you pay a fee of 25$ and it's on you (or Google). Paying 99$/year and still experiencing some strong frustration at each newer release and change is much more for fetishism

I compare that to Windows which has been around two decades longer than iOS and Android and which APIs have remained remarkably stable and backward compatible. It is possible to do it. It is just more work.

Well, to be fair, this comes at the cost of Windows (like other major desktop operating systems) being considerably less secure than Android or iOS. This tradeoff is not easy to avoid except by designing the permission model to be sane from the start, and we all know that good upfront design doesn't exist.

Re: Developing for Android is like being a demonetized YouTuber

#36

Post by scarface74 »

IloveHN84 wrote: post #18

Here people is complaining about Google bad policies..but have you ever seen/read/experienced changes in iOS ecosystem? All the new SDK versions must support newer devices while deprecating old versions of iOS. At least, you pay a fee of 25$ and it's on you (or Google). Paying 99$/year and still experiencing some strong frustration at each newer release and change is much more for fetishism

Seeing that the newest phone that doesn’t support the latest version of iOS was released in 2012, I don’t see a problem with Apple deprecating older versions of iOS.

Re: Developing for Android is like being a demonetized YouTuber

#38

Post by oarsinsync »

indigo945 wrote: post #35
cm2187 wrote: post #22

Earlier quoted context omitted.

I compare that to Windows which has been around two decades longer than iOS and Android and which APIs have remained remarkably stable and backward compatible. It is possible to do it. It is just more work.

Well, to be fair, this comes at the cost of Windows (like other major desktop operating systems) being considerably less secure than Android or iOS. This tradeoff is not easy to avoid except by designing the permission model to be sane from the start, and we all know that good upfront design doesn't exist.

Legacy baggage also comes at the cost of performance, which in the case of mobile devices, means reduced battery life.

As an app developer, it's immensely frustrating to have to keep updating apps to stay on top of the latest SDK.

As a mobile user, I delete apps that get flagged up as battery hogs.

So that leaves me with a fairly simple choice, and I keep stuff updated if I expect anyone to keep using it, and if I abandon it, I shouldn't be surprised when my users do the same.

Re: Developing for Android is like being a demonetized YouTuber

#39

Post by icebraining »

gmueckl wrote: post #33
fattire wrote: post #16

Android's Storage Access Framework is really underrated. Just ask the user to choose a document (file or image or whatever) by firing an intent-- then Android's built-in file picker starts up and you don't have to deal with implementing any of that UI experience. After the user picks the file, a content:// URI is returned back. https://developer.android.com/guide/topics/providers/documen... Best part-- along with the…

So how would a file manager work then? I have used several file managers over the years that allowed me to conveniently manage files locally and remotely. E.g. extract the downloaded zip file locally, edit ome of them, copy these 20 selected extracted files via SCP and delete these three folders. Granted, I only do that on a phome in a pinch but having these features saved me more than once. I dom't want Android to b…

The Framework lets you ask for access to a whole directory, not just individual files.

Re: Developing for Android is like being a demonetized YouTuber

#40

Post by gmueckl »

icebraining wrote: post #39
gmueckl wrote: post #33

Earlier quoted context omitted.

So how would a file manager work then? I have used several file managers over the years that allowed me to conveniently manage files locally and remotely. E.g. extract the downloaded zip file locally, edit ome of them, copy these 20 selected extracted files via SCP and delete these three folders. Granted, I only do that on a phome in a pinch but having these features saved me more than once. I dom't want Android to b…

The Framework lets you ask for access to a whole directory, not just individual files.

How is that solving the issue? How can that result in a local and remote file manager with a consistent GUI?
Post reply on HN