[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"technologies":3,"\u002Fblog\u002Ftelegram-bot-to-app-6-weeks":167,"team-members":745,"blog-topics":1087,"mdc--6coqo3-key":1128,"glossary":1152},[4,10,15,21,26,32,38,43,48,53,58,63,68,73,77,82,87,92,97,103,108,113,118,123,128,133,138,143,147,152,157,162],{"title":5,"description":6,"slug":7,"category":8,"icon":9},"Android","Every app we ship reaches Android — platform APIs, background execution, permissions, and the store requirements that come with them.","android","framework","logos:android-icon",{"title":11,"description":12,"slug":13,"category":8,"icon":14},"Angular","The front-end framework we work in when a product is already Angular — a batteries-included structure that suits large, long-lived apps.","angular","logos:angular-icon",{"title":16,"description":17,"slug":18,"category":19,"icon":20},"Dart","The language every Flutter app we ship is written in — sound null safety, real pattern matching, and a compiler that targets native and the web.","dart","language","logos:dart",{"title":22,"description":23,"slug":24,"category":8,"icon":25},"Django","The Python framework we use when a product needs an admin, auth and a real data model on day one rather than a hand-rolled service.","django","logos:django-icon",{"title":27,"description":28,"slug":29,"category":30,"icon":31},"Docker","Every service we build ships as a container, so what runs on a laptop, in CI and in production is one artefact rather than three of them.","docker","infrastructure","logos:docker-icon",{"title":33,"description":34,"slug":35,"category":36,"icon":37},"Fastlane","The release automation behind our mobile work — signing, builds and store uploads run from CI instead of from one engineer's laptop on release day.","fastlane","tools","logos:fastlane",{"title":39,"description":40,"slug":41,"category":8,"icon":42},"Flutter","Our primary mobile stack since 2018 — one Dart codebase shipping to iOS, Android, web and desktop without a separate team per platform.","flutter","logos:flutter",{"title":44,"description":45,"slug":46,"category":36,"icon":47},"Git","Every project we touch lives in Git — reviewed pull requests, CI on every branch, and a history that still makes sense months later.","git","logos:git-icon",{"title":49,"description":50,"slug":51,"category":19,"icon":52},"Go","Our backend language for real-time APIs and services under load — small binaries, fast builds, and concurrency that stays readable.","go","logos:gopher",{"title":54,"description":55,"slug":56,"category":30,"icon":57},"Google Cloud","The cloud our production workloads run on — managed Kubernetes, storage and networking, without hand-built servers nobody wants to maintain.","gcp","logos:google-cloud",{"title":59,"description":60,"slug":61,"category":36,"icon":62},"Gradle","The build system every Android release goes through — product flavours, signing configs, and the dependency wiring under a Flutter app.","gradle","logos:gradle",{"title":64,"description":65,"slug":66,"category":30,"icon":67},"Helm","How we package a Kubernetes deployment — service, config, secrets and ingress as one versioned unit that can be promoted and rolled back.","helm","logos:helm",{"title":69,"description":70,"slug":71,"category":19,"icon":72},"Kotlin","What we reach for when a Flutter app needs real Android underneath it — platform channels, background work, and native SDK integrations.","kotlin","logos:kotlin-icon",{"title":74,"description":75,"slug":76,"category":8,"icon":72},"Kotlin Multiplatform","Sharing business logic across iOS and Android while each platform keeps its own native UI — the alternative when Flutter is not the right fit.","kmp",{"title":78,"description":79,"slug":80,"category":30,"icon":81},"Kubernetes","How we run services in production — Helm-packaged deployments, rollouts that can be rolled back, and scaling that does not need a person at 3am.","kubernetes","logos:kubernetes",{"title":83,"description":84,"slug":85,"category":30,"icon":86},"NATS","Lightweight messaging between services — publish\u002Fsubscribe and request\u002Freply without the operational weight of a full broker cluster.","nats","logos:nats-icon",{"title":88,"description":89,"slug":90,"category":8,"icon":91},"Nuxt","Vue with server rendering, routing and SEO handled — how we build marketing sites and web apps that must be fast and indexable on first load.","nuxt","logos:nuxt-icon",{"title":93,"description":94,"slug":95,"category":19,"icon":96},"PHP","Where we work with an existing PHP backend — extending it, integrating with it, and building the mobile and web clients it has to serve.","php","logos:php",{"title":98,"description":99,"slug":100,"category":101,"icon":102},"PostgreSQL","Our default database — the one we reach for unless a product gives us a specific reason not to, from schema design through to index tuning.","postgres","database","logos:postgresql",{"title":104,"description":105,"slug":106,"category":19,"icon":107},"Python","Our language for backends, data work and AI integrations — including the Python bindings we ship for our own Rust tooling.","python","logos:python",{"title":109,"description":110,"slug":111,"category":8,"icon":112},"React","The front-end library we work in when a product is already React — components, hooks, and the ecosystem that has grown around them.","react","logos:react",{"title":114,"description":115,"slug":116,"category":101,"icon":117},"Redis","Where we put data that has to be fast and can be rebuilt — caches, sessions, rate limits, and the queues behind a product's slow paths.","redis","logos:redis",{"title":119,"description":120,"slug":121,"category":19,"icon":122},"Ruby","The language our mobile release automation is written in — Fastlane lanes, custom actions, and the CI glue that ships builds to the stores.","ruby","logos:ruby",{"title":124,"description":125,"slug":126,"category":19,"icon":127},"Rust","Where we go when performance and correctness both matter — document rendering, CLI tooling, and services that have to stay fast and predictable.","rust","simple-icons:rust",{"title":129,"description":130,"slug":131,"category":101,"icon":132},"SQLite","The database that ships inside the app — local caches, offline-first storage, and anything that still has to work with no network.","sqlite","logos:sqlite",{"title":134,"description":135,"slug":136,"category":8,"icon":137},"Strapi","A headless CMS we reach for when editors need to own the content — a real admin and a clean API, without building either from scratch.","strapi","logos:strapi-icon",{"title":139,"description":140,"slug":141,"category":19,"icon":142},"Swift","What we reach for when a Flutter app needs real iOS underneath it — platform channels, native SDK integrations, widgets and App Clips.","swift","logos:swift",{"title":144,"description":145,"slug":146,"category":8,"icon":142},"SwiftUI","Apple's UI framework, where we build the native surfaces a Flutter app cannot own — widgets, App Clips, extensions and system integrations.","swiftui",{"title":148,"description":149,"slug":150,"category":8,"icon":151},"Tailwind CSS","How we style every front end we build — utility classes and design tokens instead of a stylesheet that only ever grows and is never deleted.","tailwind","logos:tailwindcss-icon",{"title":153,"description":154,"slug":155,"category":19,"icon":156},"TypeScript","The default for everything we write for the browser and for Node services — types that catch integration bugs before they reach a review.","typescript","logos:typescript-icon",{"title":158,"description":159,"slug":160,"category":8,"icon":161},"Vue","Our front-end framework for admin panels, merchant dashboards and product web apps that have to stay maintainable for years, not sprints.","vue","logos:vue",{"title":163,"description":164,"slug":165,"category":36,"icon":166},"Whisper","OpenAI's open-source speech recognition model — the transcription engine behind voice input, running as both a backend service and on-device in the app.","whisper","simple-icons:openai",{"id":168,"title":169,"author":170,"body":171,"description":726,"extension":727,"hero":728,"meta":731,"metaDescription":732,"metaTitle":733,"navigation":734,"ogDescription":735,"path":736,"seo":737,"slug":738,"stem":739,"summary":740,"timestamp":741,"topic":742,"updated":743,"__hash__":744},"blog_en\u002Fblog\u002Ftelegram-bot-to-app-6-weeks.md","You Have a Telegram Bot With 50k Users — Here's How to Ship It as an App in 6 Weeks","masha",{"type":172,"value":173,"toc":708},"minimark",[174,188,196,199,204,215,230,236,243,259,261,265,272,275,292,295,327,337,339,343,346,353,358,366,369,389,392,396,399,406,409,447,451,454,483,486,490,497,531,535,538,544,547,549,553,556,583,586,588,592,595,630,633,635,639,658,665,667,671,685,688,692,700],[175,176,177,181,182,187],"p",{},[178,179,180],"strong",{},"TL;DR."," A Telegram bot with a real user base and a backend behind it can become a shipped iOS and Android app in about six weeks — not because the work is trivial, but because the hard product question (does anyone want this?) is already answered. This post is the week-by-week plan: what gets built when, where the six weeks actually go, how you migrate 50,000 users without losing them, and the specific things that turn six weeks into four months. If you want to self-qualify first, the ",[183,184,186],"a",{"href":185},"\u002Fservices\u002Fchatbot-to-app","chatbot-to-app service page"," has a readiness checklist.",[175,189,190,191,195],{},"If you just want the schedule, jump to ",[183,192,194],{"href":193},"#the-six-week-plan-week-by-week","the six-week plan",".",[197,198],"hr",{},[200,201,203],"h2",{"id":202},"the-setup","The setup",[175,205,206,207,195],{},"Picture the position you're in — it's a good one. You launched a Telegram bot a year or two ago to test an idea. It worked. You now have 50,000 users who open it, use it, and occasionally pay for it. The bot does something real: a fitness coach, an AI assistant, a finance tracker, a language tutor, a marketplace — the category doesn't matter for this post. What matters is that you have ",[178,208,209,214],{},[210,211,213],"term",{"slug":212},"product-market-fit","product-market fit"," on a platform you don't own",[175,216,217,218,224,225,229],{},"And the platform is starting to hurt. Users ask for things the bot can't do. You can't send a push notification without it landing in a muted channel. You can't charge the way you want to. A ",[183,219,223],{"href":220,"rel":221},"https:\u002F\u002Fcore.telegram.org\u002Fbots\u002Fapi",[222],"nofollow","Telegram Bot API"," change broke a flow last quarter and you spent a weekend firefighting. You're successful ",[226,227,228],"em",{},"despite"," the platform, and you can feel the ceiling.",[175,231,232,233],{},"So you want an app. The question every founder in this position asks is the same: ",[226,234,235],{},"how long, and how do we not lose the 50k users we already have?",[175,237,238,239,242],{},"The honest answer for a large class of bots is ",[178,240,241],{},"six weeks to a launched app",", plus a gradual migration that runs in parallel and finishes when you decide it's done. Here's why that number is realistic, and exactly where the time goes.",[244,245,246],"blockquote",{},[175,247,248,249,253,254,258],{},"The walkthrough below is a composite — it's the plan we've run, in pieces, across real chat-heavy Flutter builds like ",[183,250,252],{"href":251},"\u002Fportfolio\u002Farcana","Arcana"," (a streaming AI chat client shipped in three weeks) and ",[183,255,257],{"href":256},"\u002Fportfolio\u002Fyoumi","YouMi"," (a real-time messaging app we stabilized in two). No single client is \"the 50k bot,\" but every step here is something we've actually done.",[197,260],{},[200,262,264],{"id":263},"why-six-weeks-is-realistic-and-when-it-isnt","Why six weeks is realistic (and when it isn't)",[175,266,267,268,271],{},"Six weeks sounds aggressive until you remember what you're ",[226,269,270],{},"not"," doing.",[175,273,274],{},"You're not discovering the product. You're not running user research to figure out what to build — your bot is two years of user research. You're not designing a novel interaction model — the conversational flow already works and you're going to keep most of it. You're not validating demand — 50,000 people already validated it.",[175,276,277,278,281,282,286,287,291],{},"What's left is ",[178,279,280],{},"execution against a known specification",", and that's the part that compresses. A single ",[183,283,39],{"href":284,"rel":285},"https:\u002F\u002Fflutter.dev",[222]," codebase ships to both iOS and Android at once (we've written about ",[183,288,290],{"href":289},"\u002Fblog\u002Fflutter-vs-react-native-2026","why one codebase beats two native builds","), so you're not paying for the same work twice. The backend mostly exists. The feature list is finite and already battle-tested in production.",[175,293,294],{},"Six weeks is realistic when:",[296,297,298,306,313,320],"ul",{},[299,300,301,302,305],"li",{},"Your bot already talks to a ",[178,303,304],{},"backend API",", not just Telegram's servers.",[299,307,308,309,312],{},"The feature set is ",[178,310,311],{},"chat-centric plus a handful of screens"," — not a sprawling super-app.",[299,314,315,316,319],{},"You have ",[178,317,318],{},"one decision-maker"," who can approve designs and scope without a committee.",[299,321,322,323,326],{},"You're willing to launch a focused v1 and add the long tail ",[226,324,325],{},"after"," the app is live.",[175,328,329,330,332,333,195],{},"Six weeks is ",[226,331,270],{}," realistic when the bot has no separate backend and all logic lives inside bot handlers (add 2–3 weeks to extract an API), when you need a from-scratch custom design system, or when \"parity\" secretly means fifty edge-case commands that each need their own screen. We'll come back to these in ",[183,334,336],{"href":335},"#what-turns-six-weeks-into-four-months","what blows the timeline",[197,338],{},[200,340,342],{"id":341},"the-six-week-plan-week-by-week","The six-week plan, week by week",[175,344,345],{},"Here's the schedule we run. The weeks overlap more than this linear list suggests — design starts while the audit finishes, store paperwork starts on day one — but the critical path looks like this.",[347,348],"how-to-schema",{":description":349,":name":350,":steps":351,":total-time":352},"A week-by-week plan for migrating a Telegram bot with an existing backend to a standalone iOS and Android app.","How to Ship a Telegram Bot as an App in 6 Weeks","[{\"name\": \"Week 1 — Audit and feature mapping\", \"text\": \"Document every command, flow, and integration, then sort features into keep-as-chat, promote-to-screen, and cut-from-v1 buckets to lock the scope.\"}, {\"name\": \"Week 2 — Architecture and the API\", \"text\": \"Design the client around the existing backend API and settle real-time messaging and push notifications. If no backend exists, extract a thin API layer first.\"}, {\"name\": \"Weeks 3 and 4 — Build the core\", \"text\": \"Build the chat interface, authentication mapped to existing users, the promoted screens, and end-to-end push notifications, with an installable demo build every week.\"}, {\"name\": \"Week 5 — Migration plumbing and store prep\", \"text\": \"Wire up account linking, submit to the App Store and Google Play, and add an in-bot announcement with deep links.\"}, {\"name\": \"Week 6 — Launch and gradual migration\", \"text\": \"Launch the app without shutting off the bot, then move users across over time with deep links and app-only features.\"}]","P6W",[354,355,357],"h3",{"id":356},"week-1-audit-and-feature-mapping","Week 1 — Audit and feature mapping",[175,359,360,361,365],{},"We go through the bot command by command, flow by flow, and write down everything it does. Every ",[362,363,364],"code",{},"\u002Fcommand",", every inline keyboard, every multi-step conversation, every integration, every payment path. This becomes the specification, and it's the single most important artifact in the whole project.",[175,367,368],{},"Then we map each bot capability to its app equivalent and sort it into three buckets:",[296,370,371,377,383],{},[299,372,373,376],{},[178,374,375],{},"Keep as chat."," The conversational core stays conversational — that's what your users know.",[299,378,379,382],{},[178,380,381],{},"Promote to a screen."," Things you crammed into chat because the bot forced you to (settings, history, dashboards, profiles) become real screens.",[299,384,385,388],{},[178,386,387],{},"Cut from v1."," The commands 2% of users touch. They go on the post-launch list, not the critical path.",[175,390,391],{},"That third bucket is where six weeks is won or lost. The output of week one is a signed-off scope: a specific list of what ships in v1.",[354,393,395],{"id":394},"week-2-architecture-and-the-api-question","Week 2 — Architecture and the API question",[175,397,398],{},"The app needs to talk to a backend. The best case is that your bot already does, and the app simply calls the same endpoints. We design the client architecture around your existing API — auth, data models, real-time channels — with no backend rewrite.",[175,400,401,402,405],{},"If your bot has ",[178,403,404],{},"no separate backend"," (all logic inside Telegram handlers), this is where we extract a thin API layer so both the bot and the app can share it. That's the one situation that legitimately adds time, and we flag it on day one rather than discovering it in week four.",[175,407,408],{},"This week also nails down the two subsystems that quietly sink chat apps:",[296,410,411,429],{},[299,412,413,416,417,422,423,425,426,195],{},[178,414,415],{},"Real-time messaging"," — proper ",[183,418,421],{"href":419,"rel":420},"https:\u002F\u002Fdeveloper.mozilla.org\u002Fen-US\u002Fdocs\u002FWeb\u002FAPI\u002FWebSockets_API",[222],"WebSocket"," lifecycle: reconnection, message queuing, state sync. Getting this wrong is exactly what we were called in to fix on ",[183,424,257],{"href":256},", where users were dropping mid-conversation. It's unglamorous and it's the difference between an app that works and one that works ",[226,427,428],{},"when nothing goes wrong",[299,430,431,434,435,440,441,446],{},[178,432,433],{},"Push notifications"," — ",[183,436,439],{"href":437,"rel":438},"https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fusernotifications",[222],"APNs"," and ",[183,442,445],{"href":443,"rel":444},"https:\u002F\u002Ffirebase.google.com\u002Fdocs\u002Fcloud-messaging",[222],"FCM"," wired up early, because notifications are half the reason you're leaving Telegram.",[354,448,450],{"id":449},"weeks-34-build-the-core","Weeks 3–4 — Build the core",[175,452,453],{},"This is the heaviest stretch: the actual app. In a single Flutter codebase, the team builds:",[296,455,456,466,472,478],{},[299,457,458,459,462,463,465],{},"The ",[178,460,461],{},"chat interface"," — smooth scrolling over thousands of messages, rich media, streaming responses if your bot is AI-backed (the incremental-Markdown rendering we built for ",[183,464,252],{"href":251}," lives here).",[299,467,468,471],{},[178,469,470],{},"Authentication"," — phone, email, or social login, mapped to your existing user identities so accounts carry over.",[299,473,458,474,477],{},[178,475,476],{},"promoted screens"," from week one — dashboards, history, settings, profiles.",[299,479,480,482],{},[178,481,433],{}," end to end, on your schedule and your terms.",[175,484,485],{},"You get a demo build at the end of each week. Not a status email — an installable build on a real device. This is non-negotiable: weekly builds are how scope creep gets caught while it's cheap to fix.",[354,487,489],{"id":488},"week-5-migration-plumbing-and-store-prep","Week 5 — Migration plumbing and store prep",[175,491,492,493,496],{},"Now the part unique to ",[226,494,495],{},"migrating"," rather than building fresh. Three things run in parallel:",[296,498,499,510,522],{},[299,500,501,504,505,509],{},[178,502,503],{},"Account linking."," A user opens the app and proves they're the same person who used the bot — usually a one-tap ",[210,506,508],{"slug":507},"deep-linking","deep link"," from the bot carrying a signed token, or a phone\u002Femail match. Their history and data come with them.",[299,511,512,515,516,521],{},[178,513,514],{},"Store submission."," App Store and Google Play listings, screenshots, privacy declarations, review submission. ",[183,517,520],{"href":518,"rel":519},"https:\u002F\u002Fdeveloper.apple.com\u002Fapp-store\u002Freview\u002Fguidelines\u002F",[222],"Apple's review queue"," is the one external dependency you can't fully control, which is why this starts now, not in week six.",[299,523,524,527,528,195],{},[178,525,526],{},"The in-bot bridge."," The bot itself becomes your best acquisition channel. We add an announcement flow and deep links so the 50k users hear about the app ",[226,529,530],{},"inside the tool they already open every day",[354,532,534],{"id":533},"week-6-launch-and-the-start-of-migration","Week 6 — Launch and the start of migration",[175,536,537],{},"The app goes live. But \"launch\" doesn't mean a hard cutover — and this is the part founders worry about most, so let's be precise.",[175,539,540,543],{},[178,541,542],{},"You do not shut the bot off."," The bot keeps running. On launch day it starts nudging users toward the app with a deep link, but anyone who ignores it keeps using the bot exactly as before. Nobody is locked out, nothing breaks, and your 50k users don't churn because of a forced migration.",[175,545,546],{},"Migration becomes a dial you turn over the following weeks: a banner, then a softer prompt, then app-only features that pull people across on their own. Many products keep a permanently simplified bot as a second entry point. You decide the pace; the app being live on day one is what week six delivers.",[197,548],{},[200,550,552],{"id":551},"how-you-dont-lose-50000-users","How you don't lose 50,000 users",[175,554,555],{},"This deserves its own section because it's the real fear, and the mechanics are straightforward once you see them.",[557,558,559,565,571,577],"ol",{},[299,560,561,564],{},[178,562,563],{},"Parallel running, not a cutover."," Bot and app coexist. There is never a moment where a user's only option is \"download the app or lose access.\"",[299,566,567,570],{},[178,568,569],{},"The bot is the migration channel."," You're not buying ads to find these users — they're already talking to you every day. A deep link in the bot converts far better than any cold install campaign, and it's free.",[299,572,573,576],{},[178,574,575],{},"Accounts and history carry over."," Deep-link tokens or phone\u002Femail matching mean a user signs in and finds their data already there. The app feels like an upgrade, not a fresh start.",[299,578,579,582],{},[178,580,581],{},"Gradual incentives, not force."," App-only features, better notifications, and a nicer experience pull users across. Pushing them with a hard deadline pushes some of them out entirely.",[175,584,585],{},"Done this way, migration isn't a risky event — it's a curve you control, and the bot stays as a safety net the whole time.",[197,587],{},[200,589,591],{"id":590},"what-turns-six-weeks-into-four-months","What turns six weeks into four months",[175,593,594],{},"Honesty about the failure modes, because they're predictable:",[296,596,597,603,609,615,621],{},[299,598,599,602],{},[178,600,601],{},"No backend to talk to."," If every bit of logic lives inside Telegram handlers with no API, extracting one adds 2–3 weeks. Worth doing — it's the foundation everything else stands on — but it's real time.",[299,604,605,608],{},[178,606,607],{},"\"Parity\" means everything."," Insisting v1 ship all 60 commands, including the ones 2% of users touch, is the most common timeline killer. Ship the core, add the tail after launch.",[299,610,611,614],{},[178,612,613],{},"Design from a blank page."," A bespoke design system invented during the build adds weeks. A clean, conventional design applied to a known flow does not.",[299,616,617,620],{},[178,618,619],{},"Decision-by-committee."," Six weeks assumes someone can approve a screen the day they see it. If every decision waits a week for a meeting, the calendar — not the engineering — sets the pace.",[299,622,623,626,627,629],{},[178,624,625],{},"A rescue, not a build."," If there's an existing half-finished app that's breaking, fixing inherited problems is a different job than starting clean — that's the ",[183,628,257],{"href":256}," situation, and it's scoped separately.",[175,631,632],{},"None of these are mysteries. We surface them in week one, which is the entire point of starting with an audit instead of a Gantt chart.",[197,634],{},[200,636,638],{"id":637},"what-it-costs","What it costs",[175,640,641,642,649,650,652,653,657],{},"A straightforward migration on this timeline — core features preserved, chat interface, auth, push notifications, store deployment, and user migration — lands in the ",[178,643,644],{},[645,646],"service-price",{"format":647,"service":648},"full","chatbot-to-app\u002Fsimple"," range over four to six weeks. Feature-rich bots with payments, offline support, and custom screens run higher and longer; AI-backed bots with streaming and real-time rendering higher still. The full breakdown by tier is on the ",[183,651,186],{"href":185},", and the ",[183,654,656],{"href":655},"\u002Fblog\u002Fflutter-app-development-cost-2026","cost framework"," explains how scope compounds into the final number.",[175,659,660,661,664],{},"The thing worth internalizing: the expensive part of building an app is finding product-market fit, and ",[178,662,663],{},"you already paid that bill"," with your bot. The migration is the cheap part. You're converting validated demand into a product you own — and that's a far better starting position than the founder staring at a blank Figma file, guessing what to build.",[197,666],{},[200,668,670],{"id":669},"frequently-asked-questions","Frequently asked questions",[672,673,675],"questions",{":items":674},"[{\"title\":\"How long does it take to turn a Telegram bot into a mobile app?\",\"text\":\"A straightforward bot with a working backend can ship as an iOS and Android app in about six weeks. Feature-rich bots with payments, offline support, or AI streaming typically take two to four months. The timeline depends mostly on whether the bot already has a separate backend API and how much of the feature set must ship in version one.\"},{\"title\":\"Will I lose my users when I migrate from the bot to the app?\",\"text\":\"Not if you migrate gradually. The bot keeps running alongside the app, so no user is ever locked out. The bot itself becomes the migration channel: a deep link inside it converts far better than paid ads, and accounts plus history carry over, so the app feels like an upgrade rather than a fresh start.\"},{\"title\":\"Do I need to rebuild my backend to launch the app?\",\"text\":\"Usually not. If your bot already talks to a backend API, the app calls the same endpoints with no rewrite. Only when all logic lives inside Telegram handlers with no separate backend do you need to extract a thin API layer first, which adds about two to three weeks.\"},{\"title\":\"How much does it cost to convert a Telegram bot into an app?\",\"slot\":\"cost\",\"text\":\"A straightforward migration with core features, chat, authentication, push notifications, and store deployment lands around 5,000 to 10,000 US dollars. Feature-rich and AI-backed bots cost more. Because the bot already proved demand, the most expensive part of building an app is already paid for.\"},{\"title\":\"Can the Telegram bot keep running after the app launches?\",\"text\":\"Yes. Most products keep a simplified bot running permanently as a second entry point. Launch is not a hard cutover: the bot nudges users toward the app over time while staying fully functional for anyone who has not switched yet.\"},{\"title\":\"Why build the app with Flutter?\",\"text\":\"Flutter ships to iOS and Android from a single codebase, which cuts time and cost by roughly 30 to 40 percent versus two native builds, with no performance penalty. It is especially strong for chat-heavy apps that need smooth scrolling, real-time updates, and rich media rendering.\"}]",[676,677,679],"template",{"v-slot:cost_body":678},"",[175,680,681,682,684],{},"A straightforward migration with core features, chat, authentication, push notifications, and store deployment lands around ",[645,683],{"format":647,"service":648},". Feature-rich and AI-backed bots cost more. Because the bot already proved demand, the most expensive part of building an app is already paid for.",[175,686,687],{},"::",[200,689,691],{"id":690},"start-with-the-checklist","Start with the checklist",[175,693,694,695,699],{},"Before a single line of code, run your bot through the ",[183,696,698],{"href":697},"\u002Fservices\u002Fchatbot-to-app#bot-to-app-migration-readiness-checklist","migration readiness checklist"," on the service page. It tells you, honestly, how close to a clean six-week migration you actually are — and where the gaps will cost you time.",[175,701,702,703,707],{},"If you've got a bot with real users and you're feeling the platform ceiling, ",[183,704,706],{"href":705},"\u002Fcontact","book a discovery call",". We'll walk your bot through the audit, tell you which weeks will be easy and which will be hard, and give you a fixed-scope quote — not a guess.",{"title":678,"searchDepth":709,"depth":709,"links":710},2,[711,712,713,721,722,723,724,725],{"id":202,"depth":709,"text":203},{"id":263,"depth":709,"text":264},{"id":341,"depth":709,"text":342,"children":714},[715,717,718,719,720],{"id":356,"depth":716,"text":357},3,{"id":394,"depth":716,"text":395},{"id":449,"depth":716,"text":450},{"id":488,"depth":716,"text":489},{"id":533,"depth":716,"text":534},{"id":551,"depth":709,"text":552},{"id":590,"depth":709,"text":591},{"id":637,"depth":709,"text":638},{"id":669,"depth":709,"text":670},{"id":690,"depth":709,"text":691},"TL;DR. A Telegram bot with a real user base and a backend behind it can become a shipped iOS and Android app in about six weeks — not because the work is trivial, but because the hard product question (does anyone want this?) is already answered. This post is the week-by-week plan: what gets built when, where the six weeks actually go, how you migrate 50,000 users without losing them, and the specific things that turn six weeks into four months. If you want to self-qualify first, the chatbot-to-app service page has a readiness checklist.","md",{"type":729,"src":730},"image","\u002Fblog\u002Ftelegram-bot-to-app-6-weeks.webp",{},"A week-by-week plan for turning a Telegram bot into a standalone iOS and Android app — where the 6 weeks go, and what blows the timeline.","Turn a Telegram Bot Into an App in 6 Weeks",true,"50k people already use your bot. The week-by-week plan to put it on the App Store in six weeks, and what usually blows the timeline.","\u002Fblog\u002Ftelegram-bot-to-app-6-weeks",{"title":169,"description":726},"telegram-bot-to-app-6-weeks","blog\u002Ftelegram-bot-to-app-6-weeks","A week-by-week migration plan for turning a Telegram bot into a standalone iOS and Android app — what happens each week, where the 6 weeks actually go, and what blows the timeline.","2026-06-02T08:50:12Z","for-founders",null,"vudly5NxsIETbkixxb1AQUskRxqUzmqMl2X52WvP7-0",[746,803,849,899,989,1041],{"id":747,"bio":748,"expertise":753,"extension":769,"links":770,"meta":774,"metaDescription":775,"name":780,"ogDescription":783,"photo":788,"role":789,"seniority":794,"skills":795,"slug":796,"specialization":797,"stem":796,"__hash__":802},"team_members\u002Fdima.yaml",{"en":749,"ru":750,"es":751,"nl":752},"Dima has been building with [Flutter](\u002Ftechnologies\u002Fflutter) since 2021, and specializes in :term[state management]{slug=\"state-management\"} and app architecture.\n\nHe has hands-on experience with real-time communication protocols — :term{slug=\"webrtc\"} for audio and video, and :term{slug=\"xmpp\"} for messaging — which makes him comfortable with the network-heavy, stateful features many teams struggle to get right.\n","Дима работает с [Flutter](\u002Ftechnologies\u002Fflutter) с 2021 года и специализируется на :term[state management]{slug=\"state-management\"} и архитектуре приложений.\n\nУ него есть практический опыт с протоколами реального времени — :term{slug=\"webrtc\"} для аудио и видео и :term{slug=\"xmpp\"} для обмена сообщениями, — поэтому ему близки сетевые stateful-фичи, которые многим командам даются с трудом.\n","Dima trabaja con [Flutter](\u002Ftechnologies\u002Fflutter) desde 2021 y se especializa en :term[gestión de estado]{slug=\"state-management\"} y arquitectura de aplicaciones.\n\nTiene experiencia práctica con protocolos de comunicación en tiempo real —:term{slug=\"webrtc\"} para audio y vídeo, y :term{slug=\"xmpp\"} para mensajería—, lo que le hace sentirse cómodo con esas funcionalidades con mucho estado y mucha red que a muchos equipos se les atragantan.\n","Dima werkt sinds 2021 met [Flutter](\u002Ftechnologies\u002Fflutter) en is gespecialiseerd in :term[state management]{slug=\"state-management\"} en applicatiearchitectuur.\n\nHij heeft praktijkervaring met protocollen voor realtime communicatie — :term{slug=\"webrtc\"} voor audio en video, en :term{slug=\"xmpp\"} voor berichten — waardoor hij zich thuis voelt bij de netwerkzware functies met veel staat waar veel teams moeite mee hebben.\n",[754,757,762,764],{"en":755,"ru":755,"es":756,"nl":755},"State management","Gestión de estado",{"en":758,"ru":759,"es":760,"nl":761},"Application architecture","Архитектура приложений","Arquitectura de aplicaciones","Applicatiearchitectuur",{"en":763,"ru":763,"es":763,"nl":763},"WebRTC",{"en":765,"ru":766,"es":767,"nl":768},"XMPP messaging","Обмен сообщениями по XMPP","Mensajería XMPP","Berichten via XMPP","yaml",[771],{"type":772,"address":773},"email","konopatov@nerdy.pro",{},{"en":776,"ru":777,"es":778,"nl":779},"Lead Flutter developer at Nerdy Production, building real-time apps since 2021 — state management, app architecture, WebRTC and XMPP.","Ведущий Flutter-разработчик Nerdy Production: приложения реального времени с 2021 года — state management, архитектура, WebRTC и XMPP.","Lead de desarrollo Flutter en Nerdy Production, construyendo apps en tiempo real desde 2021: gestión de estado, arquitectura de aplicaciones, WebRTC y XMPP.","Lead Flutter-developer bij Nerdy Production, bouwt sinds 2021 realtime-apps — state management, applicatiearchitectuur, WebRTC en XMPP.",{"en":781,"ru":782,"es":781,"nl":781},"Dima","Дима",{"en":784,"ru":785,"es":786,"nl":787},"Lead Flutter developer at Nerdy Production — real-time apps since 2021, and the state management that keeps them from falling over.","Ведущий Flutter-разработчик Nerdy Production: приложения реального времени с 2021 года и state management, на котором они держатся.","Lead de desarrollo Flutter en Nerdy Production: apps en tiempo real desde 2021 y la gestión de estado que evita que se caigan.","Lead Flutter-developer bij Nerdy Production — realtime-apps sinds 2021, en het state management dat ze overeind houdt.","\u002Fteam\u002Fdima.webp",{"en":790,"ru":791,"es":792,"nl":793},"Lead Flutter Developer","Ведущий Flutter-разработчик","Lead de desarrollo Flutter","Lead Flutter-developer","lead",[41,18,155,160,90,111,150,95],"dima",{"en":798,"ru":799,"es":800,"nl":801},"Real-time apps, state management, and architecture","Приложения реального времени, state management и архитектура","Apps en tiempo real, gestión de estado y arquitectura","Realtime-apps, state management en architectuur","1TuxUt3zjdVkQUvMf9dBITG872C0exrdZyyoKw1beiE",{"id":804,"bio":805,"expertise":810,"extension":769,"links":743,"meta":821,"metaDescription":822,"name":827,"ogDescription":830,"photo":835,"role":836,"seniority":841,"skills":842,"slug":170,"specialization":843,"stem":170,"__hash__":848},"team_members\u002Fmasha.yaml",{"en":806,"ru":807,"es":808,"nl":809},"Masha builds [Flutter](\u002Ftechnologies\u002Fflutter) apps where design and copy are treated as one job.\n\nShe specializes in UI\u002FUX — turning product requirements into clean, usable interfaces — and in the writing inside the app, from onboarding flows to the microcopy that makes a screen make sense. The result is apps that feel considered, not just functional.\n","Маша делает приложения на [Flutter](\u002Ftechnologies\u002Fflutter), где дизайн и текст — одна задача.\n\nОна специализируется на UI\u002FUX, превращая продуктовые требования в чистые и удобные интерфейсы, и на текстах внутри приложения — от онбординга до микрокопирайта, который делает экран понятным. В итоге приложения получаются продуманными, а не просто рабочими.\n","Masha crea apps en [Flutter](\u002Ftechnologies\u002Fflutter) donde el diseño y el texto se tratan como un mismo trabajo.\n\nSe especializa en UI\u002FUX —convertir requisitos de producto en interfaces limpias y usables— y en la escritura dentro de la app, desde los flujos de onboarding hasta el microcopy que hace que una pantalla se entienda. El resultado son apps que se sienten pensadas, no solo funcionales.\n","Masha bouwt [Flutter](\u002Ftechnologies\u002Fflutter)-apps waarin ontwerp en tekst als één taak worden behandeld.\n\nZe is gespecialiseerd in UI\u002FUX — productwensen omzetten in heldere, bruikbare interfaces — en in de teksten binnen de app, van onboarding tot de microteksten die een scherm begrijpelijk maken. Het resultaat zijn apps die doordacht aanvoelen en niet alleen werken.\n",[811,816],{"en":812,"ru":813,"es":814,"nl":815},"UI\u002FUX design","UI\u002FUX-дизайн","Diseño UI\u002FUX","UI\u002FUX-ontwerp",{"en":817,"ru":818,"es":819,"nl":820},"Product copywriting","Продуктовый копирайтинг","Redacción de producto","Productteksten",{},{"en":823,"ru":824,"es":825,"nl":826},"Flutter developer at Nerdy Production working where design meets copy — UI\u002FUX, onboarding flows, and the microcopy that makes a screen make sense.","Flutter-разработчик Nerdy Production на стыке дизайна и текста: UI\u002FUX, онбординг и микрокопирайт, который делает экран понятным.","Desarrolladora Flutter en Nerdy Production, donde el diseño se encuentra con el texto: UI\u002FUX, onboarding y el microcopy que hace que una pantalla se entienda.","Flutter-developer bij Nerdy Production op het snijvlak van ontwerp en tekst — UI\u002FUX, onboarding, en de microteksten die een scherm begrijpelijk maken.",{"en":828,"ru":829,"es":828,"nl":828},"Masha","Маша",{"en":831,"ru":832,"es":833,"nl":834},"Flutter developer at Nerdy Production working where design meets copy — onboarding flows and the microcopy that makes a screen make sense.","Flutter-разработчик Nerdy Production на стыке дизайна и текста: онбординг и микрокопирайт, который делает экран понятным.","Desarrolladora Flutter en Nerdy Production, donde el diseño se encuentra con el texto: onboarding y el microcopy que hace entender una pantalla.","Flutter-developer bij Nerdy Production op het snijvlak van ontwerp en tekst — onboarding en de microteksten die een scherm begrijpelijk maken.","\u002Fteam\u002Fmasha.webp",{"en":837,"ru":838,"es":839,"nl":840},"Flutter Developer","Flutter-разработчик","Desarrolladora Flutter","Flutter-developer","middle",[41,18],{"en":844,"ru":845,"es":846,"nl":847},"UI\u002FUX and copywriting for Flutter apps","UI\u002FUX и копирайтинг для Flutter-приложений","UI\u002FUX y redacción para apps Flutter","UI\u002FUX en teksten voor Flutter-apps","z3c64iWR39RIrn8wE0elSy00IfCITYgNkbgp_G_sslk",{"id":850,"bio":851,"expertise":856,"extension":769,"links":867,"meta":870,"metaDescription":871,"name":876,"ogDescription":879,"photo":884,"role":885,"seniority":890,"skills":891,"slug":892,"specialization":893,"stem":892,"__hash__":898},"team_members\u002Fmaxim.yaml",{"en":852,"ru":853,"es":854,"nl":855},"Maxim is a polyglot engineer who moves comfortably across [Go](\u002Ftechnologies\u002Fgo), [Flutter](\u002Ftechnologies\u002Fflutter), [Python](\u002Ftechnologies\u002Fpython), and [TypeScript](\u002Ftechnologies\u002Ftypescript), which lets him own a feature from the backend to the screen.\n\nHe came up at Ozon, one of Russia's largest marketplaces, where scale makes reliability non-negotiable — and it shows in his work: testing is a first-class part of how he builds, not an afterthought bolted on at the end.\n","Максим — полиглот-инженер, свободно работающий с [Go](\u002Ftechnologies\u002Fgo), [Flutter](\u002Ftechnologies\u002Fflutter), [Python](\u002Ftechnologies\u002Fpython) и [TypeScript](\u002Ftechnologies\u002Ftypescript), что позволяет ему вести фичу от бэкенда до экрана.\n\nОн вырос в Ozon, одном из крупнейших маркетплейсов России, где масштаб делает надёжность обязательной, — и это видно в его работе: тестирование для него первоклассная часть разработки, а не то, что прикручивают в конце.\n","Maxim es un ingeniero políglota que se mueve con soltura entre [Go](\u002Ftechnologies\u002Fgo), [Flutter](\u002Ftechnologies\u002Fflutter), [Python](\u002Ftechnologies\u002Fpython) y [TypeScript](\u002Ftechnologies\u002Ftypescript), lo que le permite hacerse cargo de una funcionalidad desde el backend hasta la pantalla.\n\nSe formó en Ozon, uno de los mayores marketplaces de Rusia, donde la escala hace que la fiabilidad no sea negociable, y se le nota: el testing es para él una parte de primera clase de cómo construye, no un añadido al final.\n","Maxim is een polyglotte engineer die zich moeiteloos beweegt tussen [Go](\u002Ftechnologies\u002Fgo), [Flutter](\u002Ftechnologies\u002Fflutter), [Python](\u002Ftechnologies\u002Fpython) en [TypeScript](\u002Ftechnologies\u002Ftypescript), waardoor hij een functie van de backend tot het scherm kan dragen.\n\nHij is opgegroeid bij Ozon, een van de grootste marktplaatsen van Rusland, waar schaal betrouwbaarheid onderhandelbaar maakt noch toestaat — en dat zie je terug in zijn werk: testen is bij hem een volwaardig onderdeel van hoe hij bouwt, geen bijzaak die er aan het eind bij komt.\n",[857,862],{"en":858,"ru":859,"es":860,"nl":861},"Automated testing","Автоматизированное тестирование","Testing automatizado","Geautomatiseerd testen",{"en":863,"ru":864,"es":865,"nl":866},"High-load backend systems","Высоконагруженные бэкенд-системы","Sistemas backend de alta carga","Backendsystemen met hoge belasting",[868],{"type":772,"address":869},"maxim@nerdy.pro",{},{"en":872,"ru":873,"es":874,"nl":875},"Senior engineer at Nerdy Production across Go, Flutter, Python and TypeScript — from backend to screen, with automated testing built in.","Старший инженер Nerdy Production: Go, Flutter, Python и TypeScript — от бэкенда до экрана, с автотестами как частью разработки.","Ingeniero senior en Nerdy Production con Go, Flutter, Python y TypeScript: del backend a la pantalla, con testing automatizado incorporado.","Senior engineer bij Nerdy Production met Go, Flutter, Python en TypeScript — van backend tot scherm, met geautomatiseerd testen ingebouwd.",{"en":877,"ru":878,"es":877,"nl":877},"Maxim","Максим",{"en":880,"ru":881,"es":882,"nl":883},"Senior engineer at Nerdy Production working from backend to screen — Go, Flutter, Python and TypeScript, with the tests written as he goes.","Старший инженер Nerdy Production, работающий от бэкенда до экрана: Go, Flutter, Python и TypeScript — и тесты, которые пишутся по ходу дела.","Ingeniero senior en Nerdy Production, del backend a la pantalla: Go, Flutter, Python y TypeScript, con los tests escritos sobre la marcha.","Senior engineer bij Nerdy Production, van backend tot scherm — Go, Flutter, Python en TypeScript, met de tests die hij onderweg schrijft.","\u002Fteam\u002Fmax.webp",{"en":886,"ru":887,"es":888,"nl":889},"Senior Software Engineer","Старший инженер-программист","Ingeniero de software senior","Senior software engineer","senior",[41,18,51,106,155,13,150],"maxim",{"en":894,"ru":895,"es":896,"nl":897},"Backend and Flutter engineering with a testing focus","Бэкенд и Flutter с фокусом на тестирование","Ingeniería backend y Flutter con foco en testing","Backend- en Flutter-engineering met focus op testen","a-8Kx1i-PQXIGU92_Rimqr3bPEur6ZwMfPKQWr2uk4I",{"id":900,"bio":901,"expertise":906,"extension":769,"links":948,"meta":960,"metaDescription":961,"name":966,"ogDescription":969,"photo":974,"role":975,"seniority":980,"skills":981,"slug":982,"specialization":983,"stem":982,"__hash__":988},"team_members\u002Fnixan.yaml",{"en":902,"ru":903,"es":904,"nl":905},"Ilya founded Nerdy Production and leads its engineering. He has been building software since 2010 and shipping production Flutter since 2018.\n\nBefore that he was CTO of QIWI, one of Russia's largest payment platforms, where he ran roughly 12 engineering teams spanning web products down to card processing, :term{slug=\"pci-dss\"} scope, and contactless payments — including building contactless card payments on Android via :term[Host Card Emulation]{slug=\"host-card-emulation\"} over ISO\u002FIEC 14443, with EMV Contactless (Visa PayWave) on top.\n\nHe was also a principal developer at Yandex, where he worked on Yandex.Auto — taking native Android deep into the vehicle, with heavy CAN-bus integration through a custom CAN shield — and a principal at Evotor, whose point-of-sale devices run on a forked :term{slug=\"aosp\"}, giving him a low-level view of Android most app developers never touch.\n\nToday he leads delivery on the agency's flagship apps — from the chart-heavy fintech UI of [ExtraETF](\u002Fportfolio\u002Fextraetf) to the fully custom design system of [Arcana](\u002Fportfolio\u002Farcana). He writes most of the essays on this blog and maintains the agency's open-source work, including the [dxpdf](\u002Fopen-source\u002Fdxpdf) DOCX-to-PDF engine.\n\nHe works across [Flutter](\u002Ftechnologies\u002Fflutter), native iOS and Android, [Go](\u002Ftechnologies\u002Fgo), [Rust](\u002Ftechnologies\u002Frust), [TypeScript](\u002Ftechnologies\u002Ftypescript), [Kotlin](\u002Ftechnologies\u002Fkotlin), [Kubernetes](\u002Ftechnologies\u002Fkubernetes), and [Docker](\u002Ftechnologies\u002Fdocker), with a focus on app architecture, cross-platform delivery, and building teams that ship.\n","Илья основал Nerdy Production и руководит инженерной командой. Он занимается разработкой с 2010 года и выпускает продакшн-приложения на Flutter с 2018-го.\n\nДо этого он был CTO QIWI — одной из крупнейших платёжных платформ России, — где руководил примерно 12 инженерными командами: от веб-продуктов до карточного процессинга, зоны :term{slug=\"pci-dss\"} и бесконтактных платежей, включая бесконтактную оплату картой на Android через :term[Host Card Emulation]{slug=\"host-card-emulation\"} поверх ISO\u002FIEC 14443, с платёжным протоколом EMV Contactless (Visa PayWave).\n\nОн также был принципал-разработчиком в Яндексе, где работал над Яндекс.Авто, уводя нативный Android глубоко в автомобиль, с серьёзной интеграцией по шине CAN через собственный CAN-шилд, и принципалом в Эвоторе, чьи кассовые устройства работают на форке :term{slug=\"aosp\"}, что дало ему низкоуровневый взгляд на Android, недоступный большинству прикладных разработчиков.\n\nСейчас он ведёт поставку флагманских приложений агентства — от насыщенного графиками финтех-интерфейса [ExtraETF](\u002Fportfolio\u002Fextraetf) до полностью кастомной дизайн-системы [Arcana](\u002Fportfolio\u002Farcana). Он пишет большую часть материалов этого блога и поддерживает open-source агентства, включая движок [dxpdf](\u002Fopen-source\u002Fdxpdf) для конвертации DOCX в PDF.\n\nРаботает с [Flutter](\u002Ftechnologies\u002Fflutter), нативными iOS и Android, [Go](\u002Ftechnologies\u002Fgo), [Rust](\u002Ftechnologies\u002Frust), [TypeScript](\u002Ftechnologies\u002Ftypescript), [Kotlin](\u002Ftechnologies\u002Fkotlin), [Kubernetes](\u002Ftechnologies\u002Fkubernetes) и [Docker](\u002Ftechnologies\u002Fdocker); его фокус — архитектура приложений, кросс-платформенная поставка и построение команд, которые доводят продукт до релиза.\n","Ilya fundó Nerdy Production y dirige su ingeniería. Lleva construyendo software desde 2010 y entregando Flutter en producción desde 2018.\n\nAntes fue CTO de QIWI, una de las mayores plataformas de pago de Rusia, donde dirigió alrededor de 12 equipos de ingeniería que abarcaban desde productos web hasta procesamiento de tarjetas, alcance :term{slug=\"pci-dss\"} y pagos contactless, incluida la construcción de pagos contactless con tarjeta en Android mediante :term[Host Card Emulation]{slug=\"host-card-emulation\"} sobre ISO\u002FIEC 14443, con EMV Contactless (Visa PayWave) por encima.\n\nTambién fue principal developer en Yandex, donde trabajó en Yandex.Auto —llevando Android nativo hasta el interior del vehículo, con una integración intensiva por bus CAN a través de un CAN shield propio— y principal en Evotor, cuyos terminales de punto de venta funcionan sobre un fork de :term{slug=\"aosp\"}, lo que le dio una visión de bajo nivel de Android que la mayoría de desarrolladores de apps nunca llega a tocar.\n\nHoy lidera la entrega de las apps insignia de la agencia, desde la interfaz fintech cargada de gráficos de [ExtraETF](\u002Fportfolio\u002Fextraetf) hasta el sistema de diseño totalmente a medida de [Arcana](\u002Fportfolio\u002Farcana). Escribe la mayoría de los artículos de este blog y mantiene el trabajo de código abierto de la agencia, incluido el motor de conversión de DOCX a PDF [dxpdf](\u002Fopen-source\u002Fdxpdf).\n\nTrabaja con [Flutter](\u002Ftechnologies\u002Fflutter), iOS y Android nativos, [Go](\u002Ftechnologies\u002Fgo), [Rust](\u002Ftechnologies\u002Frust), [TypeScript](\u002Ftechnologies\u002Ftypescript), [Kotlin](\u002Ftechnologies\u002Fkotlin), [Kubernetes](\u002Ftechnologies\u002Fkubernetes) y [Docker](\u002Ftechnologies\u002Fdocker), con foco en arquitectura de aplicaciones, entrega multiplataforma y la construcción de equipos que entregan.\n","Ilya richtte Nerdy Production op en leidt de engineering. Hij bouwt software sinds 2010 en levert sinds 2018 Flutter in productie.\n\nDaarvoor was hij CTO van QIWI, een van de grootste betaalplatforms van Rusland, waar hij zo'n 12 engineeringteams aanstuurde die reikten van webproducten tot kaartverwerking, :term{slug=\"pci-dss\"}-scope en contactloos betalen — waaronder het bouwen van contactloze kaartbetalingen op Android via :term[Host Card Emulation]{slug=\"host-card-emulation\"} over ISO\u002FIEC 14443, met EMV Contactless (Visa PayWave) daarbovenop.\n\nHij was ook principal developer bij Yandex, waar hij aan Yandex.Auto werkte — native Android diep de auto in brengen, met zware integratie over de CAN-bus via een eigen CAN-shield — en principal bij Evotor, waarvan de kassa-apparaten op een fork van :term{slug=\"aosp\"} draaien, wat hem een blik op Android op laag niveau gaf die de meeste app-ontwikkelaars nooit krijgen.\n\nVandaag leidt hij de oplevering van de vlaggenschipapps van het bureau — van de grafiekzware fintech-UI van [ExtraETF](\u002Fportfolio\u002Fextraetf) tot het volledig eigen designsysteem van [Arcana](\u002Fportfolio\u002Farcana). Hij schrijft de meeste artikelen op deze blog en onderhoudt het opensourcewerk van het bureau, waaronder de DOCX-naar-PDF-motor [dxpdf](\u002Fopen-source\u002Fdxpdf).\n\nHij werkt met [Flutter](\u002Ftechnologies\u002Fflutter), native iOS en Android, [Go](\u002Ftechnologies\u002Fgo), [Rust](\u002Ftechnologies\u002Frust), [TypeScript](\u002Ftechnologies\u002Ftypescript), [Kotlin](\u002Ftechnologies\u002Fkotlin), [Kubernetes](\u002Ftechnologies\u002Fkubernetes) en [Docker](\u002Ftechnologies\u002Fdocker), met de nadruk op applicatiearchitectuur, cross-platform oplevering en het bouwen van teams die opleveren.\n",[907,912,917,922,927,932,937,942,944,946],{"en":908,"ru":909,"es":910,"nl":911},"iOS development","Разработка под iOS","Desarrollo iOS","iOS-ontwikkeling",{"en":913,"ru":914,"es":915,"nl":916},"Software architecture","Архитектура ПО","Arquitectura de software","Softwarearchitectuur",{"en":918,"ru":919,"es":920,"nl":921},"Engineering team leadership","Руководство инженерными командами","Liderazgo de equipos de ingeniería","Leidinggeven aan engineeringteams",{"en":923,"ru":924,"es":925,"nl":926},"Payment systems","Платёжные системы","Sistemas de pago","Betaalsystemen",{"en":928,"ru":929,"es":930,"nl":931},"Card processing","Карточный процессинг","Procesamiento de tarjetas","Kaartverwerking",{"en":933,"ru":934,"es":935,"nl":936},"PCI-DSS compliance","Соответствие PCI-DSS","Cumplimiento de PCI-DSS","Naleving van PCI-DSS",{"en":938,"ru":939,"es":940,"nl":941},"NFC and contactless payments","NFC и бесконтактные платежи","NFC y pagos contactless","NFC en contactloos betalen",{"en":943,"ru":943,"es":943,"nl":943},"Host Card Emulation",{"en":945,"ru":945,"es":945,"nl":945},"EMV Contactless",{"en":947,"ru":947,"es":947,"nl":947},"AOSP",[949,952,955,958],{"type":950,"url":951},"github","https:\u002F\u002Fgithub.com\u002Fthenixan",{"type":953,"url":954},"linkedin","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fthenixan\u002F",{"type":956,"url":957},"telegram","https:\u002F\u002Ft.me\u002Fthenixan",{"type":772,"address":959},"nixan@nerdy.pro",{},{"en":962,"ru":963,"es":964,"nl":965},"Founder and lead developer at Nerdy Production, former CTO of QIWI. Flutter architecture, payments infrastructure, and engineering teams that ship.","Основатель и ведущий разработчик Nerdy Production, экс-CTO QIWI. Архитектура на Flutter, платёжная инфраструктура и команды, которые доводят до релиза.","Fundador y lead developer en Nerdy Production, ex-CTO de QIWI. Arquitectura Flutter, infraestructura de pagos y equipos de ingeniería que entregan.","Oprichter en lead developer bij Nerdy Production, oud-CTO van QIWI. Flutter-architectuur, betaalinfrastructuur en teams die opleveren.",{"en":967,"ru":968,"es":967,"nl":967},"Ilya Nixan","Илья Никсан",{"en":970,"ru":971,"es":972,"nl":973},"Founder and lead developer at Nerdy Production, former CTO of QIWI — Flutter architecture, payments infrastructure, and teams that ship.","Основатель и ведущий разработчик Nerdy Production, экс-CTO QIWI: архитектура на Flutter, платёжная инфраструктура и команды, которые доводят до релиза.","Fundador y lead developer en Nerdy Production, ex-CTO de QIWI: arquitectura Flutter, infraestructura de pagos y equipos que entregan.","Oprichter en lead developer bij Nerdy Production, oud-CTO van QIWI — Flutter-architectuur, betaalinfrastructuur en teams die opleveren.","\u002Fteam\u002Fnixan.webp",{"en":976,"ru":977,"es":978,"nl":979},"Founder & Lead Developer","Основатель и ведущий разработчик","Fundador y lead developer","Oprichter & lead developer","founder_lead",[41,18,71,141,76,146,51,126,121,155,160,90,13,150,136,7,29,80],"nixan",{"en":984,"ru":985,"es":986,"nl":987},"Flutter architecture and leading delivery teams","Архитектура на Flutter и руководство командами поставки","Arquitectura Flutter y liderazgo de equipos de entrega","Flutter-architectuur en het leiden van opleverteams","BmeQZ7JyhRFIx8527WO2t1-WklP8AAvevAxiN9U4TEs",{"id":990,"bio":991,"expertise":996,"extension":769,"links":1008,"meta":1013,"metaDescription":1014,"name":1019,"ogDescription":1022,"photo":1027,"role":1028,"seniority":890,"skills":1033,"slug":1034,"specialization":1035,"stem":1034,"__hash__":1040},"team_members\u002Froma.yaml",{"en":992,"ru":993,"es":994,"nl":995},"Roman works across native iOS and Android and [Flutter](\u002Ftechnologies\u002Fflutter), and pairs that mobile depth with [Python](\u002Ftechnologies\u002Fpython) and applied AI.\n\nMuch of his background is in ERP and CRM development — complex, data-heavy business systems where getting the domain model right matters more than the UI — which gives him a pragmatic eye for how an app fits the process behind it.\n","Роман работает с нативными iOS и Android и с [Flutter](\u002Ftechnologies\u002Fflutter), дополняя мобильную экспертизу [Python](\u002Ftechnologies\u002Fpython) и прикладным AI.\n\nЗначительная часть его опыта — разработка ERP и CRM, сложных систем с большим объёмом данных, где правильная доменная модель важнее интерфейса, — что даёт ему прагматичный взгляд на то, как приложение встраивается в процесс за ним.\n","Roman trabaja con iOS y Android nativos y con [Flutter](\u002Ftechnologies\u002Fflutter), y combina esa profundidad móvil con [Python](\u002Ftechnologies\u002Fpython) e IA aplicada.\n\nBuena parte de su trayectoria está en el desarrollo de ERP y CRM —sistemas de negocio complejos y con mucho dato, donde acertar con el modelo de dominio importa más que la interfaz—, lo que le da una mirada pragmática sobre cómo encaja una app en el proceso que hay detrás.\n","Roman werkt met native iOS en Android en met [Flutter](\u002Ftechnologies\u002Fflutter), en combineert die mobiele diepgang met [Python](\u002Ftechnologies\u002Fpython) en toegepaste AI.\n\nEen groot deel van zijn achtergrond ligt in ERP- en CRM-ontwikkeling — complexe, datazware bedrijfssystemen waarin het domeinmodel goed krijgen zwaarder weegt dan de interface — wat hem een pragmatische blik geeft op hoe een app in het proces erachter past.\n",[997,998,1003],{"en":908,"ru":909,"es":910,"nl":911},{"en":999,"ru":1000,"es":1001,"nl":1002},"Applied AI","Прикладной AI","IA aplicada","Toegepaste AI",{"en":1004,"ru":1005,"es":1006,"nl":1007},"ERP and CRM systems","ERP- и CRM-системы","Sistemas ERP y CRM","ERP- en CRM-systemen",[1009,1011],{"type":953,"url":1010},"https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fromanbatler\u002F",{"type":772,"address":1012},"roma@nerdy.pro",{},{"en":1015,"ru":1016,"es":1017,"nl":1018},"Senior mobile developer at Nerdy Production — native iOS and Android, Flutter, applied AI, and a background in data-heavy ERP and CRM systems.","Старший мобильный разработчик Nerdy Production: нативные iOS и Android, Flutter, прикладной AI и опыт в ERP- и CRM-системах.","Desarrollador móvil senior en Nerdy Production: iOS y Android nativos, Flutter, IA aplicada y experiencia en sistemas ERP y CRM con gran volumen de datos.","Senior mobiele developer bij Nerdy Production — native iOS en Android, Flutter, toegepaste AI, en een achtergrond in datazware ERP- en CRM-systemen.",{"en":1020,"ru":1021,"es":1020,"nl":1020},"Roman","Рома",{"en":1023,"ru":1024,"es":1025,"nl":1026},"Senior mobile developer at Nerdy Production — native iOS and Android, Flutter, applied AI, and years of data-heavy ERP and CRM behind him.","Старший мобильный разработчик Nerdy Production: нативные iOS и Android, Flutter, прикладной AI и годы работы с нагруженными ERP и CRM.","Desarrollador móvil senior en Nerdy Production: iOS y Android nativos, Flutter, IA aplicada y años de ERP y CRM con mucha carga de datos.","Senior mobiele developer bij Nerdy Production — native iOS en Android, Flutter, toegepaste AI, en jaren datazware ERP en CRM achter zich.","\u002Fteam\u002Froma.webp",{"en":1029,"ru":1030,"es":1031,"nl":1032},"Senior Mobile Developer","Старший мобильный разработчик","Desarrollador móvil senior","Senior mobiele developer",[7,41,18,141,146,106],"roma",{"en":1036,"ru":1037,"es":1038,"nl":1039},"Mobile, AI, and ERP\u002FCRM systems","Мобильная разработка, AI и системы ERP\u002FCRM","Móvil, IA y sistemas ERP\u002FCRM","Mobiel, AI en ERP\u002FCRM-systemen","caPSPO2BX35G9lEjNb6p3U4uF_V7yh8cexCe6l5hm8Y",{"id":1042,"bio":1043,"expertise":1048,"extension":769,"links":743,"meta":1059,"metaDescription":1060,"name":1065,"ogDescription":1068,"photo":1073,"role":1074,"seniority":890,"skills":1079,"slug":1080,"specialization":1081,"stem":1080,"__hash__":1086},"team_members\u002Fxsox.yaml",{"en":1044,"ru":1045,"es":1046,"nl":1047},"Eugene builds the systems that apps depend on. His background is in backend engineering — designing and running the APIs, data models, and services behind a product, primarily in [Python](\u002Ftechnologies\u002Fpython) and [Django](\u002Ftechnologies\u002Fdjango).\n\nHe also works in [Flutter](\u002Ftechnologies\u002Fflutter), so he can reason about a feature from the database to the device and build the backend so the app that consumes it stays simple.\n","Женя строит системы, на которые опираются приложения. Его основной опыт — бэкенд-инженерия: проектирование и эксплуатация API, моделей данных и сервисов за продуктом, в первую очередь на [Python](\u002Ftechnologies\u002Fpython) и [Django](\u002Ftechnologies\u002Fdjango).\n\nОн также работает с [Flutter](\u002Ftechnologies\u002Fflutter), поэтому может рассуждать о фиче от базы данных до устройства и строить бэкенд так, чтобы потребляющее его приложение оставалось простым.\n","Eugene construye los sistemas de los que dependen las apps. Su trayectoria está en la ingeniería backend: diseñar y operar las APIs, los modelos de datos y los servicios que hay detrás de un producto, principalmente en [Python](\u002Ftechnologies\u002Fpython) y [Django](\u002Ftechnologies\u002Fdjango).\n\nTambién trabaja con [Flutter](\u002Ftechnologies\u002Fflutter), así que puede razonar sobre una funcionalidad desde la base de datos hasta el dispositivo y construir el backend de forma que la app que lo consume siga siendo simple.\n","Eugene bouwt de systemen waar apps op leunen. Zijn achtergrond ligt in backend-engineering: de API's, datamodellen en services achter een product ontwerpen en draaien, vooral in [Python](\u002Ftechnologies\u002Fpython) en [Django](\u002Ftechnologies\u002Fdjango).\n\nHij werkt daarnaast met [Flutter](\u002Ftechnologies\u002Fflutter), zodat hij over een functie kan nadenken van de database tot het toestel en de backend zo kan bouwen dat de app die hem verbruikt eenvoudig blijft.\n",[1049,1054],{"en":1050,"ru":1051,"es":1052,"nl":1053},"API design","Проектирование API","Diseño de APIs","API-ontwerp",{"en":1055,"ru":1056,"es":1057,"nl":1058},"Data modelling","Моделирование данных","Modelado de datos","Datamodellering",{},{"en":1061,"ru":1062,"es":1063,"nl":1064},"Senior backend developer at Nerdy Production building the APIs, data models and services behind our apps, primarily in Python and Django.","Старший бэкенд-разработчик Nerdy Production: API, модели данных и сервисы за нашими приложениями, в первую очередь на Python и Django.","Desarrollador backend senior en Nerdy Production: las APIs, modelos de datos y servicios detrás de nuestras apps, sobre todo en Python y Django.","Senior backenddeveloper bij Nerdy Production die de API's, datamodellen en services achter onze apps bouwt, vooral in Python en Django.",{"en":1066,"ru":1067,"es":1066,"nl":1066},"Eugene Xsox","Женя Xsox",{"en":1069,"ru":1070,"es":1071,"nl":1072},"Senior backend developer at Nerdy Production — the APIs, data models and services our apps run on, mostly in Python and Django.","Старший бэкенд-разработчик Nerdy Production: API, модели данных и сервисы, на которых работают наши приложения, в основном на Python и Django.","Desarrollador backend senior en Nerdy Production: las APIs, modelos de datos y servicios sobre los que corren nuestras apps, en Python y Django.","Senior backenddeveloper bij Nerdy Production — de API's, datamodellen en services waarop onze apps draaien, vooral in Python en Django.","\u002Fteam\u002Fxsox.webp",{"en":1075,"ru":1076,"es":1077,"nl":1078},"Senior Backend Developer","Старший бэкенд-разработчик","Desarrollador backend senior","Senior backenddeveloper",[106,24,41,18,155,160,90,150],"xsox",{"en":1082,"ru":1083,"es":1084,"nl":1085},"Python\u002FDjango backends, plus Flutter","Бэкенды на Python\u002FDjango и Flutter","Backends en Python\u002FDjango, además de Flutter","Backends in Python\u002FDjango, plus Flutter","w_QAKKq_Mh_dtMvAxFpAJBC10PW1I7zgVOxELwRHwO8",[1088,1097,1104,1109,1118],{"id":1089,"extension":769,"meta":1090,"name":1091,"slug":1095,"stem":1095,"__hash__":1096},"blog_topics\u002Fcybersecurity.yaml",{},{"en":1092,"ru":1093,"es":1094,"nl":1092},"Cybersecurity","Кибербезопасность","Ciberseguridad","cybersecurity","kt1rdsMy5W4b9MvGHm6mZVCr0inHidEuqaosPYmmk4E",{"id":1098,"extension":769,"meta":1099,"name":1100,"slug":1102,"stem":1102,"__hash__":1103},"blog_topics\u002Fdevops.yaml",{},{"en":1101,"ru":1101,"es":1101,"nl":1101},"DevOps","devops","D3mxlZuFHKCGeszKZuWCiQmHmP5EiCvzg1qEAIQhnyU",{"id":1105,"extension":769,"meta":1106,"name":1107,"slug":41,"stem":41,"__hash__":1108},"blog_topics\u002Fflutter.yaml",{},{"en":39,"ru":39,"es":39,"nl":39},"OOeALAmwFuEqByuJvTGk4g15FIHENPfYMdpfZh_HTAE",{"id":1110,"extension":769,"meta":1111,"name":1112,"slug":742,"stem":742,"__hash__":1117},"blog_topics\u002Ffor-founders.yaml",{},{"en":1113,"ru":1114,"es":1115,"nl":1116},"For Founders","Для основателей","Para fundadores","Voor oprichters","lp2u6Ol2qF4DGxpB83HxbbGzWioT-e40mJhD4lr28-U",{"id":1119,"extension":769,"meta":1120,"name":1121,"slug":1126,"stem":1126,"__hash__":1127},"blog_topics\u002Fsoftware-engineering.yaml",{},{"en":1122,"ru":1123,"es":1124,"nl":1125},"Software Engineering","Разработка ПО","Ingeniería de software","Software-engineering","software-engineering","aZMb3aUDptoFQk_cEE6l5H4wrYcgZuBYUubmKqOAaaU",{"data":1129,"body":1130},{},{"type":1131,"children":1132},"root",[1133,1147],{"type":1134,"tag":175,"props":1135,"children":1136},"element",{},[1137,1140,1145],{"type":1138,"value":1139},"text","Masha builds ",{"type":1134,"tag":183,"props":1141,"children":1143},{"href":1142},"\u002Ftechnologies\u002Fflutter",[1144],{"type":1138,"value":39},{"type":1138,"value":1146}," apps where design and copy are treated as one job.",{"type":1134,"tag":175,"props":1148,"children":1149},{},[1150],{"type":1138,"value":1151},"She specializes in UI\u002FUX — turning product requirements into clean, usable interfaces — and in the writing inside the app, from onboarding flows to the microcopy that makes a screen make sense. The result is apps that feel considered, not just functional.",[1153,1167,1179,1194,1208,1222,1238,1250,1264,1277,1291,1304,1320,1333,1350,1363,1374,1384,1397,1407,1418,1432,1441,1454,1467,1474,1485,1497,1508,1523,1535,1548,1560,1572,1584,1596,1607,1618,1629,1640,1652,1662,1673,1686,1698,1707,1719,1731,1741,1752,1765,1773,1784],{"slug":1154,"term":947,"definition":1155,"category":1156,"aliases":1157,"links":1159,"related":1163,"readMore":-1,"target":1165,"hasArticle":1166},"aosp","The Android Open Source Project — Android without the Google layer on top, which anyone may fork. Point-of-sale terminals, kiosks and in-car systems run on forks of it, and working at that level exposes parts of the OS an app developer never sees.","platform",[1158],"Android Open Source Project",[1160],{"kind":1161,"url":1162},"website","https:\u002F\u002Fsource.android.com\u002F",[1164],"host-card-emulation","\u002Fglossary#aosp",false,{"slug":1168,"term":1169,"definition":1170,"category":1156,"aliases":1171,"links":1172,"related":1176,"readMore":-1,"target":1178,"hasArticle":1166},"app-clips","App Clips","An Apple feature that runs a small slice of an iOS app — under 15 MB — without installing the whole thing. Invoked from a QR code, an NFC tag or a link, for when the first thing a user does should not require a store visit.",[],[1173],{"kind":1174,"url":1175},"documentation","https:\u002F\u002Fdeveloper.apple.com\u002Fapp-clips\u002F",[507,1177],"install-referrer","\u002Fglossary#app-clips",{"slug":1180,"term":1181,"definition":1182,"category":1156,"aliases":1183,"links":1184,"related":1190,"readMore":-1,"target":1193,"hasArticle":1166},"bigquery","BigQuery","Google Cloud's analytics warehouse. You point SQL at billions of rows and it scans them in seconds, on storage held separately from the machines doing the querying — which is what keeps reporting and exploration off the database that is serving live traffic.",[],[1185,1187],{"kind":1161,"url":1186},"https:\u002F\u002Fcloud.google.com\u002Fbigquery",{"kind":1188,"url":1189},"wikipedia","https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FBigQuery",[1191,1192],"object-storage","elasticsearch","\u002Fglossary#bigquery",{"slug":1195,"term":1196,"definition":1197,"category":1198,"aliases":1199,"links":1203,"related":1206,"readMore":-1,"target":1207,"hasArticle":1166},"ci-cd","CI\u002FCD","Automation that builds, tests and ships every change without anyone running commands by hand. On mobile it is what turns a release into a button press instead of an afternoon of someone else being unavailable.","practice",[1200,1201,1202],"CI","continuous integration","continuous delivery",[1204],{"kind":1188,"url":1205},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FCI\u002FCD",[],"\u002Fglossary#ci-cd",{"slug":1209,"term":1210,"definition":1211,"category":1212,"aliases":1213,"links":1215,"related":1218,"readMore":-1,"target":1221,"hasArticle":1166},"crud","CRUD","Create, read, update, delete — the four operations behind almost every form and admin screen. Shorthand for the routine data-management half of an app, as opposed to the parts carrying real domain logic.","architecture",[1214],"Create, Read, Update, Delete",[1216],{"kind":1188,"url":1217},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FCreate,_read,_update_and_delete",[1219,1220],"rest","graphql","\u002Fglossary#crud",{"slug":1223,"term":1224,"definition":1225,"category":1212,"aliases":1226,"links":1231,"related":1234,"readMore":-1,"target":1237,"hasArticle":1166},"container-registry","Container registry","A hosted store for container images, addressed by name and tag — Docker Hub, GitHub Container Registry, or a cloud provider's own. Pushing a build there turns 'works on my machine' into an image anyone can pull and run unchanged.",[1227,1228,1229,1230],"image registry","Docker registry","GHCR","ghcr.io",[1232],{"kind":1174,"url":1233},"https:\u002F\u002Fdocs.github.com\u002Fen\u002Fpackages\u002Fworking-with-a-github-packages-registry\u002Fworking-with-the-container-registry",[1235,1236],"dev-container","multi-arch-image","\u002Fglossary#container-registry",{"slug":507,"term":1239,"definition":1240,"category":1156,"aliases":1241,"links":1245,"related":1248,"readMore":1249,"target":1249,"hasArticle":734},"Deep linking","A link that opens a specific screen inside an installed app instead of its home screen or a web page. Deferred deep linking survives an install, so a tap that leads through the app store still lands on the right screen.",[1242,1243,1244],"deferred deep linking","universal links","Android App Links",[1246],{"kind":1188,"url":1247},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FMobile_deep_linking",[1168,1177],"\u002Fglossary\u002Fdeep-linking",{"slug":1235,"term":1251,"definition":1252,"category":1198,"aliases":1253,"links":1257,"related":1262,"readMore":-1,"target":1263,"hasArticle":1166},"Dev Container","A development environment described once in devcontainer.json — the OS, tools, and runtime versions a project needs — and opened identically inside a container by every contributor's editor, instead of a setup guide everyone interprets differently.",[1254,1255,1256],"devcontainer.json","Dev Containers","VS Code Dev Containers",[1258,1260],{"kind":1161,"url":1259},"https:\u002F\u002Fcontainers.dev\u002F",{"kind":1174,"url":1261},"https:\u002F\u002Fcode.visualstudio.com\u002Fdocs\u002Fdevcontainers\u002Fcontainers",[1223],"\u002Fglossary#dev-container",{"slug":1192,"term":1265,"definition":1266,"category":1156,"aliases":1267,"links":1270,"related":1275,"readMore":-1,"target":1276,"hasArticle":1166},"Elasticsearch","A search and analytics engine that indexes records so they can be filtered and searched interactively instead of scanned. What you reach for when the question is \"show me these particular sessions, narrowed six ways\" rather than \"sum this column\".",[1268,1269],"Elastic","ELK",[1271,1273],{"kind":1161,"url":1272},"https:\u002F\u002Fwww.elastic.co\u002Felasticsearch",{"kind":1188,"url":1274},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FElasticsearch",[1180],"\u002Fglossary#elasticsearch",{"slug":1278,"term":1279,"definition":1280,"category":1212,"aliases":1281,"links":1284,"related":1287,"readMore":-1,"target":1290,"hasArticle":1166},"end-to-end-encryption","End-to-end encryption","Encryption applied on the sending device and undone only on the receiving one, so the service carrying the message cannot read it — not under subpoena, not after a breach. It protects the content and never the metadata.",[1282,1283],"E2EE","end-to-end encrypted",[1285],{"kind":1188,"url":1286},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FEnd-to-end_encryption",[1288,1289],"tls","jwt","\u002Fglossary#end-to-end-encryption",{"slug":1292,"term":1293,"definition":1294,"category":1212,"aliases":1295,"links":1298,"related":1299,"readMore":-1,"target":1303,"hasArticle":1166},"fan-out","Fan-out","Reading an upstream source once and delivering each update to every client subscribed to it. The naive version writes to subscribers in a loop and stalls the moment one socket is slow; a real one buffers per client and drops whoever cannot keep up.",[1296,1297],"fanout","broadcast",[],[1300,1301,1302],"websocket","pub-sub","server-sent-events","\u002Fglossary#fan-out",{"slug":1305,"term":1306,"definition":1307,"category":1198,"aliases":1308,"links":1312,"related":1315,"readMore":-1,"target":1319,"hasArticle":1166},"feature-flags","Feature flags","Switches that turn functionality on or off from configuration rather than from a release. They let one binary behave differently per brand, market or user, and let a risky feature be shut off without shipping a new build through review.",[1309,1310,1311],"feature flag","feature toggle","feature gating",[1313],{"kind":1188,"url":1314},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FFeature_toggle",[1316,1317,1318],"staged-rollout","white-label","multi-tenancy","\u002Fglossary#feature-flags",{"slug":1321,"term":1322,"definition":1323,"category":1212,"aliases":1324,"links":1328,"related":1331,"readMore":-1,"target":1332,"hasArticle":1166},"floating-point","Floating point","The IEEE 754 binary format behind double and float. It cannot hold 0.1 exactly, so 0.1 + 0.2 is 0.30000000000000004 — invisible in graphics and fatal in money, which belongs in integer minor units or a decimal type instead.",[1325,1326,1327],"IEEE 754","double","floating-point arithmetic",[1329],{"kind":1188,"url":1330},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FIEEE_754",[],"\u002Fglossary#floating-point",{"slug":1334,"term":1335,"definition":1336,"category":1198,"aliases":1337,"links":1340,"related":1345,"readMore":-1,"target":1349,"hasArticle":1166},"gdpr","GDPR","The EU regulation covering personal data of people in the EU: a lawful basis for collecting it, real consent for tracking, and rights to see and delete it. It follows your users, not your servers, so it applies wherever the company is registered.",[1338,1339],"General Data Protection Regulation","data protection",[1341,1343],{"kind":1161,"url":1342},"https:\u002F\u002Fgdpr.eu\u002F",{"kind":1188,"url":1344},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FGeneral_Data_Protection_Regulation",[1346,1347,1348],"pci-dss","soc-2","hipaa","\u002Fglossary#gdpr",{"slug":1351,"term":1352,"definition":1353,"category":1198,"aliases":1354,"links":1358,"related":1361,"readMore":-1,"target":1362,"hasArticle":1166},"golden-test","Golden test","A test that renders a widget and compares the result pixel for pixel against a stored reference image. In Flutter it is the cheapest way to answer whether a redesign broke the empty state at 320pt, in dark mode, at 200% text scale.",[1355,1356,1357],"golden tests","screenshot test","snapshot test",[1359],{"kind":1174,"url":1360},"https:\u002F\u002Fapi.flutter.dev\u002Fflutter\u002Fflutter_test\u002FmatchesGoldenFile.html",[1195],"\u002Fglossary#golden-test",{"slug":1220,"term":1364,"definition":1365,"category":1212,"aliases":1366,"links":1367,"related":1372,"readMore":-1,"target":1373,"hasArticle":1166},"GraphQL","A query language for APIs where the client names exactly the fields it wants and gets one response shaped to match. It removes the over-fetching REST endpoints drift into, and adds a failure mode of its own: an unbounded query that walks the whole data model.",[],[1368,1370],{"kind":1161,"url":1369},"https:\u002F\u002Fgraphql.org\u002F",{"kind":1188,"url":1371},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FGraphQL",[1219],"\u002Fglossary#graphql",{"slug":1348,"term":1375,"definition":1376,"category":1198,"aliases":1377,"links":1379,"related":1382,"readMore":-1,"target":1383,"hasArticle":1166},"HIPAA","The US law governing protected health information — how it may be stored, transmitted, logged and disclosed. Like PCI-DSS it is an architectural constraint chosen at the start, not a policy document added before launch.",[1378],"Health Insurance Portability and Accountability Act",[1380],{"kind":1188,"url":1381},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FHealth_Insurance_Portability_and_Accountability_Act",[1346,1334,1347],"\u002Fglossary#hipaa",{"slug":1385,"term":1386,"definition":1387,"category":1212,"aliases":1388,"links":1391,"related":1394,"readMore":-1,"target":1396,"hasArticle":1166},"headless-cms","Headless CMS","A content system with an editor and an API but no front end of its own. Editors publish in one place, and the site or app renders that content itself — so the presentation layer is yours rather than the CMS vendor's.",[1389,1390],"headless content management system","content API",[1392],{"kind":1188,"url":1393},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FHeadless_content_management_system",[1395,1219],"server-side-rendering","\u002Fglossary#headless-cms",{"slug":1164,"term":943,"definition":1398,"category":1156,"aliases":1399,"links":1402,"related":1405,"readMore":-1,"target":1406,"hasArticle":1166},"Letting an Android phone act as a contactless card over NFC in software, with no hardware secure element. It is how a wallet app pays at a terminal: the phone speaks the same EMV contactless protocol the plastic card would have.",[1400,945,1401],"HCE","contactless payments",[1403],{"kind":1174,"url":1404},"https:\u002F\u002Fdeveloper.android.com\u002Fdevelop\u002Fconnectivity\u002Fnfc\u002Fhce",[1346,1154],"\u002Fglossary#host-card-emulation",{"slug":1408,"term":1409,"definition":1410,"category":1156,"aliases":1411,"links":1412,"related":1415,"readMore":-1,"target":1417,"hasArticle":1166},"impeller","Impeller","The rendering engine Flutter uses today, default on iOS since 2023 and on Android since 2024. It compiles its shaders ahead of time instead of during the first animation, which removed the shader-compilation jank that was Flutter's most visible production problem.",[],[1413],{"kind":1174,"url":1414},"https:\u002F\u002Fdocs.flutter.dev\u002Fperf\u002Fimpeller",[1416],"skia","\u002Fglossary#impeller",{"slug":1419,"term":1420,"definition":1421,"category":1422,"aliases":1423,"links":1427,"related":1430,"readMore":-1,"target":1431,"hasArticle":1166},"in-app-purchase","In-app purchase","Selling digital goods or a subscription through the Apple or Google billing that both stores require for digital content and take a commission on. The hard part is never the purchase; it is restoring it on a new device and keeping entitlement state honest.","business",[1424,1425,1426],"IAP","in-app purchases","in-app subscription",[1428],{"kind":1174,"url":1429},"https:\u002F\u002Fdeveloper.apple.com\u002Fin-app-purchase\u002F",[212],"\u002Fglossary#in-app-purchase",{"slug":1177,"term":1433,"definition":1434,"category":1156,"aliases":1435,"links":1436,"related":1439,"readMore":-1,"target":1440,"hasArticle":1166},"Install Referrer","A Google Play API that hands a freshly installed Android app the campaign parameters from the link that led to the install. The Android half of deferred deep linking, and the dependable way to attribute where a user came from.",[],[1437],{"kind":1174,"url":1438},"https:\u002F\u002Fdeveloper.android.com\u002Fgoogle\u002Fplay\u002Finstallreferrer",[507,1168],"\u002Fglossary#install-referrer",{"slug":1289,"term":1442,"definition":1443,"category":1444,"aliases":1445,"links":1447,"related":1452,"readMore":-1,"target":1453,"hasArticle":1166},"JWT","A signed token carrying its own claims, so a server can tell who a request belongs to without looking a session up. Standard for mobile authentication. The signature proves it was not altered; it does not hide what is inside.","protocol",[1446],"JSON Web Token",[1448,1450],{"kind":1161,"url":1449},"https:\u002F\u002Fjwt.io\u002F",{"kind":1188,"url":1451},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FJSON_Web_Token",[1346],"\u002Fglossary#jwt",{"slug":1455,"term":1456,"definition":1457,"category":1198,"aliases":1458,"links":1462,"related":1465,"readMore":-1,"target":1466,"hasArticle":1166},"kyc","KYC","Know Your Customer — the identity checks a regulated financial product runs before it lets anyone move money: document capture, liveness, sanctions and anti-money-laundering screening. It shapes onboarding more than any design decision does.",[1459,1460,1461],"Know Your Customer","AML","KYC\u002FAML",[1463],{"kind":1188,"url":1464},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FKnow_your_customer",[1346,1334],"\u002Fglossary#kyc",{"slug":76,"term":74,"definition":1468,"category":1156,"aliases":1469,"links":1471,"related":1472,"readMore":1473,"target":1473,"hasArticle":1166},"Sharing business logic written in Kotlin across Android, iOS and the server while each platform keeps its own native UI. The alternative to Flutter when the interface has to be native but the rules behind it do not.",[1470],"KMP",[],[],"\u002Ftechnologies\u002Fkmp",{"slug":1475,"term":1476,"definition":1477,"category":1422,"aliases":1478,"links":1480,"related":1483,"readMore":-1,"target":1484,"hasArticle":1166},"mvp","MVP","The smallest version of a product that can go in front of real users and still answer the question you built it to answer. A decision about scope, not about quality — an MVP still has to work.",[1479],"minimum viable product",[1481],{"kind":1188,"url":1482},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FMinimum_viable_product",[1317],"\u002Fglossary#mvp",{"slug":1236,"term":1486,"definition":1487,"category":1212,"aliases":1488,"links":1492,"related":1495,"readMore":-1,"target":1496,"hasArticle":1166},"Multi-architecture image","A single image tag that resolves to different binaries per CPU architecture — linux\u002Famd64 and linux\u002Farm64 are the common pair — so the same docker pull works unchanged on Intel\u002FAMD servers and Apple Silicon laptops.",[1489,1490,1491],"multi-arch build","multi-platform image","linux\u002Famd64 + linux\u002Farm64",[1493],{"kind":1174,"url":1494},"https:\u002F\u002Fdocs.docker.com\u002Fbuild\u002Fbuilding\u002Fmulti-platform\u002F",[1223],"\u002Fglossary#multi-arch-image",{"slug":1318,"term":1498,"definition":1499,"category":1212,"aliases":1500,"links":1503,"related":1506,"readMore":-1,"target":1507,"hasArticle":1166},"Multi-tenancy","One deployment serving many customers, each seeing only its own data, configuration and enabled features because tenant context is resolved per request. It is what makes a fleet of branded apps one product instead of many forks.",[1501,1502],"multi-tenant","tenant",[1504],{"kind":1188,"url":1505},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FMultitenancy",[1317,1305],"\u002Fglossary#multi-tenancy",{"slug":1509,"term":1510,"definition":1511,"category":1444,"aliases":1512,"links":1516,"related":1521,"readMore":-1,"target":1522,"hasArticle":1166},"oauth","OAuth","The standard behind Sign in with Apple, Google and the rest: the user authorises your app at a provider they already trust, and your app receives a token instead of their password. Nobody invents a new credential and you never store one.",[1513,1514,1515],"OAuth 2.0","social login","Sign in with Apple",[1517,1519],{"kind":1161,"url":1518},"https:\u002F\u002Foauth.net\u002F2\u002F",{"kind":1188,"url":1520},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FOAuth",[1289],"\u002Fglossary#oauth",{"slug":1191,"term":1524,"definition":1525,"category":1212,"aliases":1526,"links":1530,"related":1533,"readMore":-1,"target":1534,"hasArticle":1166},"Object storage","Storage that holds a whole file under a key rather than in a filesystem tree — Amazon S3 and the many services that speak its API. Cheap, effectively unlimited, and the usual home for raw events, backups and media: written once, read rarely, kept forever.",[1527,1528,1529],"S3","S3-compatible storage","blob storage",[1531],{"kind":1188,"url":1532},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FObject_storage",[1180],"\u002Fglossary#object-storage",{"slug":1346,"term":1536,"definition":1537,"category":1198,"aliases":1538,"links":1541,"related":1546,"readMore":-1,"target":1547,"hasArticle":1166},"PCI-DSS","The card industry security standard binding anyone who stores, processes or transmits card data. Most apps stay out of its scope on purpose, by handing card entry to a certified payment provider instead.",[1539,1540],"PCI DSS","Payment Card Industry Data Security Standard",[1542,1544],{"kind":1161,"url":1543},"https:\u002F\u002Fwww.pcisecuritystandards.org\u002F",{"kind":1188,"url":1545},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FPayment_Card_Industry_Data_Security_Standard",[1289],"\u002Fglossary#pci-dss",{"slug":1549,"term":1550,"definition":1551,"category":1156,"aliases":1552,"links":1555,"related":1558,"readMore":-1,"target":1559,"hasArticle":1166},"platform-channels","Platform channels","The bridge a Flutter app uses to call native iOS and Android code — Keychain and Keystore, biometrics, payment sheets, any SDK without a Dart package. Routine work but real work, and the first place an engineer who never left Dart will stall.",[1553,1554],"platform channel","method channel",[1556],{"kind":1174,"url":1557},"https:\u002F\u002Fdocs.flutter.dev\u002Fplatform-integration\u002Fplatform-channels",[76],"\u002Fglossary#platform-channels",{"slug":1561,"term":1562,"definition":1563,"category":1444,"aliases":1564,"links":1567,"related":1570,"readMore":-1,"target":1571,"hasArticle":1166},"post-quantum-cryptography","Post-quantum cryptography","Encryption algorithms built to stay secure against a future quantum computer, now standardized by NIST. The migration is urgent ahead of the hardware because traffic captured today can be decrypted once such a machine exists.",[1565,1566],"PQC","post-quantum crypto",[1568],{"kind":1188,"url":1569},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FPost-quantum_cryptography",[1288,1278],"\u002Fglossary#post-quantum-cryptography",{"slug":212,"term":1573,"definition":1574,"category":1422,"aliases":1575,"links":1578,"related":1581,"readMore":-1,"target":1583,"hasArticle":1166},"Product-market fit","The point at which a product has demonstrably found people who want it — they use it, come back, and pay. Before it, engineering answers a question; after it, engineering answers demand.",[1576,1577],"PMF","product\u002Fmarket fit",[1579],{"kind":1188,"url":1580},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FProduct-market_fit",[1475,1582],"time-to-market","\u002Fglossary#product-market-fit",{"slug":1585,"term":1586,"definition":1587,"category":1198,"aliases":1588,"links":1590,"related":1593,"readMore":-1,"target":1595,"hasArticle":1166},"prompt-injection","Prompt injection","An attack where text supplied by a user is read by a language model as instructions rather than as data, steering it past its own rules. The LLM-era sibling of SQL injection, and it appears wherever user input is concatenated into a prompt.",[1589],"injection attack",[1591],{"kind":1188,"url":1592},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FPrompt_injection",[1594],"rate-limiting","\u002Fglossary#prompt-injection",{"slug":1301,"term":1597,"definition":1598,"category":1212,"aliases":1599,"links":1602,"related":1605,"readMore":-1,"target":1606,"hasArticle":1166},"Pub\u002FSub","A messaging pattern where a producer publishes an event and any number of consumers read it independently, with a broker in between. The producer never waits for them, which is how a request path stays fast while slower work happens behind it.",[1600,1601],"publish\u002Fsubscribe","Google Cloud Pub\u002FSub",[1603],{"kind":1188,"url":1604},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FPublish%E2%80%93subscribe_pattern",[],"\u002Fglossary#pub-sub",{"slug":1219,"term":1608,"definition":1609,"category":1212,"aliases":1610,"links":1613,"related":1616,"readMore":-1,"target":1617,"hasArticle":1166},"REST","The conventional style for HTTP APIs: a URL names a resource and the HTTP verb says what to do with it. The default way an app talks to a backend, and what most third-party integrations expect to find.",[1611,1612],"REST API","Representational State Transfer",[1614],{"kind":1188,"url":1615},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FREST",[1300,1302],"\u002Fglossary#rest",{"slug":1594,"term":1619,"definition":1620,"category":1198,"aliases":1621,"links":1624,"related":1627,"readMore":-1,"target":1628,"hasArticle":1166},"Rate limiting","A cap on how many requests one caller may make in a given window. It is what stops a single enthusiastic user, a scraper or a bot from spending a month of paid API budget in an afternoon, and it has to live on your side of the integration.",[1622,1623],"rate limit","throttling",[1625],{"kind":1188,"url":1626},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FRate_limiting",[1585],"\u002Fglossary#rate-limiting",{"slug":1347,"term":1630,"definition":1631,"category":1198,"aliases":1632,"links":1635,"related":1638,"readMore":-1,"target":1639,"hasArticle":1166},"SOC 2","An external auditor report on how an organisation handles customer data — security, availability, confidentiality — rather than a certificate you buy. Enterprise buyers ask for it, and it constrains architecture long before the audit itself does.",[1633,1634],"SOC2","System and Organization Controls",[1636],{"kind":1188,"url":1637},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FSystem_and_Organization_Controls",[1346,1334,1348],"\u002Fglossary#soc-2",{"slug":1641,"term":1642,"definition":1643,"category":1422,"aliases":1644,"links":1647,"related":1650,"readMore":-1,"target":1651,"hasArticle":1166},"saas","SaaS","Software sold as an ongoing subscription to a hosted product rather than as a one-off license the customer installs and runs. The vendor operates the servers, ships updates continuously, and bills per seat or per usage.",[1645,1646],"Software as a Service","software-as-a-service",[1648],{"kind":1188,"url":1649},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FSoftware_as_a_service",[1318,1317],"\u002Fglossary#saas",{"slug":1302,"term":1653,"definition":1654,"category":1444,"aliases":1655,"links":1657,"related":1660,"readMore":-1,"target":1661,"hasArticle":1166},"Server-Sent Events","A one-way stream from server to client over an ordinary HTTP connection. Simpler than a WebSocket and enough wherever only the server has something to say — a progress feed, an AI response arriving token by token.",[1656],"SSE",[1658],{"kind":1188,"url":1659},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FServer-sent_events",[1300,1219],"\u002Fglossary#server-sent-events",{"slug":1395,"term":1663,"definition":1664,"category":1212,"aliases":1665,"links":1668,"related":1671,"readMore":-1,"target":1672,"hasArticle":1166},"Server-side rendering","Building a page as finished HTML on the server, so the first response already carries the content, headings, meta tags and structured data. Crawlers, link previews and slow devices read it without running JavaScript.",[1666,1667],"SSR","server-rendered",[1669],{"kind":1188,"url":1670},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FServer-side_scripting",[1385],"\u002Fglossary#server-side-rendering",{"slug":1416,"term":1674,"definition":1675,"category":1156,"aliases":1676,"links":1679,"related":1684,"readMore":-1,"target":1685,"hasArticle":1166},"Skia","The open-source 2D graphics library from Google that draws Chrome, Android and — until Impeller — every Flutter frame. It renders to PDF as well as to a screen, which is what print-to-PDF in Chrome is doing.",[1677,1678],"Skia Graphics Engine","skia-safe",[1680,1682],{"kind":1161,"url":1681},"https:\u002F\u002Fskia.org\u002F",{"kind":1188,"url":1683},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FSkia_Graphics_Engine",[1408],"\u002Fglossary#skia",{"slug":1687,"term":1688,"definition":1689,"category":1422,"aliases":1690,"links":1694,"related":1695,"readMore":-1,"target":1697,"hasArticle":1166},"staff-augmentation","Staff augmentation","A hiring model where engineers from an outside partner join your team and work under your management — in your repository, your sprints, your process — instead of delivering a project of their own. You buy capacity; the code and the context stay with you.",[1691,1692,1693],"team augmentation","dedicated developers","outstaffing",[],[1696,1582],"total-cost-of-ownership","\u002Fglossary#staff-augmentation",{"slug":1316,"term":1699,"definition":1700,"category":1198,"aliases":1701,"links":1704,"related":1705,"readMore":-1,"target":1706,"hasArticle":1166},"Staged rollout","Releasing a build to a small percentage of users first and widening only once the crash-free rate holds. A bad build caught at ten percent is a bad afternoon; the same build at a hundred percent is a bad week.",[1702,1703],"phased release","canary release",[],[1305,1195],"\u002Fglossary#staged-rollout",{"slug":1708,"term":755,"definition":1709,"category":1212,"aliases":1710,"links":1714,"related":1717,"readMore":-1,"target":1718,"hasArticle":1166},"state-management","How an app decides where a value lives, who is allowed to change it, and which parts of the screen redraw when it does. In Flutter the choice between Riverpod, BLoC and Provider is among the first architectural decisions and the hardest to revisit.",[1711,1712,1713],"state management","BLoC","Riverpod",[1715],{"kind":1174,"url":1716},"https:\u002F\u002Fdocs.flutter.dev\u002Fdata-and-backend\u002Fstate-mgmt\u002Foptions",[1351],"\u002Fglossary#state-management",{"slug":1288,"term":1720,"definition":1721,"category":1444,"aliases":1722,"links":1726,"related":1729,"readMore":-1,"target":1730,"hasArticle":1166},"TLS","The encryption layer underneath HTTPS. It proves the server is who its certificate says, agrees a fresh key for the session, and encrypts everything after that — so the network in between sees ciphertext it cannot quietly alter.",[1723,1724,1725],"SSL","HTTPS","Transport Layer Security",[1727],{"kind":1188,"url":1728},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FTransport_Layer_Security",[1278,1289],"\u002Fglossary#tls",{"slug":1582,"term":1732,"definition":1733,"category":1422,"aliases":1734,"links":1736,"related":1739,"readMore":-1,"target":1740,"hasArticle":1166},"Time to market","How long it takes to get a product from decision to real users. Most stack and scope arguments are really arguments about this number, because every week saved is a week of revenue, feedback and competitive position.",[1735,1582],"TTM",[1737],{"kind":1188,"url":1738},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FTime_to_market",[1475,1696],"\u002Fglossary#time-to-market",{"slug":1696,"term":1742,"definition":1743,"category":1422,"aliases":1744,"links":1747,"related":1750,"readMore":-1,"target":1751,"hasArticle":1166},"Total cost of ownership","What a product costs across its whole life rather than to build once: maintenance, upgrades, annual OS and store migrations, and the second team you staff to keep two codebases in step. Usually larger than the build quote, and almost never inside it.",[1745,1746],"TCO","cost of ownership",[1748],{"kind":1188,"url":1749},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FTotal_cost_of_ownership",[1582],"\u002Fglossary#total-cost-of-ownership",{"slug":1753,"term":763,"definition":1754,"category":1444,"aliases":1755,"links":1757,"related":1762,"readMore":-1,"target":1764,"hasArticle":1166},"webrtc","The browser and mobile standard for sending audio, video and data directly between two devices, with servers involved only in introducing them to each other. It is what an in-app video call is built on when it is not a rented SDK.",[1756],"Web Real-Time Communication",[1758,1760],{"kind":1161,"url":1759},"https:\u002F\u002Fwebrtc.org\u002F",{"kind":1188,"url":1761},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FWebRTC",[1763,1300],"xmpp","\u002Fglossary#webrtc",{"slug":1300,"term":421,"definition":1766,"category":1444,"aliases":1767,"links":1768,"related":1771,"readMore":-1,"target":1772,"hasArticle":1166},"A protocol that holds one connection open between client and server so either side can send at any moment, instead of the client asking over and over. What live prices, chat and presence indicators run on.",[],[1769],{"kind":1188,"url":1770},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FWebSocket",[1302,1219],"\u002Fglossary#websocket",{"slug":1317,"term":1774,"definition":1775,"category":1422,"aliases":1776,"links":1779,"related":1782,"readMore":1783,"target":1783,"hasArticle":734},"White-label","One product shipped under many brands. A white-label mobile platform builds each client a store-ready app with its own name, design and content from a single shared codebase, instead of forking the project per customer.",[1777,1778],"white label","multi-tenant app",[1780],{"kind":1188,"url":1781},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FWhite-label_product",[1475],"\u002Fglossary\u002Fwhite-label",{"slug":1763,"term":1785,"definition":1786,"category":1444,"aliases":1787,"links":1790,"related":1795,"readMore":-1,"target":1796,"hasArticle":1166},"XMPP","An open, federated messaging protocol, and the long-standing alternative to writing a chat backend or renting one. It extends to presence, typing indicators and file transfer, and it is old enough that every platform has a mature client library.",[1788,1789],"Jabber","Extensible Messaging and Presence Protocol",[1791,1793],{"kind":1161,"url":1792},"https:\u002F\u002Fxmpp.org\u002F",{"kind":1188,"url":1794},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FXMPP",[1753,1300],"\u002Fglossary#xmpp"]