u/lastfootballHL

السلام عليكم! ابقول لكم عن تجربتي في بناء تطبيق بـ Flutter، رغم إني ما أشتغلت فيها قبل كذا.

الخلفية:

أنا اشتغلت في Python و HTML و PHP كتجارب وهوايه

لكن جتني فكره تطبيق لتنظيم البيت لين سميته مدبر وقلت ابغاها بلغه وحده وشفن Flutter كانت سهله وفكرتها حلوه انها تدمج بين ثلاث ويب وايفون واندرويد. قررت أتعلمها على خفيف ومع ai بنيت Mdbir في 4 شهور لاني ماطنت مستعجل

كيفية العمل:

✅ الانتقال من الويب للموبايل — Python و HTML و PHP أعطتني أساس قوي للـ logic والبنية

✅ Flutter سهل أسرع لما تكون عندك خبرة برمجية — ما توقعت الانتقال يكون سهل كذا

✅ استخدمت AI للمساعدة — جيميني بالبدايه يمسك بي خط بدون رجعه وكودكس يعدل ويرجعني وكلاود استخدمته بالتصميم

✅ تطبيق واحد لـ iOS و Android — بدون ما أكتب الكود مرتين

بلغتين مختلفتين :

وش فكره مدبر Mdbir تنسيق أمور البيت بدون فوضى WhatsApp:

🛒 قوائم التسوق المشتركة ) المدام تسجل غرض يوصلني تنبيه بسرعه (

🧊المستودع والثلاجه

💊 تتبع الأدوية والمواعيد لكل العائله مو بس لوحدي

🚗 تنبيهات صيانة السيارة

🌿 جداول سقاية الحديقة والسماد

📋 توزيع المهام على أهل البيت

📄 قسم الضمانات والفواتير مع التنبيهات

التقنيات اللي استخدمتها:

Flutter (iOS و Android)

Appwrite (database)

RevenueCat (الاشتراكات)

Firebase (التنبيهات)

Riverpod (إدارة الحالة)

اللي تعلمته:

الخبرة السابقة تفرق والحقيقه اخر خمس سنوات اهملت البرمجه لكن مع ai رجعت لها واللي خلاني اجلس ٤ شهور التدقيق واخراج العمل على اكمل وجه

Flutter سريعة لما تكون عندك أساس برمجي — ما احتجت وقت طويل للتعلم

الذكاء الاصطناعي يسرّع الأشياء — خاصة الأشياء الجديدة زي Flutter

الفكرة الذكية — واحد يشترك و يدفع Pro، كل العائلة تستفيد

اهتميت للغه العربية من اليوم الأول — ما أضفتها بعد ما خلصت، بنيتها من البداية.

موجود الآن:

ابحث عن "Mdbir" او مدبر بالعربي في App Store أو Google Play

— يوجد 90 يوم تجربة مجاني. تقدر تلغي اشتراكك قبل نهايه ٩٠ يوم

أسألوني عن أي حاجة عن التطبيق أو التقنيات

I spent a year building Mdbir app because my family's "system" was broken.

The Problem:

Shopping list = WhatsApp group (scattered messages)

Warranties = a drawer nobody opens

Car insurance expiry = discovered the day it expires

Garden watering = "I think I watered it last week?"

Medications = hope nobody runs out

Sound familiar? We were managing our household through fragmented chat history and sticky notes. I knew there had to be a better way.

What I Built:

A single app for all household coordination:

🛒 Shared shopping list (everyone adds, one person buys)

📦 Inventory tracking (Full / Running Low / Empty)

💊 Family medications (dosage, expiry, doctor appointments)

🌿 Garden schedules (watering, fertilizing reminders)

🚗 Car maintenance (oil changes, insurance, registration)

📋 Household tasks (distributed across family)

📄 Warranties & receipts (archived with expiry alerts)

The Build (Tech Stack):

Flutter (one codebase, iOS + Android)

Appwrite (backend, database, auth)

RevenueCat (subscription management)

Firebase (push notifications)

Riverpod (state management)

The Hardest Part: Permissions Model

Each location has an owner and members. The subscription tier follows the owner, not the member. So if I'm on Pro and invite my family, they all get Pro features without paying separately.

This was the unlock for family adoption—no friction, no "who pays" negotiations.

Arabic + English from Day One

Added ~20% dev time but was non-negotiable since most target users are Arabic speakers. It forced me to think about localization early instead of bolting it on later.

Surprising Winners:

I almost cut the garden and car modules for v1. They ended up being the most popular with early testers. Lesson: people forget about these things until crisis mode, so they value the app most for preventing those crises.

What I Learned:

Start with one pain point. Onboarding people into a full household system kills adoption. Start with one broken loop (shopping list, medications, whatever's losing them money/time).

Permissions are complex. The owner/member model seemed simple until real families tested it. Edge cases are everywhere (divorced parents, adult kids, elderly relatives).

The subscription model matters. Per-member billing = friction. One owner pays, family gets access = adoption.

Retention is about first wins. People stick around because they solved the immediate problem (no more forgotten milk), not because they filled out the whole household model.

Localization early = better product. Thinking in two languages forced clarity on UX decisions.

Current Status:

Launched on iOS and Android. Running a 90-day free trial to test retention and feature usage. If you're curious, search "Mdbir" on the App Store or Google Play.

What I'm Curious About:

How do you all handle shared systems in your families? What actually sticks?

For those building SaaS: what surprised you most about user adoption?

For years my family's "system" was:

• Shopping list = WhatsApp group
• Warranties = a drawer nobody opens
• Car insurance expiry = discovered the day it expires
• Garden watering = "I think I watered it last week?"
• Medications = hope nobody runs out

So I built Mdbir — a family home management app. Here's what it covers and how I built it.

What it does:

🛒 Shared shopping list — everyone adds what they need, one person buys
📦 Inventory tracking — Full / Running Low / Empty, so you know before you run out
💊 Family medications — dosage schedules, expiry dates, doctor appointments per person
🌿 Garden — watering and fertilizing schedules with custom frequencies and reminders
🚗 Car maintenance — oil changes, insurance expiry, registration, odometer, spare parts log
📋 Household tasks — distributed across family members
📄 Warranties & receipts — archived with expiry alerts
💰 Price comparison — track prices across stores
🏠 Multiple homes — manage your home and parents' home separately

How I built it:

• Flutter — one codebase for iOS and Android
• Appwrite — backend, database, auth, cloud functions
• RevenueCat — subscription management
• Firebase — push notifications
• Riverpod — state management

The hardest part was the permissions model: each location has an owner and members. The subscription tier follows the owner, not the member — so if I'm on Pro and invite my family, they get Pro features inside my location without paying separately.

Arabic + English localization from day one added ~20% dev time but was non-negotiable since most of my target users are Arabic speakers.

The garden and car modules almost got cut for v1 — they ended up being the most popular with early testers.

Current status:
Launching the 90-day free trial in 2 days. I'll drop the link in the comments the moment it's live.

Happy to answer anything about the build — architecture, the subscription model, the permissions system, whatever.