Fake Store Mobile App

Overview

A mobile app built through staged university milestones.

The source material for this project came from the Mobile Application Development folder. The reports show a staged React Native app build using the Fake Store API, with repository evidence, functional screen captures, and later shopping cart behaviour.

I am not publishing the full annotated assessment PDFs. This page turns the project into a portfolio case study and keeps the raw submission material private.

Tools and concepts

• React Native mobile app development.
• Fake Store API data for categories, product lists, and product details.
• React Navigation-style screen flow between categories, product lists, detail views, and cart screens.
• Redux shopping cart state with add, increase quantity, and decrease quantity behaviour.
• Mobile UI states including empty cart, cart with products, item counts, total cost, and cart badge feedback.

What I did

I built the app flow across multiple milestones: first getting category and product browsing working, then adding cart state and shopping cart screen behaviour. The source reports show the app loading categories from the API, navigating to product lists and detail screens, and later managing cart quantity and totals.

Key implementation details

• Category screen loaded available product categories from the Fake Store API.
• Product list screen displayed products for the selected category.
• Product detail screen supported inspecting a selected product before cart interaction.
• Redux cart slice managed add-to-cart, increase-quantity, and decrease-quantity actions.
• Cart screen handled empty and populated cart states, including totals and quantity controls.

Problems solved and challenges

The project required connecting API data, navigation, and shared cart state in a way that remained understandable on a small screen. The main challenge was making state changes visible and predictable as the user moved between product screens and the cart.

What I learned

• Even a small mobile app becomes a system once API data, navigation, and global state interact.
• Cart behaviour needs clear feedback, especially around empty states, quantities, and totals.
• Milestone reports are useful source material, but a portfolio page needs a cleaner story than an assessment submission.

Future improvements

• Add clean screenshots from the app instead of using annotated assessment captures.
• Add a short architecture diagram showing API data, navigation, and Redux cart state.
• Review loading/error states and document how the app behaves when API requests fail.
• Add a public repository link only if the code is safe and appropriate to share.