Overview
EWAPT is an EWWD product demo for multi-tenant apartment and resident management. It connects a Flutter mobile app for residents and operational staff with a Laravel API and Filament administration panel. The reference implementation is deployed as a demo and uses apartment-scoped data, roles, and branding.
Business Problem
Apartment operations are often split across WhatsApp groups, paper visitor passes, phone calls, manual billing files, and separate booking records. Residents lack one trusted service channel, while management has limited visibility into requests, payments, access, and follow-up.
Implemented Solution
- Announcements, alerts, and bilingual resident content
- Billing records, payment workflows, and finance administration
- Maintenance and customer-service tickets with assignment and status
- Facility and service booking
- QR-based visitor passes and gate validation
- Parking requests and records
- Resident, security, technician, finance, management, and super-admin roles
- Apartment-scoped multi-tenancy, branding, and data access
- Flutter mobile app, Laravel API, Filament admin, notifications, and offline cache patterns
Current Evidence Status
EWAPT is a deployed EWWD product/demo. The PRD defines adoption, collection, response-time, and task-saving targets, but those targets are not published as achieved results.
Technical Implementation Logic
| Layer | Choice | Reason |
|---|---|---|
| Mobile | Flutter | One maintainable mobile codebase for resident and operational journeys |
| API | Laravel | Role-aware business workflows, integrations, and tenant-scoped access |
| Admin | Filament | Operational dashboards, finance, content, and staff workflows |
| Data | MySQL/MariaDB | Relational records scoped by apartment, unit, user, and role |
| Notifications | Firebase-ready service | Push notifications and operational alerts when deployment credentials are configured |
Frequently Asked Questions
Is EWAPT a client deployment?
It is currently presented as an EWWD product/demo with a deployed reference environment.
What can be adapted?
Modules, branding, roles, property scope, payments, notifications, and integrations can be scoped per deployment.
Next Step
Planning a resident app or property-operations platform? Review the modules, roles, properties, and integrations required for a practical pilot.