1. Mobile App Requirements

Oh Bhaisahab (OBS) Experiences - A trekking tribe's digital home.
🥾
App Philosophy The OBS mobile app is not a standard transactional utility. It is designed to act as a digital home for high-altitude explorers, supporting them through three distinct journey states: Pre-Trek (anticipate/book), On-Trek (offline safety/coordination), and Post-Trek (memories/badges).

App Structure & Navigation

The app switches layouts contextually. Below is the primary bottom navigation layout utilized during standard Pre-Trek and Post-Trek contexts:

🏔️ Explore
📅 My Treks
🤝 Tribe
📸 Memories
👤 Profile

Contextual Navigation (On-Trek Mode): When a trekker is active on a mountain (within 24 hours of start or currently on a route), the interface morphs: a floating, persistent SOS emergency button is pinned on the viewport, battery-saver optimizations activate, offline caching enforces 100% operation, and the "Trek HQ" panel replaces the standard explore view.

Onboarding & Trek DNA Quiz

To deliver high personalization, new users complete a cinematic 5-question onboarding quiz to determine their Trek DNA. This logs their baseline cardiovascular fitness, experience milestones (Never trekked, Beginner, Intermediate, Expert), regional interests, and preferred companions.

Core Product Modules

  • Explore Feed: Search engine filtering treks by difficulty levels, best weather months, duration lengths, regions, and guide bios.
  • My Treks Panel: Countdown timers, offline packing checklists, and localized group chat channels with guides.
  • SOS System: Designed to function under zero cellular data connectivity. Fires native SMS alerts with GPS coordinates to emergency contacts, logs incident timestamps, and displays offline first-aid references for acute mountain sickness.
💡 Product Knowledge Check: What contextual layout triggers automatically during an active trek?
The payment installment checkout flow locks down the client-side inputs.
A persistent floating SOS trigger activates, battery-saver protocols engage, and offline-first mappings take priority.
The community feed redirects all users to B2B corporate team pages.
🏕️ Guide Checkpoint: Spot on! This contextual transition ensures safety, battery longevity, and route offline capabilities are accessible in the wilderness.

2. Website Requirements

Establishing trust, seo visibility, and frictionless transaction catalogs.

Website Philosophy

Our website acts as the primary customer acquisition channel. While the app retains the tribe post-purchase, the website must establish trust and authority within the first five seconds of visitor landing.

Structural Sitemap

ohbhaisahab.com/
├── / (Homepage - Cinematic autoplay video reels & region selections)
├── /treks (Interactive map search & seasonal month sliders)
│   ├── /treks/[slug] (Trek detailed specifications, batches, packing, guides)
│   └── /treks/region/[region]
├── /stories (User journals, verified review listings, adventure blogs)
├── /membership (OBS subscription details)
├── /b2b (Custom corporate adventure proposal builder)
└── /safety (Emergency rescue protocols, SDRF directory, AMS indicators)

Trek Detail Page Architecture

Each trek landing page represents a comprehensive conversion funnel, combining structural metadata, FAQs, review score systems, and active capacity indicator tables:

Page Module Objective SEO Schema Target
Trek Metrics & Facts Displays altitude peaks, distances, best months, and difficulty grades. TouristTrip Schema
Dynamic Batch Selector Shows upcoming departure schedules, active pricing, and remaining seats. Product & Offer Schema
Verified Reviews Panel Verified trekker testimonials with photo attachments and ratings. AggregateRating Schema
Section FAQs Trek-specific guides detailing altitude preps and packing recommendations. FAQPage Schema
💡 Product Knowledge Check: What is the main objective of the OBS website landing page?
To serve as a messaging portal for group chats.
To build credibility, host optimized SEO landing catalogs, and deliver frictionless booking checkout structures.
To run offline GPS tracking maps in the browser.
⛺ Guide Checkpoint: Correct! The website acts as our primary customer acquisition engine, and must optimize conversion flows for incoming web traffic.

3. Admin Panel Requirements

The operational nervous system managing guides, batches, payments, and incidents.

3.1 Role-Based Access Control (RBAC)

We restrict read and write capabilities across the back-office according to staff responsibility profiles. This ensures that guide check-ins, financial payouts, content editing, and rescue coordinations are handled securely.

