Services.

It depends on scope. A focused landing or portfolio site usually takes 1–3 weeks, a corporate site with several pages 2–5 weeks, and e-commerce or custom web applications from one to a few months. I give a concrete estimate after we define the pages and features together.

Yes. I start by auditing what you have — content, SEO signals, what actually works — then rebuild on a modern stack without losing your existing rankings. Redirects and hreflang are part of the job, not an afterthought.

Yes — almost every project I ship includes one. Roles and permissions, fast data tables, content and catalog management, reporting. The panel runs on the same backend as your site or app, so there is no syncing between separate systems.

Yes. I integrate providers like iyzico, PayTR and Stripe, including 3D Secure flows, and build the order and refund screens around them. Which provider fits best depends on your bank, your market and whether you sell abroad — we decide that together.

Nuxt and Vue on the front, TypeScript and Node on the back, PostgreSQL — usually via Supabase — for data. It is the stack I use daily on my own products, so I know exactly how it behaves in production, not just in demos.

Yes — this very site is one. I set up per-language routes, hreflang tags and localized metadata so Google serves the right language to the right audience. Content is written per language, not machine-translated.

Yes. I do technical SEO work on existing sites: structured data, sitemaps, hreflang, indexing cleanup, and Core Web Vitals optimization down to image and font loading. And I will tell you honestly if the bigger problem is content rather than technology.

Wherever fits the project: Vercel, Cloudflare, or the Docker server fleet I run myself. I operate my own production infrastructure with reverse proxies and self-hosted databases, so a fully self-hosted setup is something I already do daily — not a promise.

Yes — assistants that work on your business data, document and photo understanding, and workflow automation. I run OstamAI, a service-workshop management system built around exactly this, so I scope AI features by what actually saves you time, not by what demos well.

Yes, on web technology: installable PWAs and, when the project fits, Capacitor-packaged apps for iOS and Android. Camera, push notifications and offline data all work. I do not write Swift or Kotlin native apps — and if your project truly needs one, I will say so upfront.

For most businesses, a PWA is enough: it installs to the home screen, works offline and sends push notifications — without app-store fees or review cycles. If you need store presence, a Capacitor wrapper takes the same codebase into the App Store and Play Store. True native only pays off for heavy graphics, deep hardware access or platform-specific UX — and that is not what I sell.

Yes — by packaging the web codebase with Capacitor. That covers installation, push notifications, camera access and Play Store submission preparation. One codebase serves Android, iOS and the web, which keeps maintenance realistic for a small team.

I build desktop-style tools: full-screen, keyboard-friendly business applications that run in the browser or on a local network. When the project fits, they can be packaged Electron/Tauri-style to launch like a desktop program. To be clear: I have not shipped store-distributed native desktop software, and I will not pretend otherwise.

Yes — this is a big part of what I do. Inventory and order tracking, booking systems, CRM-like customer tools, reporting screens. I build them when generic software forces your team to work around it instead of with it.

Yes. Supabase is my daily driver — including self-hosted instances on my own servers — and I connect to Firebase or any existing REST/GraphQL API without asking you to migrate. If your current backend is healthy, I build on it rather than replace it.

Yes — that is my default architecture. One backend and one database serve the public website, the installable mobile app and the management panel, so a price updated in the panel is live everywhere instantly. Çiftliğim and OstamAI in my portfolio work exactly this way.

Yes — web push for PWAs and native push through Capacitor builds. One honest caveat: on iOS, web push only works after the user adds the app to their home screen, so if iOS notifications are critical we plan the Capacitor route from the start.

Yes — full-screen, locked-down, single-purpose screens: order terminals, check-in screens, workshop status boards. They run in a browser in kiosk mode or on a local network, restart cleanly after a power cut, and stay usable with a touchscreen alone.