#UDACITY FEED READER TESTING HOW TO#
#UDACITY FEED READER TESTING UPDATE#
#UDACITY FEED READER TESTING ANDROID#

#UDACITY FEED READER TESTING ANDROID#

In more detail, Unit 1 acts as a crash course in Android design fundamentals looking at it from 20,000 feet and explaining that Material Design borrows and transfers ideas from the physical and print design world to the virtual one of building UIs.It then shifts its focus onto building those UIs which run on all kind of Android devices, from smartphones to wearables, adapting to the requirements of each distinct environment.

#UDACITY FEED READER TESTING UPDATE#

In this project, you will update the look and feel of an app to meet Material Design specifications.

#UDACITY FEED READER TESTING HOW TO#

Understand how to refine and test your designs on for use on multiple form factors. Understand the use of motion in apps, how to use transitions to change app states and properly choreograph the motion in an app. Understand and apply branding guidelines - including key lines, metrics, fonts, typographic scale, color palette and themes/styles. Understand how to use surfaces to structure the hierarchy and interaction of elements in an app. Understand and apply the fundamentals of Android design to your app, and experiment with app structures, common navigation patterns and themes. The class is organized in 5 distinct units including the end project: Then again, while 'Material Design' might be the recommended way, it does not enforce strict or uncrossable boundaries, as any app is free to deviate when necessary, typically when wanting to infuse the brand's signature and that feeling of uniqueness. That's why the 'Hamburger' icon, the rounded Contacts of Gmail, the flipping of pages by swiping left and right are patterns so frequently met across all Android applications. In addition to standardizing aesthetics with color palettes, typography, imagery and so on, Material Design also sets up a common ground for all Android apps to be built upon so that end users are able to transfer their experience of using one app to the using of another. Thankfully, as there's patterns for everything, so there are for designing UIs and on the Android platform they're collectively known as 'Material Design'. This makes sense since the user's first encounter is with the 'get to know' phase that depends on the aesthetic, layout, setup and organization part of the application, taking place much earlier than the functionality assessment phase. This has to change since design plays a big role in what breaks or makes success and, with so much competition in the Android store, producing just a functional application is not enough. So 'design second' doesn't pertain just to Android applications but crosses boundaries and I guess that's something prevalent to most backend-oriented developers out there. I always aim for functionality first and design second, something clearly evident in my Nanodegree projects submitted thus far which satisfied just the UI essentials but also in my other unrelated-to Android-work, such as Ultimate Extract and Recover, a Win32 application and Smart Device Seeker, a Website about smart devices.

Udacity feed reader testing