3.2 Operational Dashboard Metrics

  • Active Mountain Coordinates: Real-time map displaying current coordinates of ongoing trek batches, assigned leads, and localized weather metrics.
  • SOS Alert Feeds: High-priority, floating dashboard banners that trigger auditory alerts when a trekker triggers an SOS. Includes emergency contacts snapshotting and satellite routing indicators.
  • Refund Queues: Auto-calculates transaction refund fractions based on target cancellation policy date margins.
  • Inventory Tracker: Catalogs sleeping bags, tents, barometric devices, and oxygen cylinders, warning of shortages ahead of busy seasonal departures.
💡 Product Knowledge Check: Why are SOS emergency displays positioned at the top of the admin interface?
To ensure instant operational awareness and immediate dispatch actions during HAPE, HACE, or weather emergencies.
To monitor average visitor session durations.
To allow content editors to adjust blog captions.
🏔️ Guide Checkpoint: Correct! Centralizing emergency alerts saves critical time during evacuation calls.

4. Community System Design

Designing social loops, trek memoir journals, and gamified explorer badges.

4.1 Testimonials vs. Community Feed (Hybrid Choice)

The Architectural Recommendation: We reject standalone static testimonials in favor of a **Hybrid Architecture**. The Community Feed serves as a living, breathing social feed (trip photos, day-by-day journals, trail reels), while verified reviews are structured separately on trek checkout pages. Both are pulled from the same unified pool of authentic content, maximizing trust while building a true trekking tribe.

4.2 Badges & Gamification Milestones

To incentivize retention, the platform awards point achievements (**OBS Miles**) that count toward status ranks. These ranks yield direct benefits matching the logic of our database models:

  • First Summit: Awarded on completing their first OBS route.
  • Monsoon Maverick: Awarded on completing wet weather crossings.
  • High-Altitude Pro: Unlocked on crossing passes above 5,000m.
  • Ambassador Badge: Earned by referring 5+ new booking signups.

4.3 Automated Content Moderation

The community feed utilizes automated keyword filters to block competitive ads, alongside asynchronous image classification jobs to flags inappropriate photo uploads before they go live on public feeds.

💡 Product Knowledge Check: How does the hybrid community model solve the "static review" issue?
By paying creators to draft corporate reviews on social media.
By pulling verified reviews dynamically from real, post-trek community journal entries, keeping the content fresh and credible.
By blocking community posts that don't receive 5-star scores.
⛺ Guide Checkpoint: Spot on! Linking reviews directly to actual trip memoirs guarantees authentic social proof for incoming visitors.

5. Trek-Specific Smart Features

Altitude intelligence checkers, offline maps caching, and celestial stargazing forecast panels.

5.1 Altitude Intelligence Warning System

The app monitors altitude changes using device barometric sensors and GPS signals, prompting check-ins at key elevation thresholds:

3,000m+  →  Display AMS Symptoms Informational Guide
3,500m+  →  Trigger Pace and Hydration Reminders
4,000m+  →  Daily Acclimatization Check (Rate Headache/Nausea 1-5)
4,500m+  →  Mandatory Acknowledgment check + Automatic Guide Warning Notification

5.2 Vector Map Caching

We download Mapbox vector tiles (encompassing the route coordinates and a 5km buffer) to local storage before departure. This enables offline contour mapping, elevation charting, waypoint indicators, and route deviation warnings without internet connectivity.

5.3 Stargazing & Microclimate Trackers

Calculates celestial events (moon phases, Milky Way visibility, sunrise/sunset hours) completely offline using local longitude coordinates. Provides microclimate alerts (e.g. afternoon thunderstorm risk) derived from past guide experience data.

💡 Product Knowledge Check: Why is offline barometric check capability critical for the app?
Because high-altitude valleys have zero cell data connectivity; HAPE/HAPE symptom checks and route deviation guides must function completely offline.
To enable streaming music during mountain climbs.
To update points transactions in real time.
🗻 Guide Checkpoint: Exactly! Mountain weather and cellular connectivity are volatile; ensuring core health and routing tools are offline-capable is critical for safety.

6. Growth & Monetization

Maximizing lifetime values via memberships, referral loops, B2B pipelines, and media packages.

6.1 Business Models

While core trek bookings account for ~80% of revenue, we expand operational margins using four business streams:

  • OBS Pass (Membership): Pro subscribers (₹1,499/year) receive priority booking windows, early access, and free PDF journal exports.
  • Referral Credit System: Awarding ₹500 travel credit to both referee and referrer. Credit-only rewards prevent cash drain and incentivize repeat bookings.
  • Media Packages: Pre-purchased videography bundles. Local guides capture high-resolution drone footage and pack it into a customized cinematic memory reel.
  • Trek Insurance Add-on: Checkout upsell covering HAPE/HACE emergency evacuations and search operations for a low cost (₹299).
💡 Product Knowledge Check: Why are referral points awarded as credit rather than cash payouts?
To simplify backend tax filing regulations.
To prevent cash draining, incentivize repeat bookings, and lock users into the OBS ecosystem.
Because credit operations load faster on mobile devices.
🏕️ Guide Checkpoint: Spot on! Credit lock-in keeps repeat booking metrics high and lowers customer acquisition costs.

7. Technical Recommendations

Headless systems stack, offline database sync, and server scaling pathways.

Headless System Architecture

The tech stack decouples the frontend client interfaces from our data services, allowing us to serve multiple applications (iOS, Android, Web, and Admin) from a unified backend API:

┌─────────────────────────────────────────────────────────────┐
│                    CLIENT FRONTEND                          │
│  React Native App (App Stores)  │  Next.js 14 Website       │
│  React Back-Office Admin (Vite)                             │
└─────────────────────┬───────────────────────────────────────┘
                      │ Secure REST APIs / JSON Web Tokens
┌─────────────────────▼───────────────────────────────────────┐
│                    BACKEND APPLICATION                      │
│   NodeJS Fastify Engine (Scalable Modular Monolith)         │
└─────────────────────┬───────────────────────────────────────┘
                      │
           ┌──────────┼──────────┬──────────┐
           ▼          ▼          ▼          ▼
       PostgreSQL   Redis      S3/CDN    BullMQ Tasks

Recommended Technical Stack

Layer Recommended Technology Objective
Mobile Client React Native (Expo bare) Cross-platform iOS/Android code sharing.
Local Cache DB WatermelonDB High-speed SQLite syncing for offline app operation.
Backend Engine NodeJS NestJS / Fastify High-throughput REST and WebSocket routing.
Queue Manager BullMQ / Redis Asynchronous email, SMS, and media background processing.
Content CMS Sanity.io Headless editor for blog posts and catalog updates.
💡 Product Knowledge Check: What is the primary benefit of the headless architecture for OBS?
It allows the database to run without PostgreSQL installed.
It separates client views from backend logic, allowing a single backend API to power the Web, iOS, Android, and Admin platforms.
It speeds up the CSS loading times.
⛺ Guide Checkpoint: Correct! Single-endpoint APIs minimize code maintenance, ensure unified database integrity, and allow mobile and web clients to co-exist cleanly.

8. Brand Visual Style

Wilderness, human craft, and unhurried motion principles.

Design Pillars

  • Cinematic Widescreen: Full-viewport layouts, high-contrast imagery, and atmospheric overlays that make the user feel the mountain before they book.
  • Raw & Organic: Subtle grains, paper textures, and custom handwritten ligatures that avoid the sterile flatness of standard tech startups.
  • Human-First: Prioritizes real photographs, names, and guide biographies over generic vectors or AI stock assets.

Interactive Brand Color Palette

Click on a color block below to see its design name and functional role in our UI specification:

Bleached Cotton
#F7F3EC
Zenith Sky
#4A90C4
Bugyal Meadow
#7BA05B
Wildflower Rust
#D4845A

Motion & Animations

Motion must mimic the mountain wilderness: deliberate, unhurried, and powerful. We ban spring-loaded, bouncy elements in favor of slow cross-fades (400ms). When a user completes a trek, their digital certificate unfurls using a letterpress paper transition, creating a sense of achievement.

💡 Product Knowledge Check: What type of typeface is recommended for displaying technical elevation data?
Spirited, handwritten ligatures like Caveat.
A clean, high-contrast monospace font like DM Mono or JetBrains Mono.
An italicized serif font like Playfair Display.
🗻 Guide Checkpoint: Spot on! Using a high-readability monospace font for technical numbers (altitudes, routes, coordinates) ensures clean alignment and legibility in the field.