http://developerstudyjams.com/ Week 7 - Retrospectively looking at Udacity Lesson 5 Rich & Responsive Layouts Google Developers Study Jams is a free series of global, community-run, in-person study groups. The first Study Jams series is presented in partnership with Udacity and will follow their Android Fundamentals curriculum. Google Developer Group facilitators certified in the course will lead the Study Jams that meet once weekly for 8 - 9 weeks. Promote using hashtag #devstudyjam

1. Android Manchester
Week 7 - Rich & Responsive Layouts

2. Overview
● Retro
○ Lesson 5 rich & responsive layouts
● Looking Forward
○ Lesson 6 services & notifications
● Stickers
● Next Tues is the last retro
● Next Tues 7-8pm SpacePortX

3. Energizer
Stand up and introduce yourself to
somebody around you, you don’t
know

4. Prime Directive
‘Regardless of where we are up to, we
understand and truly believe that
everyone did the best job he or she
could, given his or her skills and
abilities, the personal time available,
and the situation at hand.’

5. Difficulty Check
● Who completed the class?
● How long did it take?
● Hands up 1-10 difficulty of the weeks lesson
● Any specific areas of the lesson that require
particular focus?

6. Retro lesson 4 rich & responsive layouts
What we learnt last week
● Design principles
● Views & ViewGroups
● ViewHolder pattern
● Optimising layouts with hierarchy viewer
● Resource folders with buckets & qualifiers
● Fragments
● Custom Views

7. Design Principles
● Enchant me
● Simplify my life
● Make me amazing
http://developer.android.com/design/get-started/creative-vision.html
● 30 seconds to win people over
● Suprise & delight
● Subtle animations
● Contribute to a feeling of power
and effortlessness
● Touch & interact with objects
directly

8. Wireframes

9. Visual Mocks

10. Views & ViewGroups
● Views are just rectangles on the screen
● Manages drawing & event handling
● TextFields
● Buttons
● Spinners
● Progress bars
http://developer.android.com/design/building-blocks/index.html

11. ViewGroup
● Container for children views
● ViewGroup is a View

12. Gravity
● android:layout_ - parent inherits this attribute

13. Padding & Margin
● android:layout_ - parent inherits this attribute

14. Implementing list item

15. Implementing list item
● Protip - use tools:src / tools:text
● Preview in design pane

16. layout_weight
● Use weight to absorb any extra space
● Prefer to use ratios of 100
● android:layout_width=”0dip”
● android:layout_weight=”33”

17. Binding data to views
● newView
● bindView
● Remember to remove hardcoded values
(or did you use android:tools)

18. Adapter view types
● getViewTypeCount
● getItemViewType(position)

19. ViewHolder pattern
● findViewById() is a heavy call that does view hierarchy
traversal
● Remove unnecessary calls to findViewById()
● stored in the “tag” field of the view, setTag(Object) getTag()

20. Hierarchy Viewer
From a terminal, launch hierarchyviewer from the <sdk>/tools/directory.
http://developer.android.com/tools/debugging/debugging-ui.html

21. Resource buckets

22. Resource folders

23. Resource drawables
http://developer.android.com/guide/practices/screens_support.html#dips-pels

24. Master Detail Flow

25. Fragment separation

26. Fragment design patterns

27. Headless Fragments
● setRetainInstance(true);
● Lives separate from the Activity
● Doesn’t create a view
● Doesn’t need to be destroyed & recreated
● Lifecycle is slightly different
● Great for networking
● Holding cache data

28. Visual Mocks

29. Redlines

30. Developer Options
Show layout bounds

31. Custom views
● Class extends View or SurfaceView (Video
+Games)
● onMeasure and onDraw usually
overridden
● Referred to in Layout file as:

32. What went well

33. What went well
● Wireframing first always give me a better insight into
what layouts to use
● Understanding navigation should always be done by an
Activity
● Headless fragments are a powerful feature
● Fragments and rotation
● Themes & Styles
● Accessibility Developer Checklist is great http:
//developer.android.
com/guide/topics/ui/accessibility/checklist.html

34. What didn’t go so well

35. What didn’t go so well
● android:gravity vs android:layout_gravity is so
confusing
● ActionBar
● Flag to remember if you’re in a 2-pane layout or
single-pane
● User icon naming convention “ic_”
● Lesson has a lot of stuff to cover
● having v21 & v14 styles is a lot of overhead

36. Q&A
Free money: http://goo.gl/JHulAu

37. Next Week - Android
Jam
Services & Notifications

38. Next Lesson - Services & Notifications
Learning Objectives:
- Background work & Services
- Efficient data transferring
- Sync Adapters
- Notifications
- Final Project

39. See you next week..
- Time: Tuesday 7pm
- Place: SpacePort
- Things needed: You + Questions +
Feedback
- Can contact us if issues:
@blundell_apps / @android_mcr

40. Go forth and discuss