bkdesignhub/lifeflow

Purpose and Entry Points

LifeFlow is a Laravel 11/PHP 8.2 personal productivity PWA combining task planning, notes, money tracking, reminders, dashboard summaries, and a future-facing assistant. HTTP traffic enters Laravel through public/index.php, is mapped in routes/web.php, and is served by feature controllers under app/Http/Controllers. CLI scheduling/operations enter through artisan and routes/console.php.

Application Shell and Access Control

The application uses Laravel’s standard authentication/session stack, with account/profile and user preferences managed by AuthController, ProfileController, and SettingsController. Blade provides the server-rendered mobile-first shell and feature pages:

• app/Http/Controllers/AuthController.php

• app/Models/User.php

• resources/views/layouts/app.blade.php

Core Personal-Data Domain

The main bounded domains are user-owned tasks, notes, money entries, reminders, and task completion/history. Eloquent models define the application’s persistent entities; the consolidated LifeFlow migration establishes their schema and relationships.

• app/Models/Task.php

• app/Models/TaskLog.php

• app/Models/Note.php

• app/Models/MoneyEntry.php

• app/Models/Reminder.php

• database/migrations/2026_06_13_000001_create_lifeflow_tables.php

Feature Request Flow

Feature controllers accept browser/AJAX actions, apply domain CRUD or status changes, and return rendered pages or dynamic responses consumed by the frontend. Tasks and reminders represent scheduled work; notes support capture/retrieval; money entries feed balance/history views. The dashboard composes cross-domain “today,” cash, note, and upcoming-reminder information.

• app/Http/Controllers/TaskController.php

• app/Http/Controllers/ReminderController.php

• app/Http/Controllers/MoneyController.php

• app/Http/Controllers/DashboardController.php

• resources/views/dashboard.blade.php

Notifications and Scheduled Delivery

Reminder due-processing is separated from HTTP handling: the SendDueNotifications Artisan command finds deliverable reminders and sends push notifications through FCM. Browser/device registration tokens are stored as NotificationToken records and managed by a dedicated controller. This is the main boundary to Firebase Cloud Messaging.

• app/Console/Commands/SendDueNotifications.php

• app/Services/FcmService.php

• app/Models/NotificationToken.php

• app/Http/Controllers/NotificationTokenController.php

Assistant and Export Boundaries

The assistant is a separate UI/controller surface intended for future AI-backed actions, rather than an implemented AI runtime. Export is similarly isolated behind its own controller, keeping reporting/output concerns outside transactional feature controllers.

• app/Http/Controllers/AssistantController.php

• resources/views/assistant.blade.php

• app/Http/Controllers/ExportController.php

Client, PWA, and Infrastructure

Blade pages load compiled frontend assets from public/assets; source JavaScript/CSS is built with Vite. Service workers and the web manifest provide install/offline/PWA behavior, while Firebase’s messaging worker enables web push. Laravel is configured for MySQL persistence, with cache, session, queue, mail, filesystem, and external-service settings under config.

• resources/js/app.js

• public/service-worker.js

• public/firebase-messaging-sw.js

• public/manifest.json

• config/database.php

• config/services.php