How tiesol/proyectomoviles works
Project type and purpose
• Both ChambaPofabo and FixealoPofabo are Android mobile applications built with Kotlin. They follow a single-activity/MVVM pattern, consume a remote RESTful API, and present lists of categories, workers, appointments, chats, reviews, etc.
• The README simply labels this “proyectomoviles,” indicating a mobile-client portfolio rather than a backend or multi-service system.
File structure
• Top level: two sibling projects, each with
• an app module containing Android source, resources, tests, and Gradle config
• standard Gradle wrappers and settings files.
• Under app/src/main/java/com/ami/...:
• api: Retrofit interfaces (e.g. AppointmentApi, ChatApi)
• model: data classes for requests/responses
• repository: high-level data access abstractions
• retrofit: a RetrofitRepository factory for HTTP client setup
• ui: MainActivity, fragments, adapters, and navigation
• viewmodel: ViewModel classes exposing LiveData to UI
• Res: layouts, drawables, navigation graph, themes; no local DB layer (no Room).
• Patterns: MVVM + Repository + Retrofit network layer + Jetpack Navigation.
Detail and essential elements
• Retrofit API interface is represented or grouped under the Network layer.
• Single-activity coordinating all fragments via the Navigation Component.