Talha Tanveer

Case study · E-commerce

Alaaaldeen

A bilingual (English and Arabic) Flutter shopping app for phones, tablets, laptops and smartwatches.

Illustrative preview · no public screenshot available
Category
E-commerce
Role
Flutter developer
Team
Team of 3 developers
Duration
Jun – Aug 2024
Technologies
  • Flutter
  • Dart
  • GetX
  • Dio
  • REST API

01

Overview

Alaaaldeen is an online electronics store selling mobile phones, tablets, smartwatches, laptops and Apple products. This Flutter app connects to the store through a REST API and supports English and Arabic. I was one of three developers who built it, working mainly on accounts, checkout, addresses, orders and returns.

02

Key features

  • English and Arabic, with right-to-left support
  • Browse by category, search, filter, sort and scan QR codes
  • Product pages with reviews and similar products
  • Wishlist, cart and checkout
  • Address book, orders, transactions and returns
  • Sign-up with OTP, password reset

Stack

How it’s built

App

  • Flutter
  • Dart
  • GetX + Provider
  • Dio
  • Isar local database

Back end

  • Store REST API (OpenCart)

03

My contribution

  1. 01

    Accounts

    Login and sign-up screens, plus the forgot-password and reset-password flow.

  2. 02

    Checkout and payment

    The first checkout, checkout-payment and payment screens, with English and Arabic copy.

  3. 03

    Addresses

    Address management for adding, editing and choosing delivery addresses.

  4. 04

    Orders and returns

    Order details with product and history information, and the full return-request feature — model, repository, API call, screen and controller.

  5. 05

    Information pages

    About, privacy and terms pages.

05

Challenges

Challenge

One app in two languages, including right-to-left Arabic.

How I addressed it

Every screen I built takes its text from English and Arabic string files and uses layouts that mirror correctly for right-to-left, with an Arabic typeface (Cairo) alongside Poppins.

Challenge

Building on a store API designed for the website.

How I addressed it

Each feature follows the same layers — model, repository, API call, controller and screen — so the store API’s quirks stay in one place and the screens stay simple. The return-request feature was built that way end to end.

Challenge

Long flows like checkout and returns on a small screen.

How I addressed it

Checkout is split into address, order review and payment steps, and return requests are validated in the app before they’re sent, so customers fix mistakes as they go.

06

Outcome

Alaaaldeen has no public link to share.

  • 22 of the app’s roughly 140 commits, between June and August 2024.

07

What I learned

“Agreeing on one structure for every feature made it easy for three developers to work in parallel without stepping on each other.”

Next project

Beostoc

A connected B2B platform for Irish agrifood — sales, live-animal supply and production, now with supervised AI agents.

Have an idea? Let’s build it.

If a project like this is on your roadmap, I’d be glad to hear about it.