One of the biggest issue of running Apps (open source or not) is the inclusion of the Play Store API in the app itself. These apps when not logged into the play store usually crash with NullPointerExceptions. Please... if you are an Android developer... expect your third-party services/APIs to be missing or to crash and handle that case... If you include the Map API or several other Google Services APIs in your app and the Play Store is missing or the user does not have a registered account... calls to those services will most likely result in NullPointerExceptions. Tell me to deal with it, don't crash.
Not the good ones. Normal operation isn't when you're dealing with a mobile device, there could be any number of reasons why your app can't reach a certain service delivered by some API so better to be prepared for that eventuality.
You have to balance the tradeoffs of bloated code and pointless error checking with adding features and improving the program. The more error checking code one writes the more one must maintain and the higher the potential for bugs.
That's an artifact of the chosen environment. Not checking for errors in that environment is a bug.
Besides that what do you do to handle the loss of something your app requires as a basic service? A nice error beats NullPointer but not by much.
And related to null-checking, I took the pervasive approach in one of my apps for fun. It's hilarious - almost 1/3 of my app is checking if something is null. Makes you wish for a switch to a language where nulls don't exist unless explicitly asked for.
Google In-App purchases are safe, so if that's how you monetize, I don't see why the app should be allowed to work anywhere else but in Google's environment.
It's different if the app is open source or you don't need to monetize (sadly, not everyone can afford that luxury), but even there it depends on how important those Play Store API features are to the functionality of the app.
Even if they're currently fully unmonetized, many such apps exist on the Play store because they can be updated at any time to include in app purchases, etc.
I just don't think that you can follow some rule dogmatically, because for some it might be worth the exposure, for some the extra costs might outweigh the benefits.
This is something that I would decide on a case by case basis.
Sure you can, if the rule is "don't write shitty software that crashes". In which scenario do you think users are more likely to buy: when an app crashes with no indication of what caused it, or if an app pops up a message along the lines of "we couldn't connect to Google Play; is it disabled for some reason?"
Developers would be able to see from the crash reports how many NPEs from missing Play Services they're getting and prioritise accordingly.
Are you sure about this? This may be unique to Touchwiz or something, but you can save a contact to either the device or to Google contacts.
I have no problems whatsoever storing contacts on my device...and my friend puts all his on his SIM card.
They have a NetworkLocation replacement which uses Apple's location services, and the dev is planning to add Mozilla Location services in the future. It also replaces Google Maps with OSM.
[1] http://forum.xda-developers.com/showthread.php?t=1715375
I really want to switchover to a proper CardDav/CalDav setup that actually supports "Tasks" in my calendar, exactly how Google doesn't and continually fails to.
BaiKal[1] is just this. It too is open-source, and it's a million times lighter. Literally. I've gone from 100% CPU use to complete idling. It is also self-contained via Sqlite, with no need for "heavy" things like MySQL backing.
The only bad thing is that it might be harder to get running on a shared host, due to its "web-app" part being hosted in a sub-directory of the actual application-structure.
I wish there were a trustworthy source of prebuilt pure AOSP ROMS, like the source images Google release. Compiling them is no small feat and I'm worried I'll brick my device.
With a stock AOSP ROM + Fastmail contacts & calendaring, I think I'll finally have the minimalist install I am looking for.
What's wrong with Cyanogenmod? They even provide a dead easy installer which unlocks the bootloader, changes the recovery and then flashes the ROM. And they support a good number of devices out there.
My only problem in the past was absolutely horrid syncing and GPS battery drain with Cyanogenmod. I keep going back to try, since first running it on my HTC G1 about 4 years ago. No other ROM gives me trouble, only Cyanogenmod. This is why I'm interested in a 'plain vanilla' as possible AOSP ROM. I'm back on stock 4.4 (rooted) and looking to move back to a non-gapps version soon.
[1]: https://github.com/WhisperSystems/TextSecure/issues/127
If you can suggest viable alternatives, I am certain that the team would love to drop Google from it.
[1]: http://download.osmand.net/releases/ [2]: https://code.google.com/p/osmand/
Many apps are open source (e.g., github, wordpress, coinbase, 2FA apps compatible with many services) and so are available through f-droid. Others, like TextSecure are really easy to build from source and install.
I have occasionally downloaded apps through one of the APK downloader services mentioned in the article comments -- I've had mixed luck. Some work flawlessly, others don't work at all without the google apps.
It would be awesome to see Mozilla's location service [0] integrated into Cyanogen to replace the google location services (which are of course disabled if you don't install google apps).
[0] https://location.services.mozilla.com/