Fruit Hub
Earlier mobile product and UI work.
Three small browser experiments show how I think about request pipelines, interaction details and module boundaries. They are simplified demos—not fake product screens.
A CQRS-style request is easier to trust when you can see the stages it passes through. Toggle the cross-cutting steps, run the request, and watch the trace.
Inspired by the explicit pipeline approach I use in AstraFlow and enterprise backends. This demo does not claim production timing or benchmarks.
Type or paste six digits.
The interaction is. This demo handles digit filtering, forward focus, backspace, paste, completion, validation feedback, clearing and resend timing.
Inspired by Flutter OTP Kit. The browser demo is intentionally small; authentication trust still belongs to the server.
Open the Flutter package case study ↗Select a module to see what it owns and what it is allowed to depend on. The point is not the exact boxes—it is keeping responsibility and direction easy to explain.
Authentication, users, roles, permissions and sessions live here. Business modules consume identity contracts; they do not reimplement authentication.
These projects helped me learn mobile flows, API integration, local persistence and product UI. Public repos are linked; the rest are intentionally presented as archive notes.
Arabic-first educational simulations for oil-remediation experiments with local saved results.
GitHub ↗Flutter / booksGoogle Books discovery, search, previews, authentication, profiles and favourites.
GitHub ↗Earlier mobile product and UI work.
Earlier mobile product and UI work.
Earlier application workflow work.
Earlier Flutter UI and API integration work.
Earlier content and API-driven mobile work.
Earlier data-driven mobile interface work.
Earlier realtime/product interaction work.