[blocke]

I use the Kindle app for Android because that is where the indie authors seem to be. I use the app in spite of itself. The Kindle app on Android has over the past few years been such a buggy piece of shit that I curse it's very existence. It alone has demonstrated that Amazon can't competently develop mobile apps worth a damn and made me laugh when I heard Amazon was making a phone.

Once a month Amazon seems to make a release that outright breaks a critical flow in the app. For the past couple weeks I've had to use the website to skim through books because every time the app tries to open the store view for a book the app instead opens Chrome with "about:blank" as the URL. /facepalm

I'll ignore the fact the tablet version gets a proper store interface (when it's not completely broken) but the cellphone version gets a regurgitated ancient web view that was last updated a half decade ago.

I can only conclude that Kindle isn't profitable for Amazon at all and they throw appropriate talent at it... that is none at all.

Does Apple give a rip about iBooks? Google doesn't seem to give a crap about getting indies on Google Play.

[fpgeek]

I think you have the causality backwards. It's not that Google doesn't care about getting indies on Google Play (though, to be fair, not enough to deal with the havoc their automatic discounting creates for indies, last I heard), it's that indies often don't really care about being anywhere but Amazon (largest market, extra perks for titles that are exclusive, less to manage and so on). For obvious reasons, this may not be a great long-run choice for them, but it can be very attractive in the short-run.

[rurounijones]

> Once a month Amazon seems to make a release that outright breaks a critical flow in the app. For the past couple weeks I've had to use the website to skim through books because every time the app tries to open the store view for a book the app instead opens Chrome with "about:blank" as the URL. /facepalm

Had same issue, reported it, was told to uninstall and reinstall, no joy. Upgraded to Android 5.1 which included a new webview component update, issue fixed.