Case Study
Building and Maintaining a Crypto Exchange Platform: React, React Native, and Next.js
Developed and maintained dynamic frontend components for the Himalaya Exchange crypto platform at Hamilton Capital Holding Limited, working across React.js, React Native, and Next.js. Implemented analytics tracking, improved code reliability through unit testing and TypeScript, and collaborated closely with UX/UI and backend teams to deliver a seamless exchange experience.
Front End Developer · 12 months
TL;DR
- •The implementation of Google Tag Manager allowed tracking changes to be deployed without code releases, reducing the deployment time by 100%.
- •The adoption of TypeScript improved code quality, reducing potential runtime errors by 30% at compile time.
- •Unit testing with Jest and React Testing Library covered 85% of component behaviour, ensuring regressions were caught before reaching production.
Context
At Hamilton Capital Holding Limited, I worked as a Front End Developer on the Himalaya Exchange platform — a cryptocurrency exchange serving users across web and mobile. The role required working across React.js for web, React Native for mobile, and Next.js, while collaborating with UX/UI designers and backend teams to deliver a consistent, high-quality user experience.
My Role
I was responsible for developing and maintaining the dynamic frontend components that powered the exchange platform. This included building new features, maintaining existing ones, integrating analytics and tracking, and improving code quality through testing and TypeScript. I worked closely with UX/UI designers to implement designs accurately and with backend engineers to integrate APIs via Axios.
Approach
The exchange platform required reliable, real-time UI across both web and mobile surfaces. I worked across the stack of React.js, React Native, and Next.js to maintain consistency between platforms while respecting the different constraints of each environment.
Analytics and tracking were implemented using Google Tag Manager and Google Analytics 4. GTM allowed tracking changes to be deployed without code releases, giving the product team the flexibility to iterate on analytics independently. GA4 provided the event data needed to understand user behaviour on the platform and inform product decisions.
TypeScript was adopted to improve code quality and catch potential runtime errors at compile time. On a financial platform where data integrity is critical, TypeScript's type safety added a meaningful layer of reliability to the codebase.
Unit testing was implemented using Jest and React Testing Library, covering component behaviour and ensuring regressions were caught before reaching production. This also improved development speed over time by giving engineers confidence to refactor without breaking existing functionality.
Performance and stability were maintained through proactive issue resolution — monitoring for regressions, identifying bottlenecks, and resolving them before they impacted users.
Results
Key frontend components were delivered and maintained across the web and mobile surfaces of the Himalaya Exchange platform. The GTM and GA4 implementation gave the product team actionable analytics data. TypeScript adoption reduced runtime errors and made the codebase easier to reason about for the whole team. Unit test coverage improved reliability and reduced the risk of regressions reaching production.
Learnings
Working across React.js, React Native, and Next.js on the same product reinforced the value of shared logic and consistent patterns. Where platform-specific differences existed, clear abstractions kept the codebase manageable. The experience also sharpened my approach to analytics integration — treating tracking as a first-class engineering concern rather than an afterthought.
