العربية
Tested

Arcadea

A personal game-backlog tracker in Flutter.

My role Two-person course project. My part: led the Figma design-system foundation; designed and prototyped 11 of 23 screens; wired authentication, search, filter and stats interactions. In Flutter: 6 screens, 5 shared widgets, the AuthProvider and the three theme files.

Year
[CONTENT REQUIRED]
  • year
Shown only in review mode.
Context
[CONTENT REQUIRED]
  • context
Shown only in review mode.
Status
Tested
Team size
[CONTENT REQUIRED]
  • teamSize
Shown only in review mode.
Problem

What needed solving.

Players track their backlog across spreadsheets and screenshots. The brief asked for one app where university students and casual gamers can sort games by status, search, open details and see simple statistics.

Screen by screen

What the user sees.

  1. Library · All games
    01

    Library · All games

  2. Game detail · Silent Hill 2
    02

    Game detail · Silent Hill 2

  3. Stats
    03

    Stats

  4. Welcome
    04

    Welcome

  5. Statistics view with brand-coloured chart
    05

    Statistics view with brand-coloured chart

  6. Reusable widgets from the design-system foundation
    06

    Reusable widgets from the design-system foundation

Approach

How I approached it.

Three statuses — Want to play, In progress, Completed — organize the whole app in blue, amber and green. The design system was fixed before the first screen: tokens, text styles and the core components, then Flutter theme files that mirror the Figma Design System v2 page.

Evidence

What the test said.

100% n = 5
Task completion, 10 tasks
79.5 n = 5
Mean SUS score (CI 73.5–85.5, computed)
6
Usability issues (severity 1–2 on Nielsen's 0–4 scale; none blocking)
3 / 6
Issues on screens I designed and built (Sign Up, Profile, empty search)
[object Object]
Participant P5
[object Object]
Debug build on an Android emulator; participants completed tasks from their homes while the team collected results and observed errors "when possible".
Takeaway

What this one leaves behind.

The screens shown here are Figma frames, not captures of the running Flutter build. The report lists six proposed fixes and implements none of them — a clear next iteration if the project continues.

Reflection

What I took from it.

[CONTENT REQUIRED]
  • reflection
Shown only in review mode.

A short reflection from Wejdan — to be written.

A team project; individual contributions as noted above.