Lental Mobile App

Rental Management & Reminder

System

Project Documentation

Prepared for: Development Team

Date: July 22, 2025

Powered by Flutter & SQLite

Contents

1 Project Overview 2

2 Target Users 2

3 Core Features 2

4 App Workflow 2
4.1 Landlord Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
4.2 Add Houses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
4.3 Add Tenants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
4.4 Reminder Automation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4.5 Message Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4.6 Notification Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4.7 Vacated Tenant Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . 3

5 Screen Flow 3

6 Database Schema 4

7 Team Task Flow & Developer Assignments 4

7.1 Bertrand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
7.2 Daemma . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
7.3 Biko . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

8 Development Workflow 5
8.1 Git Branching Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
8.2 Development Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

9 Summary 6

1
1 Project Overview
Lental is a Flutter-based mobile application designed to streamline rental prop-
erty management for landlords. It facilitates tracking of rental houses, tenant
management, and automated reminders for rent due dates and lease expira-
tions. The app leverages push notifications, WhatsApp, and SMS for commu-
nication, uses SQLite for local storage, and supports offline functionality.

2 Target Users
• Primary Users: Landlords manage properties, tenants, and reminders.
• External Entities: Tenants receive notifications only.

3 Core Features
1. Landlord Authentication: Secure login and registration system.
2. House & Tenant Management: Create, update, and delete houses and ten-
ants.
3. Rent Due Reminders: Automated monthly notifications for rent payments.
4. Rental Period Expiry Reminders: Alerts for lease expirations.
5. Push Notifications: Delivered via Firebase Cloud Messaging.
6. WhatsApp Integration: Messages sent using wa.me deep links.
7. SMS Notifications: Sent via telephony or external APIs.
8. Offline-First Functionality: Full operation without internet connectivity.
9. Notification Logs: Records of all sent notifications.
10. Vacated Tenant Tracking: Manages inactive tenants and available prop-
erties.

4 App Workflow
4.1 Landlord Authentication
• Login/Register: Supports local or cloud-based authentication.

4.2 Add Houses

• Fields: House name, location.

4.3 Add Tenants

• Fields:
– Name

2
 – Phone number
– Rent amount
– Rent due day (e.g., 5th of each month)
– Rental duration (e.g., 12 months)
• Auto-computation: Calculates start and end dates.

4.4 Reminder Automation

• Rent Due:
– Triggered monthly on the specified due date.
– Sent to landlords and tenants via push, WhatsApp, or SMS.
• Rental Period Expiry:
– Scheduled at 1 month, 1 week, and on the end date.
– Sent to landlords via push and messaging.
– Tenants marked inactive upon landlord confirmation.

4.5 Message Channels

• Push: Firebase Cloud Messaging.
• WhatsApp: wa.me deep link integration.
• SMS: Telephony or external API integration.

4.6 Notification Logs

• Logged Data:
– Recipient
– Date sent
– Notification type (push, SMS, WhatsApp)

4.7 Vacated Tenant Workflow

• Process:
– Landlord confirms tenant departure.
– Tenant marked inactive and removed from reminders.
– House marked as available.

5 Screen Flow
• Login / Register: Authentication interface.

3
 • Home Dashboard:
– Houses:

* Tenants:
· Tenant Details:
· Reminders: View and manage reminders.
· Vacate: Mark tenant as vacated.
– Add House: Input house details.
– Add Tenant: Input tenant details.
– Due Date Overview: Summary of upcoming due dates.
– Notification Logs: View notification history.
– Settings: Configure app preferences.

6 Database Schema
• Table: landlords
– id, name, phone, email
• Table: houses
– id, landlord_id, name, location
• Table: tenants
– id, house_id, name, phone, rent_amount, rent_due_day, start_date,
end_date, status (active/inactive)
• Table: notifications_log
– id, tenant_id, date_sent, type (push/sms/whatsapp)

7 Team Task Flow & Developer Assignments

7.1 Bertrand
• Feature: UI Layout
– Design all screens based on the screen flow.
– Ensure alignment with the UX workflow.
• Feature: Integration
– Connect UI with backend logic and database models.
– Implement CRUD operations and notification logic in the frontend.

4
7.2 Daemma
• Feature: Database Schema
– Design and implement SQLite database structure.
– Include helper functions and migrations.
• Feature: CRUD
– Implement create, update, delete for houses and tenants.
– Add filtering by status or due date.
– Support marking tenants as vacated.
– Expose functions for integration.

7.3 Biko
• Feature: Notifications
– Set up Firebase push notifications.
– Schedule rent due and lease expiry reminders.
• Feature: SMS
– Integrate SMS and WhatsApp messaging.
– Use tenant phone numbers and templated messages.

8 Development Workflow
8.1 Git Branching Model
• main: Production-ready code (managed by Bertrand).
• develop: Staging/QA integration branch.
• Feature Branches:
– feature/ui-layout (Bertrand)
– feature/integration (Bertrand)
– feature/db-schema (Daemma)
– feature/crud (Daemma)
– feature/notification (Biko)
– feature/sms (Biko)

8.2 Development Protocol

1. Commit only to assigned feature/<task> branch.
2. After completing a task:

5
 • Create a Pull Request (PR) to develop.
• Request code review from a teammate.
• Do not merge directly into develop.
3. After review and approval:
• Merge PR into develop.
• Notify Bertrand.
4. Bertrand will:
• Test the develop branch.
• Merge to main if tests pass.

9 Summary
• Bertrand: UI design, app integration, final merge to main.
• Daemma: SQLite database schema, CRUD operations.
• Biko: Push notifications, SMS/WhatsApp messaging.
• Rules:
– Work only in assigned feature branches.
– PRs to develop require teammate review.
– Only Bertrand merges to main.