Prompt

Create a modern SaaS web application for real estate flipping, encompassing the entire process from buying to renovating and selling properties. The application should be designed with a user-friendly interface and robust functionality as outlined below:

## 🎨 Design & UI
- Implement a clean, minimalistic, and airy design with a blue and white color palette.
- Ensure support for dark mode based on user and system preferences.
- Utilize the latest Material Design icons and a horizontal top navigation menu.
- The application must be fully responsive, prioritizing desktop usability while remaining mobile-friendly.
- Design elements should include cards with soft shadows and rounded corners, ensuring a clear visual hierarchy.
- Incorporate empty states, loading indicators, and success/error toast messages for a seamless user experience.

---

## 🔐 Authentication
- Provide Google login and email/password registration.
- After the first login, present an onboarding process with two options: Create a new account or join an existing account via an invite code.

---

## 👥 Multi-user System
- Define entities: Account (workspace), User, Membership (roles: admin/user).
- Implement rules: Maximum of 10 users per account; Admins have full access, can approve/reject join requests, and change user roles; Users have read-only access.
- Create a join flow where users enter an invite code, resulting in a pending status until approved by an admin.

---

## 🧭 Navigation
- Top menu items: Dashboard, Properties, Settings.

---

## 🏠 Properties Management
### Table
- Implement a paginated table (25 rows per page) with a search bar and sortable columns (only one active sort at a time).
### Columns
- Include: Name, Type (house/apartment/land), City, Layout, Purchase date, Sale date, Purchase price, Sale price, Profit (badge), Status (colored badge).
### Filters
- Allow filtering by Type, Layout, City, Purchase/Sale price (range slider), and Purchase/Sale date (date range).
### Actions
- Enable editing (modal), deletion (confirmation modal), and navigation to property details by clicking the name.
### Export
- Allow exporting selected rows to CSV.

---

## ➕ Create / Edit Property
### Required
- Name
### Optional
- Type, Layout, City, Purchase price, Purchase date, Sale price, Sale date, Status (manual override), Photos (max 10 with drag & drop, reorder, cover image), Publish toggle (default false).

---

## 🔄 Property Status Logic
- Implement manual and automatic status updates based on filled purchase/sale date and price fields, with manual override allowed. Define statuses: Tracked, Purchased, Reconstruction, On market, Sold.

---

## 📄 Property Detail
### Tabs
1) Overview: Read-only property data and photo gallery.
2) Costs: Summary of total costs and a table of costs with actions to add, edit, or delete costs (confirmation modal).
### Cost Form
- Required: Name; Optional: Price, Date, Supplier, Type, Note, File upload.

---

## 📊 Dashboard (Homepage)
### Date Range Picker
- Include options for a custom range and a default of the last 12 months, persisted on the backend.
### KPI Cards
- Display metrics: Total purchases, costs, sales, profit (only from sold properties), ROI %, number of purchases, and sales.
### Rules
- Only sold properties count towards profit, ROI, and sales metrics.
### Chart
- Implement a line chart aggregated by months showing costs and sales.

---

## ⚙️ Settings
### Account
- Include invite code management, user management (pending requests, active users, role switching, removal).
### Preferences
- Dark mode toggle (persisted backend) and currency formatting options (CZK/EUR).

---

## ⚡ UX Details
- Ensure empty states, success/error messages, confirmation dialogs for destructive actions, loading states, and optimistic UI updates.

---

## 🧠 Data Model (implicit)
- Define the following entities: Account, User, Membership, Property, Cost.

---

## ⚙️ Performance
- Ensure pagination (25 rows) and efficient filtering/sorting mechanisms.

Build this application as a scalable SaaS foundation with a clean component structure and reusable UI patterns. Include error handling for edge cases, such as invalid input during property creation/editing and handling network errors during data fetching.