Skip to content
Let's Talk
Projects
E-Commerce & Mobile

WeRenewSneakers — E-Commerce & Mobile App

End-to-end build of a sneaker buy, sell, and restoration platform — from a client-validated e-commerce website through to a production REST API and React Native mobile app, increasing sales by 50% and building a daily-active buyer and seller community.

CLIENT
WeRenewSneakers
ROLE
Full Stack Engineer
DURATION
9 months
TEAM
2

  • 50%

    Increase in online sales after platform launch

  • 2

    Platforms delivered — web and mobile — from a single Laravel API

  • Daily

    Active mobile users checking in to buy and sell sneakers

Tech Stack

  • Laravel
  • Laravel Nova
  • React.js
  • React Native
  • Alpine.js
  • Livewire
  • Tailwind CSS
  • MySQL
  • Redis
  • AWS EC2
  • AWS S3
  • Cloudflare
  • Forge
  • Stripe
  • Google Analytics
  • Figma

Delivery

  1. PHASE 01

    E-Commerce Website Build & Client Validation

    Built the full e-commerce website against the client's requirements — product listings for buying, selling, and restoration services, Stripe checkout, order management, and an admin panel for inventory and fulfilment. The site was reviewed and signed off by the client before any work began on the API or mobile app.

  2. PHASE 02

    REST API Build

    With the web platform validated, extracted and formalised the business logic into a structured Laravel REST API — authentication, product catalogue, order lifecycle, seller submissions, and restoration bookings. The API was designed to serve both the existing web front end and the upcoming mobile app from a single source of truth.

  3. PHASE 03

    React Native Mobile App Development

    Developed the React Native mobile app in parallel while the e-commerce website moved through its go-live process. The app consumed the same REST API, giving mobile users the full platform experience — browsing daily sneaker drops, submitting pairs for sale, booking restoration services, and completing purchases via Stripe — natively on iOS and Android.

  4. PHASE 04

    Web Go-Live

    Launched the e-commerce website to production following client sign-off. Redis-backed caching and AWS S3 media storage were confirmed stable under real traffic before the mobile launch window opened.

  5. PHASE 05

    Mobile App Launch

    After the web platform was confirmed live and performing, submitted the React Native app to the App Store and Google Play. The client now had two fully operational sales channels — web and mobile — running off the same API with consistent product data, order state, and inventory in real time.

Outcomes

  • Client increased online sales by 50% following the launch of the e-commerce platform.
  • Daily active mobile users established — customers returning every day to browse new sneaker drops and list pairs for sale or restoration.
  • Two platforms — web and mobile — delivered from a single Laravel REST API with no duplicated business logic.
  • Stripe payment integration enabled secure online checkout for the first time, replacing manual bank transfers and in-person payments.
  • AWS S3 media pipeline handles high-quality sneaker photography at scale without impacting server performance.
  • Client gained a regular buyer and seller community through the mobile app, building repeat engagement beyond one-off purchases.

Challenges & Learnings

  • Building web and mobile from one API without duplicating logic.

    The core engineering challenge was ensuring the Laravel REST API could serve both the Vue.js web front end and the React Native mobile app with identical business rules — pricing, stock availability, order state, and seller submission validation — without any logic living in the client layer. Every rule was enforced at the API level, so both platforms stayed consistent automatically. This also meant that any future update to pricing or order logic only needed to be made once.

  • Sequencing a multi-platform build without blocking the client's go-live.

    The client needed the website live as quickly as possible to start taking orders. Building the mobile app at the same time risked either delaying the web launch or delivering a mobile app before the underlying API was properly validated by real traffic. The solution was to phase the build deliberately — web first, API formalisation second, mobile development in parallel with the web go-live — so the client never had to wait on the mobile app to start generating revenue, and the mobile launch had a battle-tested API beneath it from day one.