![]() * The adle is not fully complete yet, we need to implement build variants and a few other things and get the integration tests working. Why not start with v15? If that becomes the case I’ll probably remove AppCompat and use the built in Android Action Bar. ![]() Plus, if you did support v10+ (or whatever) you’d be losing that market and have a ton of tech debt to manage from that point forward. The maintenance and support costs outweigh the market position you might gain. Sure, you may miss out on ~ 30% of the available market (as of Nov 2013), but developing and supporting those old devices (pre v15) for a NEW project just doesn’t make sense most of the time. The reason for this is because if you’re going to create a new project you’re probably going to target v15 or above anyway. I also spoke with Jake and a few other people over twitter recently about how it might be a good idea to change the minSdkVersion to 15 when this is released. You should be able to open the generated project in Android Studio and start coding away. If you go to you can generate a project that has support for all of the items above. I’m happy to say we’re at an alpha stage with this.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |