Android Sunflower

print
https://github.com/googlesamples/android-sunflower

https://developer.android.com/jetpack/docs/getting-started#take_advantage_of_jetpack

A gardening app illustrating Android development best practices with Android Jetpack.

Android Sunflower is currently released as an alpha and is under heavy development. To view the latest changes, please visit the Releases page. Note that some changes (such as database schema modifications) are not backwards compatible during this alpha period and may cause the app to crash. In this case, please uninstall and re-install the app.

Introduction

Android Jetpack is a set of components, tools and guidance to make great Android apps. They bring together the existing Support Library and Architecture Components and arranges them into four categories:

Android Jetpack

Android Sunflower demonstrates utilizing these components to create a simple gardening app.

Getting Started

This project uses the Gradle build system. To build this project, use the gradlew build command or use “Import Project” in Android Studio.

There are two Gradle tasks for testing the project:

  • connectedAndroidTest – for running Espresso on a connected device
  • test – for running unit tests

Screenshots

List of plants Plant details My Garden

Libraries Used

  • Foundation – Components for core system capabilities, Kotlin extensions and support for multidex and automated testing.
    • AppCompat – Degrade gracefully on older versions of Android.
    • Android KTX – Write more concise, idiomatic Kotlin code.
    • Test – An Android testing framework for unit and runtime UI tests.
  • Architecture – A collection of libraries that help you design robust, testable, and maintainable apps. Start with classes for managing your UI component lifecycle and handling data persistence.
    • Data Binding – Declaratively bind observable data to UI elements.
    • Lifecycles – Create a UI that automatically responds to lifecycle events.
    • LiveData – Build data objects that notify views when the underlying database changes.
    • Navigation – Handle everything needed for in-app navigation.
    • Room – Access your app’s SQLite database with in-app objects and compile-time checks.
    • ViewModel – Store UI-related data that isn’t destroyed on app rotations. Easily schedule asynchronous tasks for optimal execution.
    • WorkManager – Manage your Android background jobs.
  • UI – Details on why and how to use UI Components in your apps – together or separate
  • Third party
    • Glide for image loading

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.