4 ms·
You've hit the nail on the head. It's not the system engineer's job to develop a useful application framework for common use cases any more than it is a Linux k
by lern_too_spel 11y ago
You've hit the nail on the head. It's not the system engineer's job to develop a useful application framework for common use cases any more than it is a Linux kernel developer's job to do so. Still, it has to be somebody's job, and it's clear that it isn't anybody's job on the Android team. For example, there's a hacky HTTP client library built by the Google Play Android client team (http://developer.android.com/training/volley/index.html http://developer.android.com/training/volley/index.html) that is promoted for general use for some silly reason, and to use it, you're supposed to copy the library's source code into your project. Pure amateur hour. There should be a team within Android building well-thought-out, properly versioned, and sanely distributed libraries to simplify Android application development. There should be, but there isn't.
- izacus 11y agoYou mean like the sets of support libraries which make multi-versioned Android development significantly easier and less time consuming? I don't get the first-party library cargo cult that has developed on Android. What's wrong having the community develop libraries like on any other platform? There's a huge set of very good quality 3rd party Android libraries and even a great new language (Kotlin). As a dev I'd be rather that Google focuses on developing quality core blocks which cannot be fixed by community. Sadly it seems that Google developers simply do not know how to build good APIs, even new ones like MediaCodec, BLE APIs, updated storage APIs and permissions are an utter hard to use mess.
- spbaar 11y agoThere is no excuse for how hard the permissions API is to use. Why can we not know if the user has "never show again " checked directly? It literally looks like the API and ui came from different proposals
- newjersey 11y agoBecause you don't need to know. Permissions are sacred. If you don't have the permission, consider the capabilities aren't there and move on. How would you feel if Facebook or Instagram app refused to start if you didn't give it camera permission? Maybe I don't have a working camera in my Nexus 6.
- curt15 11y agoThe only real recourse against combat adversarial developers is to either trash the defective product in reviews or penalize the developers through other means. Holding functionality hostage in order to gain permissions should be instant grounds for rejection and/or further sanctions.
- christop 11y agoUnfortunately, this is what Google's own app for the upcoming Google I/O conference does if you deny it access to your contacts at startup. If you grant the permission only to deny it later, the app won't start again until you grant the permission again. https://play.google.com/store/apps/details?id=com.google.samples.apps.iosched https://play.google.com/store/apps/details?id=com.google.sam...
- newjersey 11y agoThat sounds horrible. I can't see a reason why they'd do that. Can you think of anything why this behavior happens?
- st3v3r 11y ago"You mean like the sets of support libraries which make multi-versioned Android development significantly easier and less time consuming?" You mean the ones that seem to change between Android versions, and get weird bugs between versions? "I don't get the first-party library cargo cult that has developed on Android. What's wrong having the community develop libraries like on any other platform? There's a huge set of very good quality 3rd party Android libraries and even a great new language (Kotlin)." Because those can't be counted on not to break between versions of Android.
- agildehaus 11y agoAndroid 4.4 and later uses the core of OkHttp underneath HttpUrlConnection, which is the library you should be using. If you want fancier features, or don't like using AsyncTask everywhere, just use the full OkHttp from Square and you'll get those. Volley is just a small abstraction atop HttpUrlConnection, so I'm not sure why you consider it so hacky. It also is available on JCenter, so just compile it into your project using Gradle: "com.android.volley:volley:1.0.0". You're entirely wrong about having to copy the source into your project.
- anonymousab 11y agoIt gets even worse when you want to download files and run into the sordid mountain of bugs that is the DownloadManager library.