Title: PixiKids — iOS & Android Parental Control Platform Short description: Designed and enginee...Title: PixiKids — iOS & Android Parental Control Platform Short description: Designed and enginee...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Title:
PixiKids — iOS & Android Parental Control Platform
Short description:
Designed and engineered a cross-platform parental control solution for families, combining screen-time management, application restrictions, activity insights, location features, notifications, and secure cloud synchronization.
Our contribution:
Native iOS and Android engineering, application architecture, backend/API integration, database and cloud design, performance optimization, testing, CI/CD, and store-release engineering.
Services/tags:
Mobile Development · iOS · Android · SwiftUI · Kotlin · Firebase · Backend Development
The visual is excellent for Contra because it immediately communicates real product complexity + mobile engineering.
🧠 GROWTH TIP 06/30: DON’T START WITH WHERE. START WITH THE FEELING.
Most travel apps start with one question: “Where do you want to go?”
That works when the user already knows the answer. But a lot of travel discovery starts earlier, with a much less specific thought: I want to go somewhere, I just don’t know where yet.
That idea became Traveling Up, a travel randomizer concept.
Instead of asking users to work through dozens of filters, the product starts with just three signals:
🌍 how much time they have
🎭 how they want the trip to feel
☀️ what kind of climate they prefer
The destination stays a surprise.
Hypothesis: removing destination selection from the first step could move users faster from vague travel intent to genuine interest in one specific trip.
What I would test:
• Destination first search vs Mood first randomizer
• Randomize start rate
• Destination save rate
• Plan this trip CTR
• Time to first interesting destination
💡 Growth insight: in discovery products, uncertainty is not always friction. Sometimes it is exactly what creates curiosity and moves users toward the next action.
This concept came to me after a particularly inspiring trip. And I think it is the first mobile concept I have created purely for myself, rather than for a client project, in roughly three years.
So this one has a little more freedom, art direction, and product experimentation in it.
06/30 complete.
If you enjoy seeing mobile product experiments like this alongside the growth thinking behind them, follow along. And if this direction resonates, a reaction helps me understand which ideas are worth exploring deeper next.
Darakai is a modern food delivery app concept designed to make discovering restaurants, ordering meals, and tracking deliveries simple, fast, and enjoyable.
The project covers the complete customer journey—from onboarding and restaurant discovery to checkout, real-time tracking, delivery confirmation, and profile management.
Key Features
🍔 Restaurant & food discovery
🔎 Search and category browsing
🏪 Restaurant menus & reviews
🛒 Cart & order management
💳 Multiple payment options
📍 Delivery address management
🚴 Real-time order tracking
⭐ Order rating & feedback
👤 Profile & order history
📱 Cross-platform Flutter-ready experience
Design Focus
A clean and modern UI with strong orange branding, intuitive navigation, clear CTAs, consistent components, and a smooth ordering experience optimized for mobile users.
Project Goal
To create a scalable food delivery experience that connects customers with restaurants while making every step of the ordering process effortless.
The end-to-end journey is mapped thoughtfully, especially the handoff from discovery to tracking and delivery confirmation. The orange accent keeps the dense feature board energetic; I’d use it sparingly on the checkout step to make the primary action even clearer.
I’ve been building SabiFlow for a while, and honestly, the most interesting part of the project isn’t the code.
It's the problem.
Because it's personal.
I've experienced that thing where money comes in and somehow, without you really noticing, it starts disappearing.
Not because you don’t earn enough.
Not necessarily because you're irresponsible either.
Sometimes money simply has no job when it arrives.
And as an engineer, that got me thinking:
What if the problem isn't budgeting? What if the problem is that we’re asking people to make too many good decisions at the exact moment they have the most temptation to make bad ones?
That question became the foundation for SabiFlow.
Instead of telling someone, "You should save 20% of your income," I started thinking about what would happen if the system simply helped assign every inflow a purpose the moment it arrived.
That led me down a rabbit hole.
Funnels.
Automated distribution.
Wallet infrastructure.
Virtual accounts.
User behaviour.
Transaction flows.
KYC.
Compliance.
Even the psychology behind notifications.
And this is probably my favourite part of being both an engineer and a founder.
I don’t just ask:
"How do I build this feature?"
I ask:
"Why does this problem exist, and what kind of system could make dealing with it easier?"
Then the engineer in me comes along and asks:
"Okay… but how do we actually make this work reliably?" 😂
That tension between the founder thinking about the problem and the CTO thinking about the system is probably what I enjoy most about building SabiFlow.
I’m still figuring a lot of it out.
But I'm curious:
What’s a problem you’ve experienced personally that eventually made you want to build something around it?
The framing around “why does this problem exist?” is exactly the kind of product thinking that keeps a financial tool from becoming another dashboard. SabiFlow sounds strongest where the behavioral insight meets the practical system design—especially around notifications and reliable follow-through.