LesNotes

A local-first daily task management application built with Flutter for Windows and Android.

Features

Task Management

• Create, edit, and delete tasks with descriptions
• Mark tasks as complete/incomplete
• Schedule tasks for specific dates or keep in inbox
• Infinite scroll through future days
• Jump to specific date with calendar picker
• Bulk delete by section

Recurring Tasks

• Custom recurrence patterns (days of week)
• Automatic instance generation on-demand
• Independent completion per day

Automatic Task Rollover

• Incomplete tasks automatically roll over to today
• Occurs at app start or midnight transition
• Completed tasks stay on original date

Task Reminders

Android: System notifications (works when app closed, persists across reboots) Windows: In-app dialogs (only when app open)

Reminders only trigger for incomplete tasks and auto-cancel when completed or deleted.

Cloud Backup

Optional Supabase integration for manual save/restore of all local data.

Note: Supabase configuration is required to use cloud backup features. Without it, the app works fully offline with local storage only.

Theme Support

Light and dark modes with custom theme extensions.

Tech Stack

• Flutter 3.x / Dart 3.10+
• Riverpod 2.6 - State management with code generation
• Drift 2.22 - Type-safe SQLite ORM
• Supabase - Optional cloud backup
• flutter_local_notifications - Android notifications

Getting Started

Prerequisites

• Flutter SDK 3.x or higher
• Dart SDK 3.10 or higher
• For Windows: Visual Studio 2022 with C++ desktop development

Installation

1. Clone the repository:

git clone https://github.com/TomiNavel/LesNotes
cd lesnotes

2. Install dependencies:

flutter pub get

3. Generate code (Drift and Riverpod):

dart run build_runner build

4. (Optional) Configure Supabase for cloud backup:

   • Create a .env file in the project root
   • Add your Supabase credentials:

   SUPABASE_URL=your_supabase_url
   SUPABASE_ANON_KEY=your_anon_key
   

   • Import the database schema from Supabase-Schema.sql

5. Run the application:

flutter run -d windows  # For Windows
flutter run -d android  # For Android

Architecture

Clean Architecture with three layers:

• Domain: Business logic (pure Dart entities, repository interfaces, use cases)
• Data: Repository implementations, Drift/Supabase datasources, mappers
• Presentation: Riverpod providers, screens, widgets

Dependency rule: Presentation → Domain ← Data (Domain has zero external dependencies)

Key Design Decisions

Two-Table Database Model:

• tasks: Task templates with recurrence patterns
• task_instances: Concrete occurrences on specific dates
• UNIQUE(task_id, display_date) prevents duplicate instances

Lazy Instance Generation:

• Instances created on-demand when UI loads a date
• Recurring tasks generate instances based on weekday patterns
• Incomplete instances roll over to today during midnight migration

Building for Production

Android APK

Build release APK:

flutter build apk --release

Output: build/app/outputs/flutter-apk/app-release.apk

Windows Executable

Build release executable:

flutter build windows --release

Output: build/windows/x64/runner/Release/ (contains .exe and dependencies)

Development

Code Generation

After modifying Drift tables or Riverpod providers:

dart run build_runner build --delete-conflicting-outputs

Linting

flutter analyze

License

MIT License

Copyright (c) 2025 LesNotes

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.

Contributing

Contributions are welcome! Fork the repo, make your changes, and submit a Pull Request.