Core Hypothesis — WI QR Feature

🐢 Traditional Flow

Traditional app-based ride booking — طريقة الحجز التقليدية عبر التطبيقات

1 Find the app in the store ~30s

2 Download and install the app ~60s

3 Open the app and allow permissions ~20s

4 Sign up or create account ~60s

5 Verify phone number ~30s

6 Set pickup location manually ~20s

7 Enter destination ~15s

8 Select car and confirm ride ~15s

Total time to first ride ~ 4 minutes

More steps before value is shown = higher drop-off risk.

⚡ WI QR Flow

Scan → Price → Confirm → OTP → Ride — امسح، شاهد السعر، أكد، ثم تحقق

1 Scan QR code 2s

2 PWA opens, pickup auto-set from QR 3s

3 User enters destination 12s

4 System shows cars and prices 2s

5 User selects car and taps Confirm 6s

6 User enters phone number 8s

7 User receives and enters OTP 15s

8 Booking finalized and dispatched instant

9 Live tracking begins instant

Target time to confirmed booking < 50 seconds

OTP happens at the end, after price visibility and user confirmation.

📉 The Friction Funnel

Each extra step increases the chance of user drop-off. QR reduces the flow to only the steps needed to book.

Saw the option

100 users

100%

Started booking

−25%

Reached price view

−27%

Tapped confirm

−31%

Completed OTP

−16%

Booked ride

−6%

The goal is not only to shorten the journey, but to delay identity verification until the user has already seen value.
WI QR target: higher scan-to-booking conversion by removing every avoidable step.

💡 Why This Matters

The QR feature is not just a UI shortcut. It is a low-friction acquisition channel for users who need an immediate ride but do not want to download an app before seeing price and availability.

ميزة QR ليست مجرد اختصار في الواجهة، بل قناة وصول منخفضة الاحتكاك للمستخدمين الذين يحتاجون إلى رحلة فورية ولا يرغبون في تحميل التطبيق قبل معرفة السعر وتوفر السيارات.