13 ms·
A former employee has discussed his experience at comixology when amazon made them migrate to amazon's backend in a series of tweets: thread 1: https://twitter.
by jccalhoun 4y ago
A former employee has discussed his experience at comixology when amazon made them migrate to amazon's backend in a series of tweets:
thread 1: https://twitter.com/CocktailsAndInk/status/1625233338741956642 https://twitter.com/CocktailsAndInk/status/16252333387419566...
thread 2: https://twitter.com/CocktailsAndInk/status/1625623760685436931 https://twitter.com/CocktailsAndInk/status/16256237606854369...
thread 3: https://twitter.com/CocktailsAndInk/status/1626342140807639040 https://twitter.com/CocktailsAndInk/status/16263421408076390...
- arka2147483647 4y agoFeels to me that to Amazon; Comics are subset, of the Books subset, of the Publishing subset, of the Store subset, of the Kindle subset, of whatever division subset of Amazon. That is, not important enough to customize anything. Sad. And yet, reading Comics is subtly, but importantly, different from reading a Book. I tried both Kindle and Comixology apps for reading a Comic a while back, and the Comixology App was a lot better. But it seems this does not register at Amazon.
- paxys 4y agoThis thread isn't about any backend migration, but the switch from Comixology's own app to Kindle. Apparently it was a disaster and people were unhappy, but there's no indication in these tweets as to why. Was the engineering not good enough? Bugs? Bad product management? Unrealistic deadlines? Were the acquired engineers just waiting for their lock up periods to expire so they could quit? Was Amazon management deliberately sabotaging them? I have seen all of these situations (and more) play out before, so it's never as simple as blaming a tech stack.