✓ Personal idea board of
I’m an Application Engineer by profession and an indie developer by passion. whyThough is where I build software inspired by real frustrations and everyday experiences. Each project is an opportunity to solve a meaningful problem while exploring new technologies.
From the workbench
Each one started with a tiny, persistent frustration.
Free, accessible group expense sharing without paywalls, confusing interfaces, or missing essentials.
“Hello, we’re tracking expenses because we’re kinda broke—why are the useful features premium?”
Open project Read case studyAttendance and ministry management that helps children’s church teams spend less time on paperwork and more time serving.
“There’s nothing wrong with pen and paper—but God’s future leaders deserve nothing less than our best.”
Open project Read case studyA preparedness tool designed to put clear CPR guidance within reach when every second matters.
“Set it up today. Hopefully, never use it.”
Visit website Read case studyA privacy-first browser extension that catches duplicate pages and helps you return to the tab that’s already open.
“Why open the same page again when the browser already knows it’s there?”
Visit websiteA browser extension that gives every webpage an independent community discussion layer.
“What if people could compare notes on any page, beyond the website owner’s control?”
Visit websiteThe method behind the mess
I keep a list of everyday problems that frustrate me. Every once in a while, I choose one and build something to solve it.
That’s what whyThough is—creating useful software, one problem at a time.
Tools in the drawer
No allegiances. Just the right tool for the problem.
Keep the ideas moving
If something here helped, amused, or inspired you, your support keeps independent projects brewing.
Support on Ko-fiNo pressure. Looking around is already lovely.
Open line
No polished specification required. A few honest paragraphs are plenty.
Tell me what feels frustrating, slow, or harder than it should be—and who it affects. We can work toward the smallest useful solution from there.
I usually reply within 1–2 business days.
▲
A useful bit of contextDiscussion attached to this webpage