TF-App is a hybrid mobile and web application designed for real estate teams to manage sales operations, track commissions, and leverage geolocation — all from a single codebase that runs as both a web app and a native Android application via Capacitor.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/Niurka77/tf-app/llms.txt
Use this file to discover all available pages before exploring further.
Quickstart
Clone the repo, install dependencies, and launch your dev server in minutes.
Project Structure
Understand the source layout: views, JS logic, Capacitor config, and Android project.
Android Deployment
Build and sync the web app into a native Android APK using Capacitor.
Configuration
Configure Capacitor, the splash screen, and environment settings.
What TF-App Does
TF-App targets real estate professionals who need a lightweight yet capable tool for field operations. It bundles a web UI with native device access through Capacitor’s plugin system.Authentication
DNI-based login with session handling and password recovery flow.
Dashboard
Central hub for sales data, commission summaries, and team activity.
Sales & Commissions
Track property transactions and calculate agent commissions automatically.
Geolocation
Pin and browse property locations directly within the app.
UI Components
Reusable modal dialogs, forms, and wave-styled layout components.
Customization
Theme colors, fonts, branding, and responsive layout adjustments.
Technology Stack
Vite + Vanilla JS
The web layer is a zero-framework Vite project. Builds are fast, the output is small, and there are no framework lock-ins.
Tailwind CSS
All UI views are styled with Tailwind utility classes, loaded via CDN during development and inlined at build time.
Capacitor
Capacitor wraps the
dist/ build output into a native Android WebView, giving the app access to device APIs like the camera, filesystem, and geolocation.TF-App is an educational and personal-use project. The authentication logic currently uses hardcoded demo credentials and should be replaced with a real backend API before any production deployment.