Skip to content
Samuel Charry Tobar edited this page Aug 13, 2026 · 1 revision

Subteams

The team was divided into two subgroups based on the technologies assigned for the reports. Each subgroup was responsible for selecting and analyzing an open-source mobile application relevant to its respective technology.

Technology Members
Flutter Isabella Mantilla, Samuel Charry Tobar, Juanes Triviño
Kotlin Mateo Cante Garzón, Santiago Quiroz Pintor, Juan Sebastian Rodriguez Torres

Selected Applications

Each subgroup selected an open-source mobile application to analyze as part of the app report.

Subgroup Application
Flutter Cake Wallet
Kotlin DuckDuckGo

DuckDuckGo (Selected by the Kotlin team)

DuckDuckGo Android is the official browser and privacy-focused search app from DuckDuckGo, released as a complete, production-ready open-source project used by millions of people. The project follows a single-activity architecture, leans on Kotlin Coroutines for asynchronous work, and applies a clear Model-View-Intent (MVI) pattern for UI state management, making it a solid, contemporary codebase that follows current best practices. Unlike Flutter Catalog which is an educational showcase of widgets this repository is the actual source code of a commercial private-browsing app, which makes it valuable as a reference for modern, real-world Android architecture rather than as a teaching catalog of UI components.

Key Features:

Single-activity architecture with centralized navigation MVI (Model-View-Intent) pattern for UI state management Extensive use of Kotlin Coroutines for asynchronous operations Dependency injection via Dagger + Anvil Apache 2.0 license, actively maintained by the DuckDuckGo team GitHub Thousands of forks and stars, with issues and pull requests updated on an ongoing basis GitHub Modular, feature-based structure (privacy protections, history, settings, sync, etc.)

Use Cases:

Reference for MVI/Coroutines architecture in a production-grade Android app Source of modularization and DI (Dagger/Anvil) patterns for your own projects Case study of "privacy by design" implemented at scale Foundation for academic repository analysis (metrics, structure, code quality)

Clone this wiki locally