MLM & membership web

Member: login, profile, tier, activity summary, downline or network view, applications, documents. Admin: approve members, revenue and compliance dashboards, reports, content management.

UI clarity matters — most users are not technical. Numbers must match what admins export. I build the portal and admin software; compensation plan logic stays with the client and their advisors.

Apply or invite → admin review → approve and assign tier → member onboarded → activity and volume recorded → reports and payouts surfaced in portal → upgrades or compliance holds as rules require.

Role boundaries and what each tier can see are defined in the process flow before PHP auth and dashboard layouts are built. Member portal and admin samples on my work page follow this pattern.

I don't jump straight to screens. Every build starts with a process flow — who does what, in what order, and what status the system shows at each step. That flow becomes the shared map for you, me, backend devs, and QA.

Typical sequence: discovery call → role and feature matrix → process flow sign-off → API contract draft → mobile build per role → integration passes → store or web release → handoff notes. AI speeds drafting at each step; sign-off stays human.

You get visibility at each gate — not a black box and a surprise at launch.

Production mobile for these products is Framework7 plus Cordova — one JavaScript codebase for iOS and Android, native plugins where the product needs camera, GPS, push, or file upload.

I usually split by role: consumer app, merchant or provider app, rider or courier app, and sometimes a lightweight admin mobile surface. Same API layer pattern in each — auth token, role guard, API module, status-driven screens that match the process flow we agreed on.

Framework7 handles routing, lists, forms, modals, and pull-to-refresh patterns that feel native enough for delivery and booking products. Cordova wraps it for the stores. I map each process-flow step to a screen or state so backend devs and QA know exactly what mobile expects at each status.

Before store submission I run device passes on real phones — cold start, background resume, location permissions, and offline or slow-network behavior on the paths that matter for your product.

I'm not siloed on mobile while backend guesses endpoints. I lead with the process flow and a written API contract — roles, status enums, request and response shapes, and error codes the apps already handle.

What I hand backend devs: a status diagram (order/trip/booking/shipment states), JSON samples per endpoint, which role calls which route, and what happens on 401 or invalid transitions. PHP and MySQL on the server side; PDO with prepared statements; thin handlers that match the contract mobile already built against.

During build I review backend PRs for contract drift — field renames, missing statuses, auth gaps — before mobile QA wastes a week. When the contract must change, we version it and update mobile in the same sprint. That coordination is how multi-role platforms stay in sync in production.

On solo or lead full-stack work I own mobile, API shape, and often the PHP layer behind it. AI engineering means Cursor rules in the repo — Framework7 patterns, Cordova plugin usage, API client conventions, security bans — plus skills for recurring tasks like new screens or endpoints.

AI drafts Framework7 pages, API boilerplate, and PHP handlers from the signed-off process flow. I review every diff for security, contract alignment, and store rules before merge. Fellow devs get the same rules and contract doc so AI output stays consistent across the team.

Fast drafts, careful release — whether the product is a delivery app, booking platform, or member portal. See AI engineer services or the blog posts on React Native rules and PHP backends for the same discipline on other stacks.