Community · Mobile · Web · Platform
LIVEMauritius · product & mobile
Mobile engineer by background. Product engineer by practice.
I buildthingsI build things for people with real problems, product teams, communities, developers, founders, and sometimes myself.
Apps, systems, tools and experiments, usually somewhere between a real problem, a blank editor and the stubborn need to make it work.
Best on desktop: this hero includes an interactive 3D portrait and richer motion.
Mauritius · In industry since 2012
From mobile,to systems,to products.
I started with small screens.
Then the apps got bigger. The systems around them did too.
Over time, the interesting part stopped being any one framework or platform. It became the whole product: the problem, the architecture, the trade-offs, the people using it, and whether it actually shipped.
I still write the code.
Progression from mobile apps to full products
- 01App
- 02Platform
- 03System
- 04Product
03 / Work
Things that became real
Not everything here is live today. Each one made it past the idea stage: designed, built, tested, and pushed far enough to teach me something real.
This is selected work I can discuss publicly. Some commercial and freelance work stays off the page because of NDAs.
Education · AI · Mobile · Platform
BUILT / NOT LAUNCHEDChildren · Reading · Mobile · Web
DISCONTINUEDBuilt to solve my own problems
The dangerous part of knowing how to code is eventually building your own tools for everything.
Experiments & proofs of concept
Some were quick technical tests. Some are ideas still taking shape. All were useful enough to change how I think about bigger systems.
BeGivr
Medusa AI Shopping
BFF Orchestrator
Some shipped. Some didn't. They all taught me something.
The work behind the work
Side projects show what I choose to build. My career shows what I learned building with teams, deadlines, constraints, long-lived systems and real production users.
Jan 2025 to Present
Senior Mobile Engineer
PlusNarrative
I work primarily on a large React Native application used in time-sensitive field operations. It sits inside a broader operational system, so reliability, location and mapping, offline and local data, complex forms and consistent behaviour across changing backend services matter as much as the UI itself.
My work goes well beyond individual screens. I have worked on feature architecture, local persistence and synchronisation, API integration, reusable mobile patterns, performance, build and release workflows, and the boundaries between the app and multiple backend services. When the right fix lives outside the mobile codebase, I work across that boundary rather than treating mobile as an isolated client.
Alongside product delivery, I have built internal tooling and explored platform patterns that reduce friction for engineering teams. The role has reinforced a way of working I value a lot: understand the operational constraint first, then choose the simplest architecture that can survive real use.
May 2021 to Jan 2025
Technical Lead · Senior Mobile Engineer
Yoyo
I joined Yoyo as a Senior Mobile Engineer and later became Technical Lead, working across native iOS and Android on a long-lived financial-services application.
I stayed hands-on while owning technical direction, mentoring, estimation and delivery. I also helped modernise both platforms, moving from XML toward Jetpack Compose and from storyboards and XIBs toward SwiftUI, without stopping parallel release work.
That role was where responsibility expanded from the code I wrote to how a team learned, coordinated and shipped together.
2019 to 2021
Technical Project Manager · Android Lead · Web & Android Developer
Mobi Move
At Mobi Move I worked across web and mobile before moving into Android leadership and technical project management.
The role mixed implementation with estimates, planning, client communication and delivery. It was also where I got practical opportunities to challenge a native-by-default mindset, using React Native and Flutter for fast internal product experiments.
That period taught me to treat frameworks as choices, not identities.
2012 to 2019
Earlier roles
WiGroup · Esokia · Accenture · Freelance and other engineering work
Android, web, client delivery, production support and changing stacks. Those were the years that taught me how software behaves once other people depend on it.
Career timeline
The full story lives on LinkedIn
View full experience on LinkedIn →For the complete chronology, roles, dates and the longer arc from mobile engineering into product and platform work, LinkedIn has the résumé version.
Different companies. Different products. The recurring job was the same: understand the problem, make sensible trade-offs and ship something people could rely on.
I'm JP.
Still building.
I'm JP, a Mauritius-based engineer building mobile apps, web products, APIs, internal tools and the systems around them since 2012.
I started in Android.
Over time, I became less interested in the boundaries.
Today I'm most useful where product thinking, architecture and hands-on engineering meet: figuring out what should be built, how the pieces should fit together, and then helping build it properly.
I still like being close to the code.
I still start side projects because a problem bothers me.
And I still think shipping something useful teaches you more than talking about building it.
Education
2023 to 2025
MSc Applied Computing and Digital Technologies
Open University of Mauritius · Distinction
2009 to 2013
BSc Computer Science
University of Mauritius
- Mobile engineering
- Product engineering
- System architecture
- Backend & APIs
- Web applications
- Technical leadership
- AI integration
- Developer tooling
Let's build something useful.
If you're working on a product, a difficult technical problem or a system that has outgrown its first version, I'm always happy to talk.
I'm also open to full-time roles where mobile, web and platform engineering sit close to product decisions and long-lived systems.
Based in Mauritius
Working across mobile, web and systems