<h4 id="1-architecture-components"><strong>Architecture Components</strong></h4>
<p>Architecture is a steady plan which needs to be made before the development process starts. Architecture components keep application organized, ties all component together and provide a collection of libraries that help you to design robust, verifiable and maintainable applications. Android’s new architecture suggests some key principles to create an ideal application with security and avoid bloated classes that are difficult to maintain and test.</p>
<h4 id="2-building-blocks"><strong>Building Blocks</strong></h4>
<p>Basic examples for building blocks are Activity, View, Intents, Services, Fragments, Manifest File, AVD (Android Virtual Device). These blocks are the representation of rational application’s component architecture and also are marks of developer pain points.</p>
<p>The first set helps you with</p>
<ul>
<li>Automatically manage your activity and fragment lifecycles to avoid memory and resource leaks</li>
<li>Persist Java data objects to an SQLite database</li>
</ul>
<h4 id="3-components"><strong>Components:</strong></h4>
<h4 id="4-1-lifecycle-components"><strong>1. </strong><strong>Lifecycle Components</strong></h4>
<p>This component is used to add lifecycle awareness. Lifecycle components includes Lifecycle, LifecycleOwner and LifecycleObserver</p>
<h4 id="5-lifecycle"><strong>Lifecycle</strong></h4>
<p>So far lifecycle is an abstract class managed by the system itself. But in the current scenario, Lifecycle identify component’s state and behave &amp; end task accordingly at the appropriate time.</p>
<h4 id="6-lifecycleowner"><strong>LifecycleOwner</strong></h4>
<p>LifecycleOwner is an interface that can implement to get a lifecycle object from the getLifecycle() method. ProcessLifecycleOwner is useful when you want to manage the lifecycle of a whole process.</p>
<h4 id="7-lifecycleobserver"><strong>LifecycleObserver</strong></h4>
<p>LifecycleObserver observes LifecycleOwner components like Activities and Fragments. It receives LifecycleOwner.Event and react to them through the annotation methods.</p>
<p>By implementing this all together, we can create Lifecycle aware application.</p>
<ul>
<li>
<h4 id="8-implementing-lifecycle-observer"><b>Implementing Lifecycle observer</b></h4>
</li>
</ul>
<pre>public class TestObserver implements LifecycleObserver {

public MyObserver(Lifecycle lifecycle) {

// Starts lifecycle observation

lifecycle.addObserver(this);

...

}

// Annotated methods called when the associated lifecycle goes through these events

@OnLifecycleEvent(Lifecycle.Event.ON_RESUME)

public void onResume() {

}

@OnLifecycleEvent(Lifecycle.Event.ON_PAUSE)

public void onPause() {

}

}

</pre>
<p>Now we can use this observer in our app component, using following implementation TestObserver observer = new TestObserver(aLifecycleOwner.getLifecycle());</p>
<h4 id="9-2-livedata"><strong>2. LiveData</strong></h4>
<p>LiveData component is a data holder that contains a value that can be observed. With livedata whenever Activity or Fragment updated we will get notified so your UI will be always updated. It is a wrapper around your typical models that notify observers when something changes in that model. The Main advantage of livedata is no more memory leaks and NullPointerExceptions due to unexisting views.</p>
<ul>
<li>
<h4 id="10-create-livedata-objects"><b>Create LiveData objects</b></h4>
</li>
</ul>
<pre>public class MyViewModel extends ViewModel {
// Create a LiveData with a String
private MutableLiveData&lt;String&gt; mData;
public MutableLiveData&lt;String&gt; getData() {
if ( mData == null) {
mData = new MutableLiveData&lt;String&gt;();
}
return mData;
}
}
</pre>
<ul>
<li>
<h4 id="11-observe-livedata-objects"><strong>Observe LiveData objects</strong></h4>
</li>
</ul>
<pre>The following code illustrates how to observe LiveData object:
public class MyActivity extends AppCompatActivity {
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
MyViewModel model = ViewModelProviders.of(this).get(MyViewModel .class);
model.getData().observe(this, data -&gt; {
// update UI
});
}
}</pre>
<h4 id="12-3-view-model"><strong>3. View Model</strong></h4>
<p>ViewModel useful to provide and maintain data for your UI components (Activity or Fragment) in a lifecycle conscious way. It is able to survive through the configuration changes. So if you destroy activity or change your phone orientation you won’t lose ViewModel and data. Due to LiveData instance that is placed under ViewModel class, the input from our end isn’t required.</p>
<p>You don’t need to worry about UI lifecycle of holder data in UI. ViewModel will be build automatically through a factory and you don’t require to handle creating it and demolishing on your own.</p>
<ul>
<li>
<h4 id="13-implement-a-viewmodel"><strong>Implement a ViewModel</strong></h4>
</li>
</ul>
<pre>It’s illustrated by the following sample code:
public class MyViewModel extends ViewModel {
private MutableLiveData&lt;List&lt;Students&gt;&gt; students;
public LiveData&lt;List&lt;Students&gt;&gt; getStudents () {
if ( students == null) {
students = new MutableLiveData&lt;List&lt;Students&gt;&gt;();
loadStudents();
}
return students;
}
private void loadStudents () {
// Do an asynchronous operation to fetch students.
}
}</pre>
<p>You can access this list from an activity as follows:</p>
<pre>public class MyActivity extends AppCompatActivity {
public void onCreate(Bundle savedInstanceState) {
// Create a ViewModel the first time the system calls an activity's onCreate() method.
// Re-created activities receive the same MyViewModel instance created by the first activity.
MyViewModel model = ViewModelProviders.of(this).get(MyViewModel.class);
model.getStudents ().observe(this, students -&gt; {
// update UI
});
}
}</pre>
<h4 id="14-4-room"><strong>4. Room</strong></h4>
<p>Room is a database library &amp; a great alternative for SQLite database. To use SQLite database it is always necessary to write a lot of boilerplate. We can define database by adding annotations in Model class. The library helps to create a cache of app&#8217;s data on a device. It is much similar to OrmLite.</p>
<p>There are 3 major components in Room:</p>
<h4 id="15-a-database"><strong>a. Database</strong></h4>
<p>As your app is persisted, relational data and contains the database holder, It Serves as the chief access point for the underlying connection to the class that&#8217;s annotated with @Database should satisfy the following conditions:</p>
<p>Be an abstract class that extends RoomDatabase.</p>
<p>Include the list of entities connected with the database incorporating the annotation.</p>
<p>It returns the class that is annotated with @Dao and contains an abstract method that has 0 arguments.</p>
<p>While at the runtime, you can get an instance of database through calling Room.inMemoryDatabaseBuilder() or else Room.databaseBuilder().</p>
<h4 id="16-b-entity"><strong>b. Entity</strong></h4>
<p>Represents a table within the database.</p>
<h4 id="17-c-dao"><strong>c. DAO</strong></h4>
<p>Contains the methods used for accessing the database.</p>
<ul>
<li>
<h4 id="18-creating-entity"><strong>Creating entity</strong></h4>
</li>
</ul>
<pre>@Entity
public class User {
@PrimaryKey
private int uid;
@ColumnInfo(name = "first_name")
private String firstName;
@ColumnInfo(name = "last_name")
private String lastName;

// Getters and setters are ignored for brevity,
// but they're required for Room to work.
}</pre>
<ul>
<li>
<h4 id="19-create-database"><strong>Create database</strong></h4>
</li>
</ul>
<pre>@Database(entities = {User.class}, version = 1)
public abstract class AppDatabase extends RoomDatabase {
private static AppDatabase INSTANCE;
public static AppDatabase getDatabase(Context context) {
if (INSTANCE == null) {
INSTANCE = Room.databaseBuilder(context.getApplicationContext(), AppDatabase.class, "my_db").build();
}
return INSTANCE;
}
}</pre>
<p>This class is used to create the database and get an instance of it. We create the database using following code.</p>
<p>Room.databaseBuilder(context.getApplicationContext(), AppDatabase.class, &#8220;my_db&#8221;).build();</p>
<ul>
<li>
<h4 id="20-create-the-data-access-object"><strong>Create the Data Access Object</strong></h4>
</li>
</ul>
<p>Annotate the class with the @Dao annotation. A class implementation will then be generated by Room that implements the methods defined in the interface (very similar to how Retrofit works).</p>
<pre>@Dao
public interface UserDao {
@Query("SELECT * FROM user")
List&lt;User&gt; getAll();
@Query("SELECT * FROM user WHERE uid IN (:userIds)")
List&lt;User&gt; loadAllByIds(int[] userIds);

@Query("SELECT * FROM user WHERE first_name LIKE :first AND "
+ "last_name LIKE :last LIMIT 1")
User findByName(String first, String last);

@Insert
void insertAll(User... users);

@Delete
void delete(User user);
}</pre>
<h4 id="21-conclusion"><strong>Conclusion</strong></h4>
<p><span style="font-weight: 400;">This article gives you a basic knowledge of android architecture components. We have tried to include all topics related to newly proposed android architecture which solve all relevant issues which are faced by the developer while application development. Still, if you find any issues, consider <a href="http://www.elsner.com/hire-android-developer/"><strong>Hire Android Developer of Elsner Technology</strong></a>.</span></p>
<pre></pre>
<p>&nbsp;</p>


Do you want more traffic?

Digital Transformation begins here!

You may also like

Technology Moves
Fast, So Do We

Share this topic on

Do you want more traffic?

Digital Transformation begins here!

You may also like

Technology Moves Fast, So Do We

Technology Moves
Fast, So Do We