How inu-appcenter/android-study-17th works
This project is an Android study repository for the 17th batch of the 앱센터 안드로이드 스터디. It’s a multi-member repository that contains several independent Android application projects—each belonging to a different team member (for example, EUNU and SEUNGJUN). The members’ directories hold practice projects (like Practice1-1, Practice1-3, and MyApplication3) that follow the standard Android project structure (using Gradle with Kotlin DSL, the familiar “app” module layout with src/main, src/test, and src/androidTest, etc.).
Main Components
• Repository Level – A top-level “앱센터 안드로이드 스터디 17기” node.
• Members Directory – Branch out to the “members” folder that further splits into individual member folders (e.g., EUNU, SEUNGJUN).
• Individual Android Projects – Within each member’s folder, highlight each individual Android project (e.g., under EUNU, include Practice1-1 and Practice1-3; under SEUNGJUN, include MyApplication3).
• Android Application Structure – For each project, show its internal modular structure:
• The “app” module which contains the primary application code.
• Source sets (src/main, src/test, and src/androidTest) detailing:
▪ Main code: AndroidManifest.xml, MainActivity.kt, and UI/theme components showing the UI layer.
▪ Test layers: both local unit tests and instrumentation tests.
• Gradle configuration files (build.gradle.kts, settings.gradle.kts, gradle.properties) and the Gradle Wrapper. These represent the build and dependency management aspect.
• Additional Files – Mention support files like .gitignore, .idea settings (IDE configuration), and other documentation files (like 깃허브기본사용법.md).
Relationships and Interactions
• Repository to Member Projects: Show that the top-level repository “앱센터 안드로이드 스터디 17기” encompasses a “members” folder. Each member’s folder acts as a separate area where independent Android projects are maintained.
• Within each Android Project: The “app” module is the center where application code, resources, and tests interact.
• The src/main directory is the core Android application containing activities (like MainActivity.kt) and UI elements.
• The src/test and src/androidTest directories capture the testing layers – the unit tests and instrumentation tests respectively.
Architectural Patterns and Design Principles
• Modularization by Member: While not a microservices architecture, the repository is organized into independent modules / projects per team member. This separation supports parallel development and isolated build processes.
• Testing Strategy: Emphasize the division between unit tests and instrumentation tests, which indicates a commitment to ensuring code quality in different environments.
Relevant Technologies, Frameworks, and Tools
• Android SDK – All projects target Android as indicated by the presence of AndroidManifest.xml, Android test directories, and UI components.
• Kotlin Programming Language – Evident from MainActivity.kt and usage of Kotlin DSL for Gradle scripts.
• Gradle – The build automation tool is central to project configuration (build.gradle.kts, gradlew, gradle wrapper files).
• Android Studio – Suggested presence of the .idea directory, reminding that developers use Android Studio IDE for development.
• Git – The use of .gitignore and commit/issue conventions from the README confirm version control best practices.
• “Repository – 앱센터 안드로이드 스터디 17기”
• “Members” folder with branches to “EUNU” and “SEUNGJUN”
• For each member, list the project names (Practice1-1, Practice1-3, MyApplication3)
• Within each app module, label “src/main” (including AndroidManifest.xml and MainActivity.kt), “src/test”, “src/androidTest”, “res” (resources), and Gradle configuration files.
• How the build system (Gradle) drives the project build.
• How source code interacts with resources and tests.