3 ms·
Certainly a sensible decision for their usage, but it's worth noting that pretty much all the reasoning (apart from the fact nobody on Android actually download
by leoedin 14y ago
Certainly a sensible decision for their usage, but it's worth noting that pretty much all the reasoning (apart from the fact nobody on Android actually downloads the thing) is only an issue because they're moving from the iPad to Android.
None of the technical reasons given are actual issues with Android, they're just differences between iOS and Android. If you published a magazine solely on Android and tried to move it across to iOS you'd have the same issues (unless you found a functional platform-agnostic media store, which may or may not exist).
They are of course completely justified to stop producing an android version. Not many people used it, and I don't doubt that there's a lot of work converting between the two. Why is there a lot of work? Because the starting point is an iOS specific magazine design, not because Android is inherently limited.
- easytiger 14y ago> they're just differences between iOS and Android. Lots of them (the main ones) are issues with the prop product they use for targeting android
- pbhjpbhj 14y agoIt's the whole "optimised for IE5" thing all over again. Once you've got in the boat of single platform optimisation (using Apple Computers store for video and music integration in this case) then moving to something that is platform agnostic is hard. It's an interesting case study though, that it's costing they're losing money (I think that's what they're saying) by creating for the diversity of the Android platform. Would be nice to see the figures.
- Tichy 14y agoI think the maker of the software they use to product their magazine should solve that for them eventually.