Apps that solveeveryday problems.
Building products that solve real problems through thoughtful design, intuitive experiences, and reliable engineering. Creating software people genuinely enjoy using.
Products,not projects.
I start with the problem, not the feature list. Every detail in the interface earns its place before it goes live.
FeaturedDavao Commuters
Unsa akong sakyan? Now you'll know.
5K+
Users
46K+
Route Searches
291
Daily Active Users
Also built inside other teams
Maya Business App
Sep 2024 – PresentCore engineering work on the Maya Business mobile app across Flutter and native iOS, including shared architecture, platform capabilities, and cross-team integration across the Maya ecosystem.
Maya
ChatEasy
Aug 2022 – Sep 2024A HIPAA-compliant messaging platform for care teams, built from scratch in Flutter. Secure, real-time collaboration to streamline clinical workflows and patient care.
Theoria Medical
Shapeyou
Mar 2024 – Jul 2024Feature development for ShapeYou, a subscription fitness and nutrition app: workout tracking, nutrition planning, and coaching experiences in Flutter for iOS and Android.
Qonvex
Built alongsidegreat teams.
Eight years of turning problems into products people actually enjoy using, across startups, enterprise software, and fintech.
Currently Software Engineer at Maya.
Detailobsessed
Spacing, motion, copy, edge cases. Nothing goes out unreviewed.
Problemfirst
I solve what's actually broken, features come second.
Designsense
Interfaces that feel obvious and stay accessible.
Engineeringcraft
Architecture, testing, and CI that hold up in production.
Built beyondthe cloud.
My homelab is where ideas become experiments.
It's where I explore infrastructure, automation, networking, AI, and self-hosting before those lessons find their way into the products I build.
Built withintention.
Every product starts with a real problem, not a feature request.
Screens get looked at twice before they're called done.
If it needs an explanation, it isn't obvious enough yet.
Accessibility isn't a checklist, it's the default.
Small details aren't polish, they're the decision.
A feature that doesn't earn its place doesn't make the cut.
Because the problem always comes before the feature.
I build solutions, not just features.
This is how I approach software, not just how I write code.
Let's build somethingworth using.
If you have a real problem to solve, or a product that works but doesn't feel right yet, I'd like to hear about it. I'll sweat the details so you don't have to.