🚀 Overview

The Android Single Hotel Application is a production-ready mobile app designed for independent hotels, boutique resorts, villas, and guesthouses.
Guests can explore rooms & suites, browse a media gallery, view the property on Google Maps, and complete a secure booking flow with coupons and special requests.
It’s optimized for direct booking to reduce OTA commissions and improve guest relationships.

Experience (E): Built from actual front-desk workflows—rate plans, occupancy rules, blackout dates, and add-ons (e.g., breakfast, airport pickup)—to minimize friction from discovery to confirmation and reduce abandoned bookings.

✨ Key Features

• 🛏️ Room Catalog: Room types with photos, amenities, occupancy, bed types, refundable/non-refundable rates.
• 📅 Booking Engine: Calendar availability, min/max nights, guests/children, promo codes, and add-ons.
• 💳 Payments: Stripe / PayPal / Razorpay / Cash-on-Arrival; optional pre-auth or deposit rules.
• 🖼️ Gallery & Media: Image/video carousels for rooms, facilities, dining, spa, and events.
• 🗺️ Map & Directions: Google Maps with markers, distance, and “Open in Maps” for navigation.
• 📝 Policies & House Rules: Check-in/out, cancellation, child/extra-bed, pet policies.
• 🌐 Multi-language & Currency: Localization + currency formatting; RTL support.
• 🔔 Notifications: FCM push for booking confirmations, reminders, offers, and seasonal packages.
• 📈 Analytics: Conversion, funnel steps, and campaign attribution hooks.
• 🧾 Receipts & Invoices: Branded email/SMS confirmation and downloadable PDF vouchers.
• 🛡️ Security: PCI-aware client flows, HTTPS, tokenized requests, and rate limiting on API endpoints.
• 🎨 Branding: Theme colors, typography, and iconography configurable from a single source of truth.

⚙️ Technical Stack (Expertise)

• Mobile: Flutter 3.x (Dart 3, Material 3) or Native Android (Kotlin) build variant.
• Backend Options: Laravel 10 (PHP 8.1+) REST API or WordPress (Woo/Custom CPT) with JWT/REST.
• Database: MySQL 8 / MariaDB 10.6+; optional Redis cache & queues.
• Maps & Geo: Google Maps SDK + Geocoding/Places APIs.
• Payments: Stripe, PayPal, Razorpay, Flutterwave (pluggable gateway layer).
• Notifications: Firebase Cloud Messaging (FCM) + Crashlytics/Analytics (optional).
• Server Requirements: Nginx/Apache, HTTPS/TLS 1.2+, PHP extensions (pdo_mysql, curl, mbstring, json, openssl).
• Tooling: Android Studio, Gradle 8+, Node 18+ (assets), Composer 2.x, Docker-ready.

🧩 Installation Guide

1. Backend: Deploy Laravel/WordPress, set .env (DB, mail, payment keys), then run php artisan migrate --seed (Laravel) or enable required WP plugins.
2. Catalog: Create room types, rate plans, blackout dates, add-ons, taxes/fees in the admin panel.
3. Mobile: Open the Flutter project → update lib/config.dart (API_BASE_URL, keys) → flutter pub get.
4. Maps & Payments: Add Google Maps key in AndroidManifest.xml and gateway credentials in server env.
5. Branding: Replace icons/splash and edit theme.dart (colors/typography). Upload logo from admin.
6. Build: flutter build apk --release (Android) or flutter build ios (optional iOS build).

📦 Deliverables

• ✅ Flutter/Native Android source code (rooms, gallery, map, booking).
• ✅ Backend API (Laravel/WordPress) with room/rate management.
• ✅ SQL migrations/seed (Laravel) or WP CPT/fields (WordPress) presets.
• ✅ Payment & Maps integration templates.
• ✅ Email/SMS templates for confirmations.
• ✅ Documentation & GPL v3 license file.

📱 Supported Platforms

• Android: 8.0 (API 26)+ phones & tablets.
• iOS: 13+ (optional Flutter build with Xcode 15+).
• Server: Ubuntu 22.04 LTS / cPanel / Docker; HTTPS required for payments.

👨‍💻 Original Developer Credit (Authoritativeness)

This package credits the original commercial author. Support them on their marketplace profile:
CodeCanyon – Original Author.

🔒 Disclaimer (Trustworthiness)

Redistributed under the GPL v3 license for educational and lawful commercial use. We are not affiliated with any hotel brand.
Ensure local tax/tourist-fee rules, deposit/cancellation regulations, and payment gateway terms are respected. Always enable HTTPS,
rotate API keys, and verify availability/overbooking logic before going live.