Aftab Rehan's Work | ContraWork by Aftab Rehan
Aftab Rehan

Aftab Rehan

Frontend Engineer & Next.js Specialist | Figma to Production

    3
    Followers
Followed by Jay K, Rana J, and GALLERY L
Cover image for LaymanMax — Building a live
LaymanMax — Building a live gaming platform I developed LaymanMax for a YouTuber and gaming creator. It is a large gaming platform for players, teams, challenges, tournaments, giveaways, wallets, and live match activity. I built the frontend application, including the home page, leaderboard, player pages, playlists, tournaments, giveaways, user profiles, settings, blog, wallet, account verification, team and clan registration, and challenge flows. This included creating, accepting, and cancelling challenges, along with screens for live match records. The platform supported live challenge updates during LaymanMax YouTube streams (https://www.youtube.com/@LaymanMax/streams), where the displayed information needed to be accurate in real time. This was my first project with a large number of backend APIs. I built custom Node.js APIs with Firebase Cloud Functions for challenges, teams, giveaways, and other platform features. The challenge system involved detailed JSON data and several states that needed to work correctly for both players and teams. I also integrated YouTube APIs. For fan points based on YouTube videos, the project required additional Google access, so I recorded videos explaining the authentication flow and the permissions needed for approval. I worked alongside a junior developer, reviewing code while building my own parts of the application. The fast schedule made quality control challenging, but it taught me a lot about collaboration, code review, and building reliable features under pressure.
0
9
Cover image for Taski — Keeping task management
Taski — Keeping task management simple Taski is a clean, user-friendly to-do app I designed in Figma as a learning project in 2023. It is one of my early designs, and it helped me understand how much value a simple, focused product can have. I designed both the web and mobile experience using one consistent design language. The app focuses on the essentials: creating tasks and marking them complete. I kept the interface calm and distraction-free, using white space so users can focus on their tasks. I also created the logo, reusable components, and responsive layouts with Figma Auto Layout. It was a fun project where I could experiment and turn a small idea into a complete product without adding unnecessary complexity. I published Taski on the Figma Community, where it has been used and duplicated by almost 700 people. Seeing people use an early project like this encouraged me to keep creating.
1
1
61
Cover image for TrueSlip — Reporting Dashboard &
TrueSlip — Reporting Dashboard & Discord Workflow Automation A reporting platform exploring automated CSR slip collection and classification through Discord, with a dashboard for managerial review. Development paused before completion. Overview TrueSlip began with a partly manual reporting process. Managers needed to review daily, weekly, and monthly customer support activity, and counting slips was part of that work. An earlier Chrome extension helped with counting, but the process still required manual steps. I designed and developed the reporting website and landing page myself, working with Team Leads to understand what managers needed to review. The project explored how more of the collection and reporting workflow could be automated. Approach and implementation I moved the collection workflow toward a Discord bot that could collect messages and classify submissions. Rather than rebuild the classification logic from scratch, I reused functions from the earlier Chrome extension and adapted them to the new workflow. The reporting dashboard brought submissions, verification statuses, and transaction histories together for review, connecting the collection process to the information managers needed to see. Technical challenge Keeping recurring automation costs low was a central design consideration. I used Firebase Functions to run the automation and Google Cloud Tasks to schedule it. Each completed task scheduled its next execution programmatically, allowing the process to continue without a separate Google Cloud Scheduler job. This approach made operating cost part of the implementation decision, alongside the functionality of the automation itself. Outcome and current status TrueSlip received positive feedback, but I paused development and delivery before completion. It is not currently being used. The work demonstrates experience designing reporting interfaces around Team Lead requirements, adapting existing classification logic to a Discord workflow, and building recurring automation with operating costs in mind. It also strengthened my understanding of how to connect a partly manual support process to a reporting system.
0
167
Cover image for Comorro — Redesigning an e-commerce
Comorro — Redesigning an e-commerce platform I worked on Comorro for an external client through my role at SyncClouds. I redesigned the website from scratch and built the new interface in Next.js, giving it a consistent, modern light design. My contribution I handled both the desig:n and frontend implementation. I paid close attention to spacing, typography, and layout so the website matched the design across screen sizes. The main challenge The hardest part was managing API calls and keeping data available without requesting it repeatedly. I used Redux to store and reuse data across the application, alongside Vercel’s SWR for fetching and caching API responses. This helped reduce unnecessary requests and made me think carefully about when to fetch fresh data and when to reuse what was already available. I also built loading states and skeleton screens so users could see the shape of the content while it loaded, rather than being left with empty areas. Project status The design was completed, and the website implementation was almost finished. Payment integration was still pending when I moved on to another project at work. The work shown here represents that stage: a completed redesign and a largely implemented website, with the payment flow unfinished. What I learned Comorro helped me get better at caching, managing API requests, and building thoughtful loading states. It also gave me more practice taking a design into a working application, where the details of how a page loads matter alongside how it looks.
1
191