Different opinions are what drive conversation, so, I won't ignore your concerns here. Really don't want to see anyone get down voted here for having an opinion. Thank you in advance for doing an android app in the first place. However, simply redoing the app in a generic style adhering to these guidelines would be a drastic improvement. This is just a 1 minute recommendation and of course open to argument. Use the FAB for "search" since it is the most frequent user action. However, there are enough patterns to provide a superior experience to the jumbled mess of an application that it is right now. Yes, it is unfortunate they are guidelines and not SDK. The simplest approach you could take would be to copy and implement the design patterns presented in Google's material design guidelines. It's an unpleasant part of developing for Android that Google does very little to address. It is true that as an android dev one has to implement many things themselves. Hi Kyle, thank you for participating in this conversation. I know it's tough as a user to see one so far ahead of the other but I hope the above information puts some of it into perspective. I guess that's a long answer but really, it's simply going to take some time for our Android developers to catch up. I'm sure it's both overwhelming and exhilarating for them. I don't envy our Android developers because they have none of that to work with. I work on our iOS application and it's incredible the amount of stuff you can do in a short period of time because groundwork has been laid for years. Combine this with UI changes and stuff that mean we have to rewrite existing things to match up with that and it just becomes very overwhelming sometimes. The Android team, well, they have to implement everything themselves and it's simply going to take time. Then it becomes an interface deal in many cases which may not be easy at all but at least some of the work was done. That means when our Mac team implements something super great our iOS team gets some of that grunt work for free. Our iOS application also shares a great deal of underpinnings with Mac. Our iOS application has been in development for something like 4 years now, and several years before that as a previous incarnation (version 4 was a complete rewrite). With respect to our Android developers they have an uphill climb to catch up to iOS. I showed your comment to our Android developers so they've seen what you're requesting :) I can't help but be inspired by a group of people who fight tooth and nail to catch up to a product that's much older (our iOS application). We have some super smart people working on it and they're very passionate about what they do. It's just a matter of time and our Android application will be right up there with our iOS application. Personally, I feel they've made great strides given the time they've had. We really do want everyone to love our Android application. It might offer some perspective, not that it's an excuse but it explains things a bit more and might just help in understanding. I would encourage you to take a look at my other comment in this particular tree of comments about Android. There's some work being done to modernize the interface and some of your list will be tackled by that. I think you'll be happy with the progress when you see the next updates. Sorry to hear that you're unhappy with it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |