Seeking Growth Partner for NONOX — Android App Locker Built on a Phone
The setup most founders would quit over:
6-inch smartphone. That's my entire dev environment.
AIDE IDE. No Android Studio. No emulator.
Intermittent internet. Sometimes none for days.
Harar, Ethiopia. Not SF. Not Bangalore. Not even Addis Ababa.
Solo. No co-founder. No team. No funding.
What I built anyway:
NONOX — a privacy-first Android app locker that actually works.
24-hour app lock with no workarounds
Complete phone lockdown mode
Real-time app blocking via Accessibility Service
Focus statistics & streak tracking
Survives reboots (Direct Boot, Device Protected Storage)
5.74MB APK. Android 8.0+. Zero cloud dependencies.
The part I'm quietly proud of:
I architected a triple-trigger boot recovery system that locks the phone within 20-30 seconds of restart — on Samsung, with Knox, without root. Most devs with laptops and teams struggle with this. I did it thumbs-only on a screen smaller than most people's second monitor.
Why I'm posting:
I launched on Gumroad 3 weeks ago. $19 lifetime. 0 sales.
The product is solid. The architecture is tight. What I can't do alone — and what I need a partner for — is growth, distribution, and getting this in front of people who need it.
What I'm looking for:
A partner who can own the go-to-market side while I keep shipping product.
Marketing strategy — positioning, messaging, landing page optimization
Distribution — Gumroad SEO, app store presence, affiliate networks, content marketing
Community building — Telegram, TikTok, LinkedIn, Reddit
Sales & pricing experiments — converting visitors to buyers, testing tiers
What I bring:
Deep Android architecture expertise (Java/Kotlin)
Relentless shipping discipline (daily commits, even on 2G)
Product vision and execution
40% affiliate commission structure already built
Async-first workflow — Telegram, email, GitHub. No sync video calls needed.
The constraints (non-negotiable transparency):
I'm in Ethiopia, on intermittent internet, building on a phone
No funding, no salary to offer — equity or revenue-share only
Async communication works best for me
I ship fast, but I can't hop on Zoom at 9am EST
Who this is for:
You've grown a product from 0 to 100 users, or 0 to $1K MRR
You understand bootstrapping and lean validation
You can work async and trust without micromanagement
You believe talent exists everywhere, not just in SF
You want to build something meaningful with a technical co-founder who never stops shipping
The bigger mission:
Talent exists everywhere. Even in Ethiopia. Even on a phone. I'm not asking for charity. I'm asking for a partner who wants to prove that a solo developer with nothing but discipline and a smartphone can build something people pay for — if the right person helps get it seen.
If that partner is you, or if you know someone who fits, drop a comment or reach out directly.
Geda Taye Merga
Building NONOX | @gedatayeofficially on TikTok | Telegram: @NONOX_App | jabataye@gmail.com
Building an Android app entirely on a 6-inch phone with AIDE, no emulator, no Android Studio, and intermittent internet is genuinely impressive. That's not just resourcefulness, it shows you can already ship and problem-solve under real constraints, which is a stronger signal than most polished portfolios with a full dev setup behind them.
On the growth partner side, I'd echo what's already been said here: run it as a defined trial with a metric attached before any long-term commitment, not a title handed out on trust. A locker app lives or dies on activation, does someone actually set their first lock within the first session, so that's the number I'd want a growth partner to move first.
I come from the technical/automation side myself (AI agents, workflow systems, RAG pipelines), not growth specifically, but if you ever need a second technical set of eyes, on the Play Store side, onboarding flow, or just sanity-checking a feature before you ship it from that phone, happy to help out. What's been the hardest part of the dev workflow itself, the tooling, or the lack of an emulator to test against?
Topar, this means a lot — thank you for taking the time to write such a thoughtful response. 🙏
You're right about activation being the real metric. If someone doesn't set their first lock, nothing else matters.
The hardest part of building on a phone? Honestly, the lack of an emulator. I test everything on actual devices, which means every bug means installing, running, debugging, tweaking, repeating — on a 6-inch screen. No logs, no breakpoints, just trial and error.
That said, it's also what made me a better builder. You learn to write cleaner code when you can't afford to waste cycles.
I might take you up on that offer for a second set of eyes. What's the best way to reach you?
Thanks again. 🙌
+1 (361) 332-6512
stackbuilder1228
gmail.com
For an app locker, I'd make the first growth trial painfully concrete: pick one narrow intent like "Android app locker for students" or "block distracting apps during study", ship 3 landing/app-store variants, then measure install rate and first block setup rate. The partner who can move those two numbers is worth a longer commitment; the person who only brings vague awareness probably is not.
This is a great point, John. 🙌
The idea of starting with one clear intent makes a lot of sense — students who want to block distractions while studying feel like a strong first audience. Testing different landing page and app store versions with real user data is something I can definitely execute.
In your experience, which metric should I focus on first: install conversion rate or the percentage of users who actually set up their first block?
Really appreciate your time and insights. 🙏
Growth partner is the single most asked-for role I see from solo technical founders, and the usual way it goes wrong is committing equity to someone before you've seen them actually move a number. Whatever you do, structure the first month as a defined piece of work with a metric attached, not a title. I'm building CoBuildr around exactly that pattern (post the role, someone applies, you run a short trial before committing), it opens in early August, but the advice holds either way: trial first, title later.
This is solid advice — especially "trial first, title later." I've seen too many founders give equity too early and regret it.
A trial-based approach makes sense. If you're building CoBuild around that exact pattern, I'd love to check it out when it opens.
Thanks for taking the time to share this. 🙌
NONOX sounds like a promising utility app, especially because it was built entirely on a phone. The right growth partner could help with Play Store optimization, user acquisition, security-focused content, and partnerships with other practical digital tools.
A useful growth model is to solve one specific problem clearly and build organic traffic around it, similar to focused browser utilities such as this gamepad tester, which helps users quickly check controller buttons, triggers, and analog sticks.
Appreciate this, Michael.
You're right about the growth model — solving one problem clearly and building organic traffic around it is the path I'm on. Play Store optimization, user acquisition, and security-focused content are all on my radar.
The gamepad tester analogy is interesting — focused utilities that do one thing well. That's the direction I'm taking NONOX.
Thanks for the thoughtful feedback. 🙏
This comment was deleted 2 months ago