Independent · 2024 — Present
Momena — Marketing Website
Founder & Web Engineer
Designed and built the full marketing website for Momena from scratch — multilingual content (EN/TR/DE), blog infrastructure, SEO, and App Store landing page. No templates, no page builders.
Problem
Momena's iOS app needed a marketing presence that could explain a privacy-first product accurately, rank for the right search terms, and speak to users in their own language across three markets — without relying on a page builder that would compromise performance or make multilingual content unmanageable over time.
Approach
I designed and built momena.app entirely from scratch as a full-stack web product: a Next.js and TypeScript site styled with Tailwind CSS, structured content for English, Turkish, and German audiences, an MDX-based blog for product updates and privacy-focused writing, and an App Store landing page built to convert without gimmicks.
Architecture
The site is built on Next.js with TypeScript throughout, styled with Tailwind CSS, and structured around localized content trees for EN/TR/DE. Blog content is authored in MDX — the same content-as-code approach I use for my own writing — so there's no separate CMS to operate or secure. SEO — metadata, structured data, sitemaps — is treated as a first-class part of the architecture, not bolted on after launch.
Technical Decisions
No templates or page builders
Building the site by hand in Next.js meant slower initial setup than a page builder, but gave full control over performance, structure, and exactly how multilingual content and SEO metadata compose together — control I wasn't willing to trade for a faster first draft.
MDX for blog content, not a separate CMS
Keeping blog posts as MDX in the repository — the same pattern I use for my own writing — meant no CMS to operate or secure, consistent with the same 'no unnecessary backend' philosophy behind Momena the app.
i18n as a structural decision, not a translation layer bolted on
Structuring content trees per locale from the start, rather than retrofitting translation onto an English-only site, avoided the awkward compromises that usually show up in multilingual sites built as an afterthought.
Challenges
- Structuring multilingual content (EN/TR/DE) so translations stay accurate and maintainable without a separate localization platform.
- Building an App Store landing page that converts without resorting to a bloated third-party page builder.
- Keeping SEO fundamentals — metadata, sitemaps, structured data — correct across three languages and a growing blog.
Results
- Shipped momena.app end to end — design, engineering, content, and SEO — as a solo build alongside the iOS app itself.
- Extended the same privacy-first, no-unnecessary-backend philosophy from the app to its own marketing site.
- Established a content and blog infrastructure that scales to new languages and articles without re-architecting.
Lessons learned
- Building the marketing site with the same rigor as the product it markets is worth it — visitors can tell when a landing page was an afterthought.
- Treating i18n as an architecture decision from day one is far cheaper than retrofitting it later.
More projects
All projectsIndependent · 2021 — Present
Momena
A privacy-first consumer app I designed, built, and shipped entirely by myself — from Figma to SwiftUI, CloudKit sync, and weekly AI-powered insights — without operating a traditional backend.
Magnosco · 2023 — Present
Magnosco — Diagnostic Imaging Platform
The iOS application connecting a dermatological imaging device to an on-device CoreML diagnostic pipeline, built in close collaboration with imaging scientists.
Diconium (for Volkswagen Group) · 2018 — 2021
Volkswagen — Connected Owner App
The companion iOS app connecting Volkswagen drivers to their vehicles — remote status, trip data, and configuration — rebuilt module by module inside a large, long-lived, multi-brand codebase.