Wojo

Wojo is a hospitality and workspace operator that initially relied on the GetGround platform for its mobile and web applications.

In late 2020, during the Covid period, Wojo decided to separate from the GetGround platform and migrate to an independent technical stack while continuing to operate live services.

This migration had to happen under significant time pressure, with active users in production, during a period of global uncertainty and remote collaboration, while ensuring continuity of service for both mobile and web applications.

The main challenge was executing a safe and timely platform separation while maintaining operational continuity.

Wojo's mobile and web applications were deeply coupled to GetGround's backend and infrastructure. Decoupling them required migrating critical functionality without service disruption, rebuilding backend-for-frontend flows, reworking authentication and integration layers, and coordinating mobile and web teams under tight deadlines.

Any delay or regression would have had immediate business impact.

I initially joined the Wojo project as a mobile-focused developer, responsible for migrating and stabilizing the React Native mobile application as Wojo transitioned away from GetGround.

I completed the mobile migration ahead of schedule. As the web migration progressed and pressure increased, I began supporting the web team, helping them address architectural issues and unblock delivery.

Over time, my role naturally expanded to full-stack ownership, spanning mobile application migration and stabilization, backend-for-frontend coordination, web application support and feature delivery, and cross-team collaboration to keep both platforms aligned.

This transition coincided with my growing involvement on GetGround itself, consolidating my role as a full-stack developer across shared platform and client-specific systems.

1. Prioritizing mobile stability under migration pressure

The mobile app was a critical user-facing surface. I focused first on ensuring that the React Native application could operate independently from GetGround without regressions.

This involved carefully refactoring dependencies, validating API contracts, and maintaining release stability despite backend changes.

2. Supporting web migration to reduce delivery risk

Once the mobile migration was stabilized, I began actively assisting the web developers.

Rather than operating in silos, we shared responsibility for untangling legacy dependencies, aligning frontend needs with the evolving backend, and reducing bottlenecks by redistributing workload when possible.

This collaborative approach helped keep the migration on track during a highly stressful period.

3. Backend-for-Frontend adaptation

As Wojo moved away from GetGround, a dedicated BFF layer was introduced to bridge Wojo's applications with the backend services.

I contributed to shaping and maintaining this layer, ensuring mobile and web clients could evolve without tight coupling to backend implementation details.

4. Operating under sustained pressure

Beyond technical decisions, the project required resilience under prolonged stress, adaptability as priorities shifted, and consistent communication across distributed teams.

The Covid context amplified these challenges, making clarity and reliability even more critical.

Despite the constraints, the migration was completed successfully:

• Wojo transitioned to an independent technical stack without major service disruptions
• Mobile and web applications remained operational throughout the migration
• Teams adapted to new ownership boundaries and responsibilities
• I evolved from a mobile-focused role into a full-stack contributor through necessity and delivery

The project reinforced the importance of adaptability, teamwork, and calm execution under pressure.

• Mobile: React Native
• Web: Next.js
• Backend: NestJS (Backend-for-Frontend)
• Authentication: AWS Cognito, Auth0/Okta SSO integrations
• Services: Stripe, Firebase, Sentry