How didaktikapp5/didaktikappdurango works
Main Components
• User Interface (UI) Layer: Represented by the multitude of Android Activities (e.g., MainActivity, LoginActivity, various game activities such as ArtopilActivity, BasilicaActivity, etc.). These activities form the interactive screens of the application.
• Game Module / Logic: Each mini-game (e.g., “Buscando a Mikeldi”, “Mercado de Durango”, “Preguntas de verdadero o falso”, “Sopa de letras” and “Puzzle”) should be shown as distinct submodules. They include game-specific logic and interactions.
• Media and Resource Layer: The app uses a well-populated ‘res’ directory with layouts, drawables, raw media files (e.g., mp3, mp4), and different language resource files, indicating support for internationalization.
• Data Layer: Includes the database module (found under the "db" package with ConexionDb.kt) which handles local storage or persistence of game scores, rankings, and possibly user settings.
Relationships and Interactions
• UI Layer interacts with the Game Module by capturing user input and directing navigation between activities.
• The Data Layer (local database) is accessed from various game activities for tasks such as saving user credentials (from LoginActivity) or storing scores for the Ranking module.
• Media and Resource Layer is consumed by UI elements to render the proper layouts, images, and audio-visual instructions during gameplay.
• Components (activities) will pull data from the DB and use resource files (layouts, strings, images) to render interactive screens.
• The Gradle/Build infrastructure supports the overall compilation and bundling of these components.
Architectural Patterns and Principles
• The project follows an Android architecture where Activities serve as controllers and directly manage the UI.
• Separation of concerns: Each activity is purpose-specific—handling login, main menu, specific mini-games, map interaction, and ranking.
• Resource-driven design: Emphasis on localization (with strings for different languages) and multimedia education through audio and video files.
• Modularity: Though not explicitly using advanced patterns like MVVM, the separation between UI (activities), game logic (each mini-game’s specific activity and potentially separate logic classes) and data (database connectivity) is clear.
Relevant Technologies and Frameworks
• Android SDK: Core framework for activities, UI elements, and overall mobile app behavior.
• Kotlin: Primary programming language, as suggested by the Kotlin files (.kt) and build.gradle.kts.
• Gradle: Build tool used to manage project dependencies and build configurations.
• Database technology (possibly SQLite via the provided ConexionDb.kt).
Elements
• From “User Input” to “LoginActivity” then branching to “Main Menu”.
• From “Main Menu” to various game activities.
• From game activities to the “Database Module” when saving/reading scores.
• User Interface components.
• Backend logic (game modules, database).
• Resources.
• Optionally, include a note that Gradle and build artifacts support the development/build life cycle.