неизбежный урон
09:40 | 15-08-2013 | Apple, Google, Hardware, Software | No Comments
опять, да, да, о фрагментации, — оттого что это не просто телефоны или планшеты, а самый натуральный бизнес.
вот один аспект, например:
Fragmentation continues to crop up on Android in weird ways for devs but now is going to the next level—affecting the ecosystem. Tomorrow Apple is no longer just about integrated hardware / software, it’s about an entire integrated ecosystem. The software is built in advance while hardware is designed and spec’ed, developers have your APIs and it all just works together in tandem. To some extent Google can do this with products it controls and distributes like Glass and Chromecast (via OTA updates), but fragmentation will start to hurt Android more and more in smartphone web services which it doesn’t develop.
а вот другой:
It’s not even funny how bad fragmentation will hurt Android and Google in location based sharing and payments apps, short range sharing, and the type of things developers build on top of iBeacon (e.g. payments). Fragmentation doesn’t matter as much when you are the only one person affected, people deal with it. But when your Android phone won’t communicate with others or at POS terminals (tablets / iPads) it will be tough to rationalize. Bluetooth LE in Android is happening now, but fragmentation is a deal killer for devs, and this ensures that state of the art apps around local discovery / wireless will rarely support Android[1]. It’s already happening — Tile has raised about $3M from 50K backers and there will be no Android support (these are tagging devices running Bluetooth LE that help you find lost keys etc).
-
пир духа, натурально:
For some reason fragmentation always elicits the “too many screen sizes” example—but issues such as those can be overcome with responsive design. The real trouble comes in different ways – e.g. a friend I know has been seeing a lifecycle bug crash the keyboards on ALL Samsung phones. It’s not an Android version issue, it crashes the app across revs; it’s something non-standard Samsung is doing to Android itself. These are the types of problems that slow down developers and cause them to reevaluate Android support next time.