ikiliya
Word and puzzle games for two
- Status
- Live on App Store & Google Play
- My role
- Product, design, Flutter client, Cloud Functions backend, store management, SEO site
- Built with
- FlutterFirebaseCloud FunctionsFirestoreRevenueCatNext.js
Istanbul · Türkiye
Cem Vural Yılmaz
Who are you?Pick one and the site rebuilds itself around you.
I don't just write the product. I keep it alive in production.
I build mobile apps end to end with Flutter and Firebase. My code is live on the App Store and Google Play — real users, real payments, real debugging at 2am. If you're wondering what a solo shipper brings to a team: I know how to cut scope, spot risk early, and make done actually mean done.
I build my own products. All of them ship.
From games to AI-assisted tools, I turn the problem that's bugging me into an app. Design, code, store listing, backend and growth — all mine. What's below isn't a pile of experiments; these are real apps that get downloaded and used.
I turn an idea into a live app in the store.
A mobile app from scratch, a feature on an existing one, or rescuing a project that's stuck. Flutter gives you iOS and Android from one codebase; Firebase handles everything behind it. No agency, no middleman — the person you talk to is the person writing the code.
grab me and put me anywhere
- Flutter
- core expertise
- Firebase
- backend + infra
- Shipped
- App Store & Play
- Solo
- design · code · ship
- iOS + Android
- one codebase
- Live
- multiple apps
- End to end
- idea to store
- Direct
- no middleman
- Fixed scope
- clear delivery
scroll
Work
Products in the wild
Every one of these is solo: product, design, code, backend, store.
Coming soon
Up close
What was actually hard in each one?
ikiliya
Word and puzzle games for two
Turn-based word and puzzle games you play against a friend. Several games in one app, with seasonal content, a friend system, leaderboards and in-app purchases.
The hardest part was keeping a real-time multiplayer flow and a server-verified economy standing at the same time. Purchase verification is entirely server-side; the client is never trusted. Daily puzzle content is generated automatically, checked for repetition against the existing corpus, and published.
Highlights
- Server-verified in-app purchases and coin economy
- Seasonal rotation that refreshes content
- Auto-generated daily puzzles with repetition checks
- A marketing site that speaks the app's language, with playable demos
Bulmaca Köşesi
A new puzzle every day
An app built to create a daily puzzle habit. A fresh puzzle each day, streak tracking, and a subscription that unlocks the back catalogue.
The goal isn't a single fun session, it's a daily ritual. So the content calendar, the streak mechanic and archive access sit at the centre of the product. Subscription and ads were designed together — free users still get a complete puzzle experience.
Highlights
- Daily content calendar and streak mechanic
- Puzzle archive unlocked by subscription
- A separate marketing site with an editorial voice
freshIt
Track food expiry from a grocery receipt
Photograph your grocery receipt; the app reads the items, estimates their shelf life and warns you before they spoil. The point is throwing away less food.
Receipt reading uses an AI vision model, but the model's output isn't trusted directly — item matching and shelf-life estimates are verified server-side. A live basket screen you can use in the shop compares your running estimate against the final receipt total.
Highlights
- Item extraction straight from a receipt photo
- Server-verified shelf-life estimation
- Live in-store basket: estimate versus real total
- Scheduled notifications before food spoils
Rüyacı
AI dream interpretation
A journal that interprets the dream you describe and surfaces the symbols and themes that keep coming back over time.
Rather than one-shot interpretation, the aim is depth: finding patterns across your dream history, tracking specific symbols, and a mode that thinks for longer. Cost is kept under control through caching.
Highlights
- Pattern and symbol tracking across dream history
- Cache-driven cost control
- Layered interpretation depth
About
The hard part of shipping an app isn't the code.
Right now
Working on a new planning app and pushing growth on the ones already out there.
The hard part is getting purchase verification to work in production and not just in sandbox, reading a store rejection correctly, figuring out how to reach a user who never granted notification permission, and having someone still open the app three weeks later.
I've been through every one of those. I've set up subscriptions in my own apps, taken an App Store rejection, found the actual cause and fixed it, and read live analytics to work out why retention was dropping. That's why the code I write plans for more than the happy path.
How I work
Three things I'm stubborn about
- 01
Root cause, not a patch
When I see a bug I don't silence the symptom. I dig until I know why it happened, because a patched bug comes back — usually at the worst possible moment.
- 02
Trust the server, never the client
Payments, entitlements, economy: every decision involving money is verified server-side. The client asks; it doesn't decide.
- 03
Done means shipped
Writing the code is half the job. The store listing, the icon, permission strings, the privacy manifest, the review rejection and the analysis afterwards are all part of it.
Contact
Looking for a Flutter engineer on your team?
Happy to send my CV and walk through the technical detail behind any of these products.
Want to ask something, or just say hello?
The products, the process, the tools I use — all fair game.
Got an app in mind?
Tell me what you want to build and we'll work out the scope and a realistic timeline together.