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

41–50 of 118 posts

Re: Developing for Android is like being a demonetized YouTuber

#41

Post by robin_reala »

chronogram wrote: post #30
Arnt wrote: post #29

Earlier quoted context omitted.

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).

Boxes and drawers. A sound file could be in a collection of records or CDs or tapes. Making it just like real life is like having your users start off with the manual already read. I’m afraid a general Android VR item picker will be a lot more boring though.

And thus was born Microsoft Bob.

Re: Developing for Android is like being a demonetized YouTuber

#42

Post by specialist »

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.

Win16/Win32, sure. Everything else, eg DLLs, I bundled known good with the app. Microsoft was notorious for slipstreaming changes.

Re: Developing for Android is like being a demonetized YouTuber

#43

Post by yjftsjthsd-h »

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…

I've seen it as "use the file picker to select the parent folder" which works fine

Re: Developing for Android is like being a demonetized YouTuber

#44

Post by icebraining »

gmueckl wrote: post #40
icebraining wrote: post #39

Earlier quoted context omitted.

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?

The file manager would ask you to pick (using the Android UI, via SAF) the directory where you had downloaded the zip, then everything would work the same.

Alternatively, the app can register itself as opener of zip files, then it could extract them freely to its own private directory (without asking for permissions) and let you list and upload them.

Re: Developing for Android is like being a demonetized YouTuber

#45

Post by yjftsjthsd-h »

scarface74 wrote: post #36
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.

People use older devices.

Re: Developing for Android is like being a demonetized YouTuber

#46

Post by jaegerpicker »

wetpaws wrote: post #10
sadris wrote: post #4

I had 90% piracy rate on Android when I did it years ago. Gave up and didn't look back.

Anecdotally, 75% of my sales are on Android and only 25% on iOS.

In my experience very few people can say that. With all of the apps (games, line of business apps, audio visual apps) I've been involved with 90% of the sales/installs were iOS and 10% Android. IMO Android is rarely worth supporting for most apps. Not to mention huge piracy rates.

Re: Developing for Android is like being a demonetized YouTuber

#47

Post by scarface74 »

yjftsjthsd-h wrote: post #45
scarface74 wrote: post #36

Earlier quoted context omitted.

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.

People use older devices.

https://developer.apple.com/support/app-store/

80% of all iOS devices are on iOS 12. An additional 12% are on iOS 11. Any device that can run iOS 11 can also run iOS 12.

By not supporting older devices, you are missing out on at most 8% of the iOS population. But even some percentage of those are able to update to iOS 12.

To target anything older than the 5s means you also have to target 32 bit processors. How much time are you going to spend targeting such a small user base?

Besides, if you have an older version already in the App Store, they can download “the last compatible version”.

Re: Developing for Android is like being a demonetized YouTuber

#48

Post by yjftsjthsd-h »

scarface74 wrote: post #47
yjftsjthsd-h wrote: post #45

Earlier quoted context omitted.

People use older devices.

https://developer.apple.com/support/app-store/ 80% of all iOS devices are on iOS 12. An additional 12% are on iOS 11. Any device that can run iOS 11 can also run iOS 12. By not supporting older devices, you are missing out on at most 8% of the iOS population. But even some percentage of those are able to update to iOS 12. To target anything older than the 5s means you also have to target 32 bit processors. How much t…

8% of the iOS user base is still millions of people

Re: Developing for Android is like being a demonetized YouTuber

#49

Post by gmueckl »

icebraining wrote: post #44
gmueckl wrote: post #40

Earlier quoted context omitted.

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

The file manager would ask you to pick (using the Android UI, via SAF) the directory where you had downloaded the zip, then everything would work the same. Alternatively, the app can register itself as opener of zip files, then it could extract them freely to its own private directory (without asking for permissions) and let you list and upload them.

This is all a load of crappy workarounds leading to a convoluted and cumbersome user experience. From a usability perspective, I would not consider such a behavior a solution.

Re: Developing for Android is like being a demonetized YouTuber

#50

Post by TeMPOraL »

iliketosleep wrote: post #27

In fairness, access to features such as call logs and clipboard are too easily abused. I think that most users downloading apps from the Play Store have the expectation that Google is taking care of their privacy. As the author mentioned, advanced users can still sideload any non-approved apps they want, and as advanced users they should understand any security implications. The point I do agree on is that the platfo…

Speaking of ridiculous, Android and banking, just yesterday I was browsing my transactions and wanted to send a screenshot of one to my wife. As it turns out, you cannot make screenshots of banking apps. Because "security".
Post reply on HN