Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Android Fundamentals I

Sponsored · Ship Features Fearlessly Turn features on and off without deploys. Used by thousands of Ruby developers.

Android Fundamentals I

Capacitacón Fundamentos Básicos de Android

Avatar for Luis Alonso Paulino Flores

Luis Alonso Paulino Flores

September 01, 2016
Tweet

More Decks by Luis Alonso Paulino Flores

Other Decks in Programming

Transcript

  1. Activities - Fragments Starting with HONEYCOMB, Activity implementations can make

    use of the Fragment class to better modularize their code, build more sophisticated user interfaces for larger screens, and help scale their application between small and large screens.
  2. Activities - Intent An Intent is a messaging object you

    can use to request an action from another app component.
  3. Activities - User Interface Components Common Layouts - LinearLayout -

    RelativeLayout - FrameLayout - WebView - CoordinatorLayout - ConstraintLayout Building Layouts using Adapter - ListView - GridView - RecyclerView Others - ScrollView - NestedScrollView
  4. Activities - Code Namings A subclass of Activity must be

    named like: [Name]Activity A subclass of Fragment must be named like: [Name]Fragment An xml that is the content view of Activity: activity_[name] An xml that is the content view of Fragment: fragment_[name]
  5. Activities - Best Practices • Be careful, Android isn’t Java,

    Java isn’t Android. • Respect android conventions. • Every attributes of an Android Component must have the letter “m” as a prefix. • Every static final constants must be in capital letter using “_” between words. • Be careful when you are going to use the Application Context or your Activity as a Context. • Google is your friend, read the docs! • Try to use fragments and use Activity as a container for them. Sometimes it’s difficult, but is the correct way. • Research, research, research and research :)