3 ms·
I was able to successfully train a designer to use the Android SDK's tools when appropriate, and check in graphical assets. In preparatory meetings I insisted t
by Zigurd 13y ago
I was able to successfully train a designer to use the Android SDK's tools when appropriate, and check in graphical assets. In preparatory meetings I insisted the designer be in the room with the coders and product managers as I explained how Android is different. I taught them all how to use conditional layouts and how to test apps for good practices by changing font sizes to see if they really are geometry-independent. Once they saw how easy it is to make other developers' work look less than competent, I could see the switch in their minds flip: They were not doing to be tripped up by users who change font size.
This client was the typical kind of client who could easily have fallen into a "portitis" pattern of not designing for the capabilities of Android's layout system. If all parts of the system - product managers, coders, and designers, not have bought into thinking about their part of the project differently from an iOS implementation, the designers would have had no inputs from those other parts of the team re how they were modifying their approach for an Android version of their product.
Android has a richer system for adapting code modules to different layouts, and therefore a more sophisticated UX for tablets. It's a pity than many Android apps are low-bidder porting jobs that plaster right over that.
- whytaka 13y agoAs an app designer, I wouldn't mind a lesson myself!
- doctorcroc 13y agoLikewise. Zigurd, would you mind writing up a short lesson?
- Zigurd 13y agoSee above: https://news.ycombinator.com/item?id=7457817 https://news.ycombinator.com/item?id=7457817
- LordIllidan 13y agoI'd be interested in reading more about this - I'd love to show it to some designers I work with. At the moment, I'm struggling to get the designers to acknowledge that Android and iOS need to be designed seperately. iOS designs can look pixel-perfect due to having only 2 resolutions to care about (ok, iPhone 5+ have taller screens, but same width) Android is a whole different story.
- youngtaff 13y agoSlide 86 on of this talk by Stephanie Rieger will help http://www.slideshare.net/yiibu/designing-for-diversity-how-to-stop-worrying-and-embrace-the-android-revolution http://www.slideshare.net/yiibu/designing-for-diversity-how-... (whole slide deck is worth looking at)
- Zigurd 13y agoThis is how I introduce Android to teams that are making their first serious non-game app: 1. How to scale the app across all screen geometries: a. Let Android choose the layout from among the alternatives you create for different geometries b. This means different numbers of Fragment objects can be displayed c. This means different functionality can be available d. This means you have to organize functionality in a hierarchy (for the smallest screens) that can be unfolded and flattened (for the biggest screens) 2. Then I get into Activity and how the code that used to be in activities should be organized into Fragment subclasses, and about top-level layouts. 3. Then I get into Relative Layout and how to make your layouts "stretchy" enough that you don't have to specify a different layout for every combination of size, density, orientation, and text size. 4. Now that the coders and designers understand how they fit together in making a UX that "folds up" and "unfolds" I teach the designers how to check in to the client's repos, and how to edit layouts in Eclipse, so they can be responsible for their own work getting into the project and build and run the app to see how their layouts work. This is still a vast simplification, leaving out things like Android remote methods and high-level (Intent) IPC and how hat affects UX, and numerous other areas where Android is substantively different from iOS's app environment.