📊 Note about coverage…

The coverage report excludes code not intended to be covered.

This avoids the “broken window” effect: whether coverage is at 43% or 56%, it’s perceived as equally low—so efforts to improve it are often dismissed. In contrast, high or near-100% coverage is seen as achievable and worth tracking.

Refer to the root project's build.gradle.kts for details.

Excluded elements include:

• Data models (no logic to test)
• Authentication (tedious to cover for now; may change later)
• Network status check (done for desktop, tedious for Android)
• Dependency injection (limited relevance despite some graph tests)
• Generated code that's untestable or irrelevant (that said, *Dao_Impl are retained)
• Root screens (difficult to test due to navigation, ViewModel, DI, etc.); testable parts are extracted for UI tests
• Compose UI previews
• Dummy screens using only Material components without logic
• Compose icons
• Resources

---

Taskfolio

Taskfolio is an Android task management app built using Google Tasks API. Developed to demonstrate my expertise in modern Android development, it highlights my skills in architecture, UI design with Jetpack Compose, OAuth authentication, and more—all packaged in a sleek, user-friendly interface.

I set out to revisit the classical TODO app, ‘local-first’ syncing with Google Tasks—aiming for an MVE in 2 weeks, focusing on the 80/20 rule to nail the essentials.

🎯 Project intentions

• Showcase my expertise in Android application development
• Demonstrate UI development using Jetpack Compose with Material Design 3.
• Include local-first capabilities for local data storage using Room.
• OAuth 2.0 authentication.
• Provide sync capabilities with Google Tasks for seamless task management.
• Illustrate my ability to set up CI/CD pipelines and publish apps to the Play Store.

❌ Out of scope

This project is not intended as a comprehensive task manager for public use. I do not aim to implement advanced features beyond what is supported by the Google Tasks REST API.

• no task list reordering
• no starred task
• no task priority
• only due date, no custom time support
• no task recurrence
• limited hierarchy (2 levels)

🚧 Known Limitations

• Authentication flow isn't 100% reliable yet (#34).
• Local-first support with Google Tasks sync is limited, in particular sorting & conflict management is barely implemented (#140).
• Task completion state toggle doesn't honor indentation properly (ongoing) (#175)
• No drag'n'drop to re-order tasks nor move them between lists (#133).
• Task deletion undo is not implemented (#149).
• Local action sync failure might not be synced again (#150).
• Setting due date is partially supported (#155).

🛠️ Tech stack

• Kotlin, Multiplatform (aka KMP) (currently Desktop & Android are supported)
  • iOS & Web are not planned any time soon (contribution are welcome 🤝)
• Kotlin coroutines
• Ktor client (+ Kotlinx serialization)
• Room for local persistance
• Koin for dependency injection
• Material Design 3 Components
• Jetpack Compose, Multiplatform (aka CMP)
• Kinda follows Google architecture guidelines
• Coil
• GitHub Actions for CI
  • build Android & Desktop apps
  • run tests
  • compute code coverage & check threshold
  • publish app on Play Store
  • publish companion website on Github pages

🗺️ Project breakdown

• :google
  • :oauth ■■■■■■■■■■ 100%
    • Google OAuth2 authentication with Kotlin & Ktor
    • KMP
  • :oauth-http ■■■■■■■■■■ 100%
    • OAuth2 HTTP redirection for desktop without deep links using Ktor server
    • KMP
  • :tasks ■■■■■■■■■■ 100%
    • Google Tasks REST API bindings for Kotlin using Ktor HTTP client
    • KMP
• :lucide-icons ■■■■■■■■■■ 100%
  • Lucide Icons for Compose
  • Made from Compose Icons (not using the direct Gradle dependency to tweak stroke width)
  • Only integrates what seem relevant for the app needs
  • KMP
• :tasks-core ■■■■■■■■□□ 80%
  • Taskfolio business logic
  • Local first with Room database, sync with Google Tasks
  • KMP
• :tasks-app-shared ■■■■■■■■□□ 80%
  • All screens & UI components integrating the :tasks-core business logic in Compose
  • KMP
• :tasks-app-desktop ■■■■■■■■■□ 90%
  • The Desktop application (thin layer fully reusing :tasks-app-shared)
• :tasks-app-android ■■■■■■■■□□ 80%
  • The Android application (thin layer fully reusing :tasks-app-shared)
• website/ ■■■■■■■■■■ 100%
  • The static site presenting the project
  • Made with Jekyll and served by Github pages

🧑‍💻 Local development

See details…

Decrypt *.gpg files needed for development, and copy decrypted versions in proper places.

PLAYSTORE_SECRET_PASSPHRASE=MY_SECRET ./_ci/decrypt_secrets.sh

Updating google-services.json

The production google-services.json file is ignored by SCM to avoid exposing API keys in public repository. To update it, download the new version, encrypt it using gpg --symmetric --cipher-algo AES256 google-services.json and store this in _ci/google-services.json.gpg. The decrypt_secrets.sh will take it into account.

Compose hot reload 🔥

See details…

It is possible to use Compose hot reload on desktop app by running the :tasks-app-desktop:runHot Gradle task.

You'll see a Compose icon near the top left corner of the window.

When clicking on it, it will open a new window with the hot reload status.

⚖️ License

The MIT License (MIT)

Copyright (c) 2024-2025 Olivier Patry

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.