01 / DISCOVERY
I’m Burak Çaparlar. Follow a product through a mobile app—and discover the engineering behind every interaction. Scroll to begin.
02 / LIVE DATA
Pause here: stock moves 12 → 11 → 8, then follows into detail. My Nesine work includes socket-driven live data.
03 / NAVIGATION
The Arc card becomes its detail screen. Visual continuity helps people understand where they came from and where they are.
04 / MEDIA
Play, pause, progress. Media is part of the interface—and its behaviour needs to respect the Android lifecycle.
05 / STATE
Save Arc. Loading, failure, retry, success: explicit state keeps the interface honest while asynchronous work happens.
06 / ARCHITECTURE
The same detail screen separates into UI, state, domain and data. Clear responsibilities make changes easier to reason about.
07 / DATA
Arc’s identity travels from the repository to the API and back. Python backend experience connects both sides of the contract.
08 / RESILIENCE
The network drops. Cached Arc data stays visible; background work can retry when its constraints are met.
09 / NATIVE iOS
Arc continues on iOS. The content stays familiar while navigation and presentation follow the platform. My iOS experience is built with Swift.
10 / HOW I BUILD
Design context becomes a specification. Specialised Claude Code agents build and review; I make the final engineering decisions.
11 / YOUR TURN
The same Arc product is ready in the interactive lab. Open it, change its state and explore both platform perspectives.
The part you touch should feel simple. The thinking behind it goes deeper: state, data, platform behaviour and the decisions that connect them.
Android depth. Swift iOS experience. Interfaces grounded in how people use their phones.
Clear boundaries between presentation, state and data. Python experience beyond the mobile client.
Specialised AI agents, explicit context and independent review. Engineering judgment stays human.
Search. Open a detail. Change the state. A small interaction reveals a lot about how an app is built.
An original browser demo. Fictional products; no company app screens.
Explicit UI state keeps loading, content and failure visible to the interface.
Try the search field or open a product.
data class ScreenState(
val isLoading: Boolean,
val items: List<Product>,
val error: String?
)Scroll to peel back the layers. Or choose one to explore the thinking behind the interface.
Render the state. Keep the interface understandable.
Jetpack Compose · SwiftConsumer apps, banking, quick commerce and telecom. Different contexts; a consistent focus on mobile product engineering.
Complex journeys. Real device behaviour.
Account, membership and verification, payment and deposit, live results and video experiences, including socket-driven live data. Investigation of device-specific crashes and media compatibility across Android versions.
Android / Media / Crash investigationBanking, built in modules.
New features and bug fixes for the Yapı Kredi Mobile banking application. Kotlin and Java on a modular, MVVM-based codebase with Dagger, Flow, Coroutines, Navigation and Retrofit/OkHttp, delivered through Bamboo CI.
Kotlin / Java / Modular architectureEveryday needs, in minutes.
New features and bug fixes for Getir Android applications. Kotlin and Java with Dagger Hilt, Coroutines and Retrofit/OkHttp, VIPER and MVVM, delivered through Bitrise CI.
Kotlin / Hilt / VIPER / MVVMAccount management in every pocket.
New features and bug fixes for the Vodafone Yanımda and İKSV Android applications. Java with Retrofit/OkHttp and MVP/MVC, delivered through Jenkins CI.
Java / MVP / JenkinsThrough LoodosRole-specific agents, custom skills, explicit handoffs and review. Applied AI projects covering retrieval, structured outputs and stateful orchestration.
Explore the systemA Python research platform for systematic strategy testing: pre-registered hypotheses, cost-aware backtesting and independent review with risk checks.
Research stage. No live deployment or performance claim.My Claude Code workflow separates responsibilities. Each agent has its own skills and context. Handoffs are explicit. The final decision stays with me.
Constraints and relevant project information come before implementation.
A local simulation of the process. No AI request is sent.context → scope → implementation → review
Techniques I have used in projects. Open a topic to see what it solves.
Advanced RAG separates retrieval from generation. Re-ranking with Cohere Rerank orders candidate passages by relevance before the selected context reaches the model.
Advanced RAG · Re-ranking · Cohere RerankFunction and tool calling connect model decisions to software. Pydantic and JSON Schema validate output structure; semantic correctness still needs separate checks.
Function calling · Structured Outputs · Pydantic · JSON SchemaSSE streams incremental output to the interface. LLM and context caching can reuse eligible work; the result depends on cache validity and the workload.
SSE · LLM caching · Context cachingLangGraph state management supports multi-step workflows. MCP provides a standard way to expose context and tools, with deliberate tool access and human review.
LangGraph · State management · MCP · Multi-agent workflowsMobile engineering is my centre of gravity. Backend and AI experience expand how I approach the whole system.
Native feature development and platform behaviour.
Reusable components and consistent screen behaviour.
Asynchronous work and observable UI state.
Boundaries, dependency injection, persistence and integrations.
Background tasks, media and device-specific behaviour.
Feature development and debugging; iOS contributions at Metglobal.
Backend experience, automation and systematic research tools.
Role-specific agents with scoped instructions and handoffs.
Project context and design specifications carried into implementation.
Select relevant context before asking the model to generate.
Connect tools and validate the structure of model outputs.
Incremental responses and reuse of eligible context.
State and tool access across multi-step workflows.
Build workflows, version control and release collaboration.
Human review and meaningful checks on generated and handwritten code.
Follow failures across devices, versions and application states.
Mobile development since 2015. Each product adds another perspective on how software reaches people.
Computer Engineering · 2010–2016
Android product engineering
Consumer journeys, media and device behaviour · Remote
Banking technology
Consumer applications
Vodafone Yanımda · IKSV
Python backend · Android · iOS
Get in touch to discuss my projects and engineering work.
[email protected]