Origin • Features • Project Info • Pages • Q&A
This android app is the final project of MOBILE PHONE PROGRAMMING course given by Prof.Wu at Tamkang University. We were given the task to make a survey app, which at the time our website was already online. We thought to ourselves why not make a android version of our surveying website, and so this was how this app was created.
- 100% Kotlin
- Make use of Kotlin's new features including: KTX library and Coroutines
- Used 33 Jetpack libraries such as: Navigation, ViewModel, Material Components...etc.
- Organize courses into tabs for a cleaner UI
- Able to send requests to our general education course recommendation system api server*, and refresh options based on the recieved reponse
- Target SDK Version: 30 (Android 11.0(R))
- Min SDK Version: 21
- Build Tools Version: 30.0.2
- Android Gradle Plugin Version: 3.6.4
- Gradle Version: 6.5
- Kotlin Version: 1.4.21
-
Dependencies
- appcompat: 1.0.0
- constraintlayout: 1.1.3
- converter-moshi: 2.9.0
- espresso-core: 2.9.0
- junit: 1.1.1
- kotlin-stdlib: 1.4.21
- legacy-support-v4: 1.0.0
- material: 1.0.0
- moshi-kotlin-codegen: 1.11.0
- moshi-kotlin: 1.11.0
- navigation-fragment-ktx: 2.3.2
- navigation-ui-ktx: 2.3.2
- okhttp: 3.12.1
- recyclerview-selection: 1.0.0
- retrofit: 2.9.0
- First Page
- Second Page
- Third Page
- Fourth Page
- Fifth Page
- Sixth Page
I've done lots of research and gone through lots of websites, so I thought I'd posted some here just for your convenience
- Why single Activity, multi Fragment architecture？
- Migrate to the Navigation component
- Single activity: Why, when, and how (Android Dev Summit '18)
- Reasons to use Android Single-Activity Architecture with Navigation Component Google keyword "single activity multiple fragments" for more, main reason being this architecture is what Google proposes.
- Why use Retrofit？
- Why use Moshi？