Android and openness is something we talk about all the time, but the recent developments in the industry point towards inherent flaws with this very premise. Be it from bloggers, political institutions or corporations, Android is seemingly not open enough. The “War on Openness” is ironically becoming an open war, where many players are increasing their stakes and scope to try and land a bigger hold - or at the very least, restrict Google’s - on what is the world’s...
Dos and Don’ts of Android Design
As long as you’re coming from some type of programming background, the unseen part of app programming will not be very hard. Java is a pretty forgiving language and a good IDE makes all the difference. But that doesn’t mean the User Interface is going to be easy. A fair amount of upfront planning for the user experience will save you time tenfold when it comes to writing the code. XDA Forum Member Leafhill wrote a thoughtful post covering common mistakes in Android UI design. But along the way, he also cites best practices as well. The post will go a long way in planning how you present your app to users in an intuitive way.
High on the list of foul dev behavior is to completely re-skin the entire app, or to force it to look like another operating system. We agree that this ends up being disorienting at first glance, and frustrating over the long term as a user repeatedly searches for the functionality in a different place than expected. I also agree on the use of the ActionBar. The Android developer’s guide draws it out very clearly; you should include the ActionBar, except when a media rich experience (i.e. full screen video) is necessary. The ActionBar icons and menus should also adhere to common practice.
There are two things he mentions that I could go either way on. I think adding background graphic accents can be a way of branding your app if done tastefully. But Leafhill asserts that these are outside of the Android tradition. He also has a good point about quick action menus that hide the original content when shown. The example is swiping a Tweet in the Twitter app to get at the share/trash/favorite/retweet commands. The swipe hides the tweet being operated upon, which probably does result in the wrong one being retweeted from time to time. I use Reddit News, which has the same functionality for up and down voting, loading comments, etc. I don’t find it to be a problem, but knowing that the menu is even there would be tough for those new to the app.
The final don’t is to style apps as if they were a website. This tops my list of Android pet peeves, and that’s what the banner image is all about.
Head over to the original article, which includes a slew of screenshots and references for each of the design issues discussed.[via Reddit]
Want something on the XDA Portal? Send us a tip!
Smartphone cameras have advanced so tremendously over the past few years that they have almost completely replaced point and shoot digital cameras for the most of us. Furthermore, since our smartphones are always with us, the majority of us end up taking tons of photos throughout the lifespan of our devices. But what happens to all the old photos you take? Do you store them on an external hard-drive or keep them backed up to an online cloud service like Flickr? Let us know what your favorite way of storing old photos is and why.
Before the release of Android 5.0 Lollipop, the Holo Design guidelines served as the official reference for Android design, right from IceCream Sandwich to KitKat. However, updates to the guidelines were few and far between, leading to a lack of synchronization between Android design and current UI/UX trends. Google seems to have learned from their mistake the last time around, and earlier this week, a significant update was released for the Material Design guidelines, marking the second revision in less...