Malabji

Treatment

Football pitch bookings in Jordan run through phone calls and WhatsApp. You ask a ground about Thursday, gather players, then find the slot has gone; payment happens in cash on arrival. You also need nine other players.

حجز الملاعب في الأردن يجري بالمكالمات وواتساب. تتصل بالملعب، وتسأل عمّا هو شاغر يوم الخميس، فيُعطى لك وقت قد لا يبقى متاحًا حين تجمع اللاعبين، وتدفع نقدًا عند الوصول. نصف العناء في الحجز، والنصف الآخر أنك تحتاج تسعة أشخاص آخرين.

Malabji handles both. The booking side is a live availability calendar per pitch with instant reservation. The social side lets you look for a team, challenge another one, and run or join a tournament, plus a directory of sports academies.

يعالج «ملعبجي» الأمرين. جانب الحجز تقويم إتاحة مباشر لكل ملعب مع حجز فوري. والجانب الاجتماعي يتيح البحث عن فريق، وتحدّي فريق آخر، وإنشاء بطولة أو المشاركة فيها، إضافة إلى دليل للأكاديميات الرياضية.

I founded it and built all of it: the Expo client for both stores, the Supabase backend, the store releases, and the support that follows a real product.

أسّسته وبنيته بالكامل: تطبيق Expo للمتجرين، وخادم Supabase، وإصدارات المتاجر، والدعم الذي يتبع أي منتج حقيقي.

Challenges

1. 01

   Never sell the same hour twice

   The problem

   Two people opening the same 7pm slot at the same time is not a rare edge case on a Thursday evening. It is the normal load. Checking availability and then writing the booking is two steps, and anything can happen between them.

   What I did

   Availability is never trusted from the client. The reservation is a single server-side transaction with a uniqueness constraint on (pitch, time range); the loser of a race gets a clean 'just taken' state and the calendar refreshes under them rather than a failed payment.

2. 02

   In-app purchases on two stores with different rules

   The problem

   Apple and Google disagree on receipts, on what a restore means, and on what they will approve. A purchase that succeeds on the device but never reaches the backend is the worst possible bug in a paid product.

   What I did

   Entitlement is decided on the server from a verified receipt, never from the client's word. The client re-validates on launch and after every restore, so a purchase interrupted mid-flight reconciles itself the next time the app opens.

3. 03

   Calendar and notifications that respect the user

   The problem

   A booking is useless if the player forgets it. But asking for calendar and notification permission on first launch, before the app has earned anything, gets both denied.

   What I did

   Permissions are asked at the moment they pay off. The calendar prompt appears right after a successful booking, not before. Reminders are scheduled locally so they still fire if the device is offline.

4. 04

   Deep links that survive an install

   The problem

   Growth happens when someone shares a match invite in a group chat. If the tap opens a store page and the invite is lost after installing, the whole loop breaks.

   What I did

   Invite links carry their payload through the install, so a new user lands on the actual match after opening the app for the first time, not on a generic home screen.

Results

• Live on the App Store and Google Play.متاح على App Store وGoogle Play.
• Bookings, team search, challenges and tournaments in one app.الحجوزات والبحث عن فرق والتحديات والبطولات في تطبيق واحد.
• Built and operated solo, from schema to store listing.بُني ويُشغَّل منفردًا، من المخطط حتى صفحة المتجر.