[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"technologies":3,"\u002Fblog\u002Fflutter-app-development-process":167,"team-members":899,"blog-topics":1241,"mdc-takuur-key":1283,"glossary":1327},[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":881,"extension":882,"hero":883,"meta":886,"metaDescription":887,"metaTitle":888,"navigation":889,"ogDescription":890,"path":891,"seo":892,"slug":893,"stem":894,"summary":895,"timestamp":896,"topic":41,"updated":897,"__hash__":898},"blog_en\u002Fblog\u002Fflutter-app-development-process.md","The Flutter App Development Process: How We Take an App From Idea to App Store","dima",{"type":172,"value":173,"toc":866},"minimark",[174,220,223,228,231,392,406,409,416,418,421,424,427,453,460,466,468,471,474,485,498,501,506,508,511,514,517,565,573,575,578,585,588,600,608,613,615,618,621,624,653,656,667,669,672,675,681,692,701,707,709,713,716,719,739,742,744,748,751,761,770,779,788,795,797,801,805,807,811,818,852,855],[175,176,177,181,182,185,186,185,189,185,192,185,195,185,198,201,202,205,206,210,211,214,215,219],"p",{},[178,179,180],"strong",{},"TL;DR."," The Flutter app development process runs in seven phases: ",[178,183,184],{},"discovery and scoping",", ",[178,187,188],{},"UX\u002FUI design",[178,190,191],{},"architecture and foundations",[178,193,194],{},"iterative development",[178,196,197],{},"QA and testing",[178,199,200],{},"release",", and ",[178,203,204],{},"post-launch maintenance",". What ties them together is that they are ",[207,208,209],"em",{},"feedback loops, not a waterfall"," — design starts before discovery finishes, QA runs alongside the build rather than after it, and every two weeks you get something installable on your phone instead of a status report. The one rule we do not bend: ",[178,212,213],{},"the invariants come before the feature code."," The state model, theme, error taxonomy, CI pipeline and test strategy are decided in week one, because every screen built afterwards either follows them or fights them. A typical build is 2–3 months for an ",[216,217],"term",{"slug":218},"mvp"," and 3–5 months for a full product, and launch is the middle of the process, not the end.",[221,222],"hr",{},[224,225,227],"h2",{"id":226},"the-flutter-app-development-steps-at-a-glance","The Flutter app development steps at a glance",[175,229,230],{},"Seven phases, in the order they start. This is the whole Flutter development lifecycle on one screen.",[232,233,234,256],"table",{},[235,236,237],"thead",{},[238,239,240,244,247,250,253],"tr",{},[241,242,243],"th",{},"Phase",[241,245,246],{},"What happens",[241,248,249],{},"Key deliverable",[241,251,252],{},"Who's involved",[241,254,255],{},"Typical duration",[257,258,259,279,298,317,336,355,373],"tbody",{},[238,260,261,267,270,273,276],{},[262,263,264],"td",{},[178,265,266],{},"1. Discovery & scoping",[262,268,269],{},"Idea becomes a specific, ordered backlog; the cut list gets agreed",[262,271,272],{},"Scoped backlog, fixed-scope quote, timeline",[262,274,275],{},"Founder\u002Fproduct lead, lead engineer, designer",[262,277,278],{},"3 days – 2 weeks",[238,280,281,286,289,292,295],{},[262,282,283],{},[178,284,285],{},"2. UX\u002FUI design",[262,287,288],{},"Design system first, then flows and screens against it",[262,290,291],{},"Design system + clickable prototype",[262,293,294],{},"Designer, product lead, lead engineer",[262,296,297],{},"2–4 weeks (overlaps build)",[238,299,300,305,308,311,314],{},[262,301,302],{},[178,303,304],{},"3. Architecture & foundations",[262,306,307],{},"State model, folder structure, error taxonomy, CI\u002FCD, test strategy",[262,309,310],{},"Running app skeleton, green pipeline, ADRs",[262,312,313],{},"Lead engineer, backend engineer",[262,315,316],{},"1–2 weeks",[238,318,319,324,327,330,333],{},[262,320,321],{},[178,322,323],{},"4. Iterative development",[262,325,326],{},"Vertical feature slices, demoable every sprint",[262,328,329],{},"Installable build every 1–2 weeks",[262,331,332],{},"Engineers, designer, product lead",[262,334,335],{},"4–16 weeks",[238,337,338,343,346,349,352],{},[262,339,340],{},[178,341,342],{},"5. QA & testing",[262,344,345],{},"Widget, golden, integration, and real-device testing",[262,347,348],{},"Test suite in CI + hardening pass",[262,350,351],{},"Engineers, QA, client testers",[262,353,354],{},"Continuous + 1–2 week hardening",[238,356,357,362,365,368,371],{},[262,358,359],{},[178,360,361],{},"6. Release",[262,363,364],{},"Store assets, submission, review, staged rollout",[262,366,367],{},"Live app on App Store and Google Play",[262,369,370],{},"Lead engineer, product lead, client accounts",[262,372,316],{},[238,374,375,380,383,386,389],{},[262,376,377],{},[178,378,379],{},"7. Post-launch",[262,381,382],{},"Monitoring, crash triage, iteration on real usage",[262,384,385],{},"Monthly release cadence, crash-free rate",[262,387,388],{},"Engineers, product lead",[262,390,391],{},"Ongoing",[175,393,394,395,400,401,405],{},"Those durations are ranges, and they overlap — the calendar is shorter than the sum of the rows. For where the weeks actually go on a real project, see the companion post: ",[396,397,399],"a",{"href":398},"\u002Fblog\u002Fhow-long-to-build-a-flutter-app","how long it takes to build a Flutter app",". For what each phase costs, see ",[396,402,404],{"href":403},"\u002Fblog\u002Fflutter-app-development-cost-2026","Flutter App Development Cost in 2026",".",[175,407,408],{},"Structurally, this is the same mobile app development process any competent team runs — the phases are not a Flutter invention. What Flutter changes is the economics inside them: one codebase to design for, one to test, one to release, and a UI layer that lives in code rather than in a stylesheet. That last detail is why the design and architecture phases carry more weight here than they would elsewhere.",[410,411],"how-to-schema",{":steps":412,"description":413,"name":414,"totalTime":415},"[{\"name\":\"Discovery and scoping\",\"text\":\"Turn the idea into a specific, ordered backlog. Agree what ships in version one and what is explicitly cut. Output is a scoped backlog, a fixed-scope quote, and a timeline.\"},{\"name\":\"UX and UI design\",\"text\":\"Build the design system first, then design flows and screens against it. Output is a design system and a clickable prototype the client can walk through before any feature code exists.\"},{\"name\":\"Architecture and foundations\",\"text\":\"Decide the state model, folder structure, error taxonomy, CI pipeline, and testing strategy before feature work starts. Output is a running app skeleton with a green pipeline.\"},{\"name\":\"Iterative development\",\"text\":\"Build vertical feature slices that go from the screen through to the backend. Ship an installable build every one to two weeks and review decisions rather than lines.\"},{\"name\":\"QA and testing\",\"text\":\"Run widget tests, golden tests, and integration tests in continuous integration, plus real-device testing at 200 percent text scale, in dark mode, and on a throttled network.\"},{\"name\":\"Release\",\"text\":\"Prepare store assets, submit to the App Store and Google Play, handle review, and roll out in stages rather than to everyone at once. Automate the build and upload with Fastlane.\"},{\"name\":\"Post-launch and maintenance\",\"text\":\"Monitor crashes and performance, triage what real usage surfaces, and keep a regular release cadence. Launch is the start of the product, not the end of the project.\"}]","How a Flutter app is built from idea to App Store, phase by phase.","The Flutter App Development Process","P12W",[221,417],{},[224,419,266],{"id":420},"_1-discovery-scoping",[175,422,423],{},"Discovery is the phase where an idea becomes a specific, ordered list of things to build. It is not a workshop with sticky notes. It is a lead engineer and a designer interrogating the app until every screen has a reason to exist.",[175,425,426],{},"Three things come out of it:",[428,429,430,437,447],"ul",{},[431,432,433,436],"li",{},[178,434,435],{},"A backlog, ordered."," Not \"user management\" — \"sign in with Apple, sign in with email, password reset, account deletion.\" Vague line items are where estimates go to die.",[431,438,439,442,443,446],{},[178,440,441],{},"A cut list."," The features that are ",[207,444,445],{},"not"," in version one, written down and agreed. The most valuable artifact in the process, and the one clients resist hardest.",[431,448,449,452],{},[178,450,451],{},"A fixed-scope quote and timeline",", derived from the backlog rather than from a gut feel about \"an app like this.\"",[175,454,455,456,459],{},"This is where budgets and timelines are really set, which is why a rushed discovery is the most expensive way to save a week. When you describe \"a simple workout tracker\" and we hand back a 40-screen backlog, that gap is not padding — onboarding, auth, settings, account deletion, payments, push and offline were always in the app you described. The ",[396,457,458],{"href":403},"cost breakdown"," covers how scope compounds into a number.",[175,461,462,465],{},[178,463,464],{},"Where it breaks:"," discovery with someone who cannot decide. If every answer goes back to a committee, discovery stretches from one week to four and the estimate is built on sand.",[221,467],{},[224,469,285],{"id":470},"_2-uxui-design",[175,472,473],{},"UX\u002FUI design is the phase where the app's visual and interaction language gets defined. It starts with the system, not the screens.",[175,475,476,477,480,481,484],{},"The first deliverable is a ",[178,478,479],{},"design system",": a palette with light and dark variants, a type ramp, a spacing scale, component states (default, pressed, disabled, loading, error), and the interaction vocabulary — how ",[207,482,483],{},"this app"," shows loading, shows an empty list, confirms a destructive action. Screens get designed against that system afterwards.",[175,486,487,488,492,493,497],{},"That order is not aesthetic preference; it is build speed. A Flutter app renders every pixel from Dart code, and a mature design system maps almost one-to-one onto ",[489,490,491],"code",{},"ThemeData"," — wired in once, every later screen is assembled from components that already exist. Without it you get what we describe in ",[396,494,496],{"href":495},"\u002Fblog\u002Fai-agents-struggle-with-flutter","how AI agents struggle with Flutter",": forty screens that each work and do not add up to one app, colors hardcoded at every call site, and a rebrand that costs a several-hundred-file diff.",[175,499,500],{},"We design for the constraints that break Flutter layouts later, too — long strings in the second locale, 200% text scale, small phones at 320pt. Catching those in Figma costs minutes; catching them in QA costs a redesign. What you get out of the phase is a design system plus a clickable prototype, before a line of feature code exists.",[175,502,503,505],{},[178,504,464],{}," design-by-review-cycle. Three rounds of \"can we see one more option\" on the home screen delays every downstream phase, because engineers cannot build against a moving target.",[221,507],{},[224,509,304],{"id":510},"_3-architecture-foundations",[175,512,513],{},"Architecture is the phase where the decisions every later screen depends on get made — before any screen exists. Practically, that means we spend one to two weeks building an app that does nothing.",[175,515,516],{},"That fortnight decides the next six months. What gets settled:",[428,518,519,529,535,545,559],{},[431,520,521,524,525,528],{},[178,522,523],{},"State management."," One choice, applied everywhere. Sealed state classes, so illegal combinations — loading ",[207,526,527],{},"and"," error at once — are unrepresentable rather than merely unlikely.",[431,530,531,534],{},[178,532,533],{},"Folder structure and module boundaries."," Where a feature lives, what it may import.",[431,536,537,540,541,544],{},[178,538,539],{},"An error taxonomy."," Named failure modes — network, auth expired, validation, declined payment, conflict — instead of one ",[489,542,543],{},"Something went wrong"," that makes every bug unreproducible.",[431,546,547,550,551,554,555,558],{},[178,548,549],{},"CI\u002FCD."," Pipeline green on day one: ",[489,552,553],{},"flutter analyze"," with lints promoted to errors, ",[489,556,557],{},"flutter test",", a build artifact per commit, Fastlane wired to TestFlight and the Play internal track.",[431,560,561,564],{},[178,562,563],{},"Testing strategy."," Which layers get widget tests, which screens get goldens, what the frame-time budget is.",[175,566,567,568,572],{},"We call these the invariants, and they come first because they cannot be retrofitted cheaply. \"Follow the existing pattern\" is a cheap instruction to give a person or an agent — but only once a pattern exists to point at. In a repo with none, everyone invents their own, and the result is the archaeology we get paid to ",[396,569,571],{"href":570},"\u002Fservices\u002Fai-code-audit","audit"," two years later. The phase ends with a running skeleton, a green pipeline, and short decision records for the choices a future engineer would otherwise re-litigate.",[221,574],{},[224,576,323],{"id":577},"_4-iterative-development",[175,579,580,581,584],{},"Iterative development is the phase where features get built and shipped in small, demoable increments rather than delivered in one lump at the end. The Flutter development workflow here runs in ",[178,582,583],{},"vertical feature slices",": one feature built end to end — UI, state, API integration, error handling, tests — rather than \"all the screens\" followed by \"all the plumbing.\" A slice you can open on a phone tells you something true. A folder of unwired screens does not.",[175,586,587],{},"The cadence is a demoable increment every one to two weeks, on your device via TestFlight or the Play internal track. Not a screenshot, not a Loom — the app, on your phone, that you can hand to a colleague.",[175,589,590,591,594,595,599],{},"Code review is on ",[178,592,593],{},"decisions, not lines",". Is this the same state model as the rest of the app? Is it styled from the theme? Is this value derived once, or for the third time? Does this string survive Russian? Agents write a large share of the code and our engineers own those decisions, which is ",[396,596,598],{"href":597},"\u002Fblog\u002Fbuilding-with-ai","how we build"," — line-by-line review of generated code does not scale; decision-level review does.",[175,601,602,603,607],{},"Design and QA keep running alongside, and so does backend work — which is why a system like the ",[396,604,606],{"href":605},"\u002Fblog\u002Fextraetf-realtime-fintech-flutter-go","real-time market data layer behind ExtraETF"," gets built and load-tested while the Flutter client is still assembling screens against a mock.",[175,609,610,612],{},[178,611,464],{}," silent sprints. If two weeks pass without you opening a build, the loop is broken and you find out about the misunderstanding a month late.",[221,614],{},[224,616,342],{"id":617},"_5-qa-testing",[175,619,620],{},"QA is the layer that runs from the first feature slice to the last, not a phase bolted on at the end — automated checks in CI on every commit, plus a hardening pass before release.",[175,622,623],{},"What runs in CI on every commit:",[428,625,626,632,641,647],{},[431,627,628,631],{},[178,629,630],{},"Widget tests"," for behavior: the button disables while submitting, the error clears on retype, the list paginates at the right offset.",[431,633,634,640],{},[178,635,636],{},[216,637,639],{"slug":638},"golden-test","Golden tests"," for appearance — the highest-leverage test type in Flutter, because a golden turns \"did this redesign break the empty state at 320pt in dark mode at 200% text scale?\" into a check that runs in seconds instead of a question nobody asks.",[431,642,643,646],{},[178,644,645],{},"Integration tests"," for the flows that lose money when broken: sign-up, checkout, payment.",[431,648,649,652],{},[178,650,651],{},"A regression test for every bug fixed",", so it cannot come back.",[175,654,655],{},"What a machine cannot do, a person does on real hardware: the app at 200% text scale, in dark mode, in both languages, on a small old Android phone, with the network throttled and then killed mid-request. Ten minutes of that finds an entire category of defect no static check will ever report.",[175,657,658,659,662,663,666],{},"And we hold a ",[178,660,661],{},"frame budget"," — 16.6ms at 60fps, checked on profile builds. A list that janks after someone adds a shadow and an ",[489,664,665],{},"Opacity"," inside the item builder is a regression no unit test catches and every user feels.",[221,668],{},[224,670,361],{"id":671},"_6-release",[175,673,674],{},"Release is the phase where the app goes through store submission, review, and rollout. It is 1–2 weeks of work that most timelines pretend is an afternoon.",[175,676,677,680],{},[178,678,679],{},"Store assets and metadata"," — screenshots at every required size, descriptions, keywords, privacy nutrition labels, data-safety declarations. Account deletion has to exist in-app; both stores enforce it.",[175,682,683,686,687,691],{},[178,684,685],{},"Review realities."," Apple review is typically 24–48 hours, but typical is not guaranteed, and the rejection categories are predictable: missing account deletion, a sign-in wall with no demo credentials, an incomplete privacy declaration, payments routed around in-app purchase. For anyone shipping multiple branded apps, guideline 4.2.6 is its own discipline — we covered ",[396,688,690],{"href":689},"\u002Fblog\u002Fwhite-label-app-platform-flutter","what actually passes review"," at fleet scale. Google review is usually faster, but a new developer account can sit in extended review for days.",[175,693,694,700],{},[178,695,696,405],{},[216,697,699],{"slug":698},"staged-rollout","Staged rollout"," We ship to 10% on Google Play and watch the crash-free rate before going wider; phased release on the App Store does the same. A bad build caught at 10% is a bad afternoon. The same build at 100% is a bad week.",[175,702,703,706],{},[178,704,705],{},"Automation."," Fastlane builds, signs, and uploads to both stores — including multi-publisher setups where each brand ships under its own account. Manual release is where a version code gets typed wrong at 11pm.",[221,708],{},[224,710,712],{"id":711},"_7-post-launch-maintenance","7. Post-launch & maintenance",[175,714,715],{},"Post-launch maintenance is the phase where the app meets real users and keeps changing. Launch is the start of it, not the end of the project.",[175,717,718],{},"Real usage immediately surfaces what no test could: the OEM Android skin that breaks push notifications, the OS update that deprecates an API, the crash on a device you did not own. So the process continues:",[428,720,721,727,733],{},[431,722,723,726],{},[178,724,725],{},"Monitoring"," — crash reporting, performance traces, and analytics on the flows that matter, watched hourly for the first 48 hours and weekly after that.",[431,728,729,732],{},[178,730,731],{},"Iteration"," — the backlog you cut in discovery, reprioritized against what people actually do.",[431,734,735,738],{},[178,736,737],{},"Maintenance"," — annual OS releases, SDK updates, store policy changes, certificate and API-key rotation. Flutter and its plugins move; an app left untouched for a year is not stable, it is stale.",[175,740,741],{},"Budget for the product, not the project. An app that ships and then gets nothing is on a slow path back to a rewrite.",[221,743],{},[224,745,747],{"id":746},"how-we-keep-it-on-track","How we keep it on track",[175,749,750],{},"Processes do not fail dramatically. They slip a few days at a time. Four things prevent most of it, and each has a known failure mode.",[175,752,753,756,757,760],{},[178,754,755],{},"Tight scope, written down."," The cut list from discovery is a contract with the timeline; new ideas go on the v2 list and we say so out loud. ",[207,758,759],{},"Breaks when"," nobody defends the list — every \"tiny addition\" is genuinely tiny, and the twentieth one is a month.",[175,762,763,766,767,769],{},[178,764,765],{},"A decisive stakeholder cadence."," One person who can approve a screen the day they see it, a weekly call, a build to install. ",[207,768,759],{}," decisions route through a committee. On a six-week build, one week of decision latency is a 20% overrun before an engineer has done anything wrong.",[175,771,772,775,776,778],{},[178,773,774],{},"Invariants set up front."," The reason our third month costs about what our first did. ",[207,777,759],{}," a deadline tempts everyone to skip week one and start on screens.",[175,780,781,784,785,787],{},[178,782,783],{},"Short feedback loops."," Installable builds every one to two weeks, QA in CI, a demo you actually open. ",[207,786,759],{}," the client goes quiet — the loop only works if someone is on the other end of it.",[175,789,790,791,794],{},"And the honest one: ",[178,792,793],{},"our estimates are wrong in one direction."," Integrations are where they miss most. Every third-party SDK looks like an afternoon in the pitch and turns into a two-week debugging session about edge cases on Android 10. We build slack in for that rather than pretending it away, and when a phase is going to overrun you hear it that week, not at the deadline.",[221,796],{},[224,798,800],{"id":799},"frequently-asked-questions","Frequently asked questions",[802,803],"questions",{":items":804},"[{\"title\":\"What are the steps to build a Flutter app?\",\"text\":\"There are seven steps: discovery and scoping, UX\u002FUI design, architecture and foundations, iterative development, QA and testing, release, and post-launch maintenance. Discovery turns the idea into an ordered backlog and a fixed scope, design produces a design system and a prototype, and architecture sets the state model, error handling, CI pipeline and testing strategy before any feature code is written. Development then builds features in vertical slices with QA running alongside rather than after, followed by store release and ongoing maintenance.\"},{\"title\":\"How does the Flutter development process work?\",\"text\":\"It works as a set of overlapping feedback loops rather than a linear waterfall. Design starts before discovery finishes, engineering foundations are laid while the last screens are being designed, and QA runs continuously in continuous integration instead of as a phase at the end. The client sees an installable build every one to two weeks, which is the loop that catches misunderstandings while they are still cheap to fix. A typical build is two to three months for an MVP and three to five months for a full product.\"},{\"title\":\"What comes first in app development?\",\"text\":\"Discovery comes first: turning the idea into a specific, ordered backlog with an explicit list of what is not in version one. Budgets and timelines are really set here, not later, because everything downstream is execution against these decisions. On the engineering side, the first thing built is not a feature but the foundations — the state model, folder structure, error taxonomy, CI pipeline and testing strategy — because those cannot be retrofitted cheaply once forty screens exist.\"},{\"title\":\"How is QA done for Flutter apps?\",\"text\":\"QA runs continuously, not as a final phase. Widget tests cover behavior, golden tests catch visual regressions by comparing rendered screens against reference images, and integration tests cover the flows that lose money when broken. On top of that, engineers test on real devices at 200 percent text scale, in dark mode, in every supported language, and on a throttled or dropped network. Frame times are checked against a 16.6ms budget on profile builds, because jank is a regression that no unit test catches and every user feels.\"},{\"title\":\"How long does each phase of a Flutter project take?\",\"text\":\"Discovery takes three days to two weeks, design two to four weeks, and architecture and foundations one to two weeks. Iterative development runs four to sixteen weeks depending on scope, with QA continuous throughout plus a one to two week hardening pass. Release takes one to two weeks including store assets, review and staged rollout. The phases overlap heavily, so the calendar is shorter than the sum of those ranges — typically two to three months for an MVP and three to five for a full product.\"},{\"title\":\"What happens after a Flutter app launches?\",\"text\":\"Launch is the start of the product, not the end of the project. The first 48 hours are spent watching crash reports, performance traces and the staged rollout percentage before widening it. After that the work becomes iteration on real usage data plus maintenance: annual iOS and Android releases, Flutter and plugin updates, store policy changes, and certificate and API key rotation. An app that ships and then receives nothing is not stable, it is quietly heading toward a rewrite.\"},{\"title\":\"How is agile used in Flutter development?\",\"text\":\"It is used as short feedback loops rather than as a ceremony framework. Work is built in vertical feature slices that go from the screen through to the backend, so every increment is something you can install and use rather than a folder of unwired screens. Sprints are one to two weeks and each ends with a build on the client device via TestFlight or the Play internal track. What stays deliberately non-agile is the architecture: the state model, theme, error taxonomy and test strategy are set up front, because iterating on those after forty screens exist is a rewrite, not a sprint.\"}]",[221,806],{},[224,808,810],{"id":809},"scope-your-build-with-us","Scope your build with us",[175,812,813,814,817],{},"That is how Flutter apps are built when someone is actually running the process. If you are evaluating agencies, the process ",[207,815,816],{},"is"," the product — anyone can show you screenshots. What decides whether your app ships on time is whether there is a real machine behind it: a cut list someone defends, invariants set in week one, a build on your phone every fortnight, and tests that run before a human looks.",[428,819,820,831,842],{},[431,821,822,825,826,830],{},[178,823,824],{},"Book a discovery call"," and we will run your idea through step one: ",[396,827,829],{"href":828},"\u002Fcontact","talk to us",". You get an ordered backlog, a cut list, and a fixed-scope quote — not a range wide enough to hide in.",[431,832,833,836,837,841],{},[178,834,835],{},"See the offering"," — team, stack, and pricing tiers on the ",[396,838,840],{"href":839},"\u002Fservices\u002Fflutter-app-development","Flutter app development"," page.",[431,843,844,847,848,851],{},[178,845,846],{},"Already have a build?"," If someone else ran this process badly, an ",[396,849,850],{"href":570},"AI code audit"," tells you what it costs to fix in place — almost always less than the rewrite you are being quoted.",[175,853,854],{},"Tell us what you are building and where you are stuck, and we will tell you which phases will be easy and which will hurt.",[856,857,858],"post-credits",{},[175,859,860,861,865],{},"Dima is Lead Flutter Developer at ",[396,862,864],{"href":863},"\u002F","Nerdy Production",", a Flutter-first agency that takes apps from discovery to the App Store across fintech, retail, and AI products.",{"title":867,"searchDepth":868,"depth":868,"links":869},"",2,[870,871,872,873,874,875,876,877,878,879,880],{"id":226,"depth":868,"text":227},{"id":420,"depth":868,"text":266},{"id":470,"depth":868,"text":285},{"id":510,"depth":868,"text":304},{"id":577,"depth":868,"text":323},{"id":617,"depth":868,"text":342},{"id":671,"depth":868,"text":361},{"id":711,"depth":868,"text":712},{"id":746,"depth":868,"text":747},{"id":799,"depth":868,"text":800},{"id":809,"depth":868,"text":810},"TL;DR. The Flutter app development process runs in seven phases: discovery and scoping, UX\u002FUI design, architecture and foundations, iterative development, QA and testing, release, and post-launch maintenance. What ties them together is that they are feedback loops, not a waterfall — design starts before discovery finishes, QA runs alongside the build rather than after it, and every two weeks you get something installable on your phone instead of a status report. The one rule we do not bend: the invariants come before the feature code. The state model, theme, error taxonomy, CI pipeline and test strategy are decided in week one, because every screen built afterwards either follows them or fights them. A typical build is 2–3 months for an  and 3–5 months for a full product, and launch is the middle of the process, not the end.","md",{"type":884,"src":885},"image","\u002Fblog\u002Fflutter-app-development-process.webp",{},"How a Flutter app actually gets built — discovery to release and maintenance, phase by phase, with the practices that keep it on track.","The Flutter App Development Process, Step by Step",true,"Discovery to App Store, phase by phase — how a Flutter build actually runs when it is short feedback loops instead of a waterfall.","\u002Fblog\u002Fflutter-app-development-process",{"title":169,"description":881},"flutter-app-development-process","blog\u002Fflutter-app-development-process","The actual process behind a Flutter build — discovery, design, architecture, iterative development, QA, release, and maintenance — run as short feedback loops rather than a waterfall. What happens in each phase, what you get out of it, who is in the room, how long it takes, and the specific places the process breaks.","2026-07-29T18:35:16Z",null,"5hvBCrshyZM1Quv115bsdnDlf0jsh3wVQCB5EOTDTwo",[900,956,1003,1053,1143,1195],{"id":901,"bio":902,"expertise":907,"extension":923,"links":924,"meta":928,"metaDescription":929,"name":934,"ogDescription":937,"photo":942,"role":943,"seniority":948,"skills":949,"slug":170,"specialization":950,"stem":170,"__hash__":955},"team_members\u002Fdima.yaml",{"en":903,"ru":904,"es":905,"nl":906},"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",[908,911,916,918],{"en":909,"ru":909,"es":910,"nl":909},"State management","Gestión de estado",{"en":912,"ru":913,"es":914,"nl":915},"Application architecture","Архитектура приложений","Arquitectura de aplicaciones","Applicatiearchitectuur",{"en":917,"ru":917,"es":917,"nl":917},"WebRTC",{"en":919,"ru":920,"es":921,"nl":922},"XMPP messaging","Обмен сообщениями по XMPP","Mensajería XMPP","Berichten via XMPP","yaml",[925],{"type":926,"address":927},"email","konopatov@nerdy.pro",{},{"en":930,"ru":931,"es":932,"nl":933},"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":935,"ru":936,"es":935,"nl":935},"Dima","Дима",{"en":938,"ru":939,"es":940,"nl":941},"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":944,"ru":945,"es":946,"nl":947},"Lead Flutter Developer","Ведущий Flutter-разработчик","Lead de desarrollo Flutter","Lead Flutter-developer","lead",[41,18,155,160,90,111,150,95],{"en":951,"ru":952,"es":953,"nl":954},"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":957,"bio":958,"expertise":963,"extension":923,"links":897,"meta":974,"metaDescription":975,"name":980,"ogDescription":983,"photo":988,"role":989,"seniority":994,"skills":995,"slug":996,"specialization":997,"stem":996,"__hash__":1002},"team_members\u002Fmasha.yaml",{"en":959,"ru":960,"es":961,"nl":962},"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",[964,969],{"en":965,"ru":966,"es":967,"nl":968},"UI\u002FUX design","UI\u002FUX-дизайн","Diseño UI\u002FUX","UI\u002FUX-ontwerp",{"en":970,"ru":971,"es":972,"nl":973},"Product copywriting","Продуктовый копирайтинг","Redacción de producto","Productteksten",{},{"en":976,"ru":977,"es":978,"nl":979},"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":981,"ru":982,"es":981,"nl":981},"Masha","Маша",{"en":984,"ru":985,"es":986,"nl":987},"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":990,"ru":991,"es":992,"nl":993},"Flutter Developer","Flutter-разработчик","Desarrolladora Flutter","Flutter-developer","middle",[41,18],"masha",{"en":998,"ru":999,"es":1000,"nl":1001},"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":1004,"bio":1005,"expertise":1010,"extension":923,"links":1021,"meta":1024,"metaDescription":1025,"name":1030,"ogDescription":1033,"photo":1038,"role":1039,"seniority":1044,"skills":1045,"slug":1046,"specialization":1047,"stem":1046,"__hash__":1052},"team_members\u002Fmaxim.yaml",{"en":1006,"ru":1007,"es":1008,"nl":1009},"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",[1011,1016],{"en":1012,"ru":1013,"es":1014,"nl":1015},"Automated testing","Автоматизированное тестирование","Testing automatizado","Geautomatiseerd testen",{"en":1017,"ru":1018,"es":1019,"nl":1020},"High-load backend systems","Высоконагруженные бэкенд-системы","Sistemas backend de alta carga","Backendsystemen met hoge belasting",[1022],{"type":926,"address":1023},"maxim@nerdy.pro",{},{"en":1026,"ru":1027,"es":1028,"nl":1029},"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":1031,"ru":1032,"es":1031,"nl":1031},"Maxim","Максим",{"en":1034,"ru":1035,"es":1036,"nl":1037},"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":1040,"ru":1041,"es":1042,"nl":1043},"Senior Software Engineer","Старший инженер-программист","Ingeniero de software senior","Senior software engineer","senior",[41,18,51,106,155,13,150],"maxim",{"en":1048,"ru":1049,"es":1050,"nl":1051},"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":1054,"bio":1055,"expertise":1060,"extension":923,"links":1102,"meta":1114,"metaDescription":1115,"name":1120,"ogDescription":1123,"photo":1128,"role":1129,"seniority":1134,"skills":1135,"slug":1136,"specialization":1137,"stem":1136,"__hash__":1142},"team_members\u002Fnixan.yaml",{"en":1056,"ru":1057,"es":1058,"nl":1059},"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",[1061,1066,1071,1076,1081,1086,1091,1096,1098,1100],{"en":1062,"ru":1063,"es":1064,"nl":1065},"iOS development","Разработка под iOS","Desarrollo iOS","iOS-ontwikkeling",{"en":1067,"ru":1068,"es":1069,"nl":1070},"Software architecture","Архитектура ПО","Arquitectura de software","Softwarearchitectuur",{"en":1072,"ru":1073,"es":1074,"nl":1075},"Engineering team leadership","Руководство инженерными командами","Liderazgo de equipos de ingeniería","Leidinggeven aan engineeringteams",{"en":1077,"ru":1078,"es":1079,"nl":1080},"Payment systems","Платёжные системы","Sistemas de pago","Betaalsystemen",{"en":1082,"ru":1083,"es":1084,"nl":1085},"Card processing","Карточный процессинг","Procesamiento de tarjetas","Kaartverwerking",{"en":1087,"ru":1088,"es":1089,"nl":1090},"PCI-DSS compliance","Соответствие PCI-DSS","Cumplimiento de PCI-DSS","Naleving van PCI-DSS",{"en":1092,"ru":1093,"es":1094,"nl":1095},"NFC and contactless payments","NFC и бесконтактные платежи","NFC y pagos contactless","NFC en contactloos betalen",{"en":1097,"ru":1097,"es":1097,"nl":1097},"Host Card Emulation",{"en":1099,"ru":1099,"es":1099,"nl":1099},"EMV Contactless",{"en":1101,"ru":1101,"es":1101,"nl":1101},"AOSP",[1103,1106,1109,1112],{"type":1104,"url":1105},"github","https:\u002F\u002Fgithub.com\u002Fthenixan",{"type":1107,"url":1108},"linkedin","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fthenixan\u002F",{"type":1110,"url":1111},"telegram","https:\u002F\u002Ft.me\u002Fthenixan",{"type":926,"address":1113},"nixan@nerdy.pro",{},{"en":1116,"ru":1117,"es":1118,"nl":1119},"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":1121,"ru":1122,"es":1121,"nl":1121},"Ilya Nixan","Илья Никсан",{"en":1124,"ru":1125,"es":1126,"nl":1127},"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":1130,"ru":1131,"es":1132,"nl":1133},"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":1138,"ru":1139,"es":1140,"nl":1141},"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":1144,"bio":1145,"expertise":1150,"extension":923,"links":1162,"meta":1167,"metaDescription":1168,"name":1173,"ogDescription":1176,"photo":1181,"role":1182,"seniority":1044,"skills":1187,"slug":1188,"specialization":1189,"stem":1188,"__hash__":1194},"team_members\u002Froma.yaml",{"en":1146,"ru":1147,"es":1148,"nl":1149},"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",[1151,1152,1157],{"en":1062,"ru":1063,"es":1064,"nl":1065},{"en":1153,"ru":1154,"es":1155,"nl":1156},"Applied AI","Прикладной AI","IA aplicada","Toegepaste AI",{"en":1158,"ru":1159,"es":1160,"nl":1161},"ERP and CRM systems","ERP- и CRM-системы","Sistemas ERP y CRM","ERP- en CRM-systemen",[1163,1165],{"type":1107,"url":1164},"https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fromanbatler\u002F",{"type":926,"address":1166},"roma@nerdy.pro",{},{"en":1169,"ru":1170,"es":1171,"nl":1172},"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":1174,"ru":1175,"es":1174,"nl":1174},"Roman","Рома",{"en":1177,"ru":1178,"es":1179,"nl":1180},"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":1183,"ru":1184,"es":1185,"nl":1186},"Senior Mobile Developer","Старший мобильный разработчик","Desarrollador móvil senior","Senior mobiele developer",[7,41,18,141,146,106],"roma",{"en":1190,"ru":1191,"es":1192,"nl":1193},"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":1196,"bio":1197,"expertise":1202,"extension":923,"links":897,"meta":1213,"metaDescription":1214,"name":1219,"ogDescription":1222,"photo":1227,"role":1228,"seniority":1044,"skills":1233,"slug":1234,"specialization":1235,"stem":1234,"__hash__":1240},"team_members\u002Fxsox.yaml",{"en":1198,"ru":1199,"es":1200,"nl":1201},"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",[1203,1208],{"en":1204,"ru":1205,"es":1206,"nl":1207},"API design","Проектирование API","Diseño de APIs","API-ontwerp",{"en":1209,"ru":1210,"es":1211,"nl":1212},"Data modelling","Моделирование данных","Modelado de datos","Datamodellering",{},{"en":1215,"ru":1216,"es":1217,"nl":1218},"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":1220,"ru":1221,"es":1220,"nl":1220},"Eugene Xsox","Женя Xsox",{"en":1223,"ru":1224,"es":1225,"nl":1226},"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":1229,"ru":1230,"es":1231,"nl":1232},"Senior Backend Developer","Старший бэкенд-разработчик","Desarrollador backend senior","Senior backenddeveloper",[106,24,41,18,155,160,90,150],"xsox",{"en":1236,"ru":1237,"es":1238,"nl":1239},"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",[1242,1251,1258,1263,1273],{"id":1243,"extension":923,"meta":1244,"name":1245,"slug":1249,"stem":1249,"__hash__":1250},"blog_topics\u002Fcybersecurity.yaml",{},{"en":1246,"ru":1247,"es":1248,"nl":1246},"Cybersecurity","Кибербезопасность","Ciberseguridad","cybersecurity","kt1rdsMy5W4b9MvGHm6mZVCr0inHidEuqaosPYmmk4E",{"id":1252,"extension":923,"meta":1253,"name":1254,"slug":1256,"stem":1256,"__hash__":1257},"blog_topics\u002Fdevops.yaml",{},{"en":1255,"ru":1255,"es":1255,"nl":1255},"DevOps","devops","D3mxlZuFHKCGeszKZuWCiQmHmP5EiCvzg1qEAIQhnyU",{"id":1259,"extension":923,"meta":1260,"name":1261,"slug":41,"stem":41,"__hash__":1262},"blog_topics\u002Fflutter.yaml",{},{"en":39,"ru":39,"es":39,"nl":39},"OOeALAmwFuEqByuJvTGk4g15FIHENPfYMdpfZh_HTAE",{"id":1264,"extension":923,"meta":1265,"name":1266,"slug":1271,"stem":1271,"__hash__":1272},"blog_topics\u002Ffor-founders.yaml",{},{"en":1267,"ru":1268,"es":1269,"nl":1270},"For Founders","Для основателей","Para fundadores","Voor oprichters","for-founders","lp2u6Ol2qF4DGxpB83HxbbGzWioT-e40mJhD4lr28-U",{"id":1274,"extension":923,"meta":1275,"name":1276,"slug":1281,"stem":1281,"__hash__":1282},"blog_topics\u002Fsoftware-engineering.yaml",{},{"en":1277,"ru":1278,"es":1279,"nl":1280},"Software Engineering","Разработка ПО","Ingeniería de software","Software-engineering","software-engineering","aZMb3aUDptoFQk_cEE6l5H4wrYcgZuBYUubmKqOAaaU",{"data":1284,"body":1285},{},{"type":1286,"children":1287},"root",[1288,1310],{"type":1289,"tag":175,"props":1290,"children":1291},"element",{},[1292,1295,1300,1302,1308],{"type":1293,"value":1294},"text","Dima has been building with ",{"type":1289,"tag":396,"props":1296,"children":1298},{"href":1297},"\u002Ftechnologies\u002Fflutter",[1299],{"type":1293,"value":39},{"type":1293,"value":1301}," since 2021, and specializes in ",{"type":1289,"tag":216,"props":1303,"children":1305},{"slug":1304},"state-management",[1306],{"type":1293,"value":1307},"state management",{"type":1293,"value":1309}," and app architecture.",{"type":1289,"tag":175,"props":1311,"children":1312},{},[1313,1315,1319,1321,1325],{"type":1293,"value":1314},"He has hands-on experience with real-time communication protocols — ",{"type":1289,"tag":216,"props":1316,"children":1318},{"slug":1317},"webrtc",[],{"type":1293,"value":1320}," for audio and video, and ",{"type":1289,"tag":216,"props":1322,"children":1324},{"slug":1323},"xmpp",[],{"type":1293,"value":1326}," for messaging — which makes him comfortable with the network-heavy, stateful features many teams struggle to get right.",[1328,1342,1355,1370,1384,1398,1414,1426,1440,1453,1467,1480,1495,1508,1525,1537,1548,1558,1571,1581,1592,1607,1616,1629,1642,1649,1659,1671,1682,1697,1709,1722,1734,1746,1758,1770,1781,1792,1803,1814,1826,1836,1847,1860,1872,1880,1890,1902,1912,1923,1934,1943,1954],{"slug":1329,"term":1101,"definition":1330,"category":1331,"aliases":1332,"links":1334,"related":1338,"readMore":-1,"target":1340,"hasArticle":1341},"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",[1333],"Android Open Source Project",[1335],{"kind":1336,"url":1337},"website","https:\u002F\u002Fsource.android.com\u002F",[1339],"host-card-emulation","\u002Fglossary#aosp",false,{"slug":1343,"term":1344,"definition":1345,"category":1331,"aliases":1346,"links":1347,"related":1351,"readMore":-1,"target":1354,"hasArticle":1341},"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.",[],[1348],{"kind":1349,"url":1350},"documentation","https:\u002F\u002Fdeveloper.apple.com\u002Fapp-clips\u002F",[1352,1353],"deep-linking","install-referrer","\u002Fglossary#app-clips",{"slug":1356,"term":1357,"definition":1358,"category":1331,"aliases":1359,"links":1360,"related":1366,"readMore":-1,"target":1369,"hasArticle":1341},"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.",[],[1361,1363],{"kind":1336,"url":1362},"https:\u002F\u002Fcloud.google.com\u002Fbigquery",{"kind":1364,"url":1365},"wikipedia","https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FBigQuery",[1367,1368],"object-storage","elasticsearch","\u002Fglossary#bigquery",{"slug":1371,"term":1372,"definition":1373,"category":1374,"aliases":1375,"links":1379,"related":1382,"readMore":-1,"target":1383,"hasArticle":1341},"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",[1376,1377,1378],"CI","continuous integration","continuous delivery",[1380],{"kind":1364,"url":1381},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FCI\u002FCD",[],"\u002Fglossary#ci-cd",{"slug":1385,"term":1386,"definition":1387,"category":1388,"aliases":1389,"links":1391,"related":1394,"readMore":-1,"target":1397,"hasArticle":1341},"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",[1390],"Create, Read, Update, Delete",[1392],{"kind":1364,"url":1393},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FCreate,_read,_update_and_delete",[1395,1396],"rest","graphql","\u002Fglossary#crud",{"slug":1399,"term":1400,"definition":1401,"category":1388,"aliases":1402,"links":1407,"related":1410,"readMore":-1,"target":1413,"hasArticle":1341},"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.",[1403,1404,1405,1406],"image registry","Docker registry","GHCR","ghcr.io",[1408],{"kind":1349,"url":1409},"https:\u002F\u002Fdocs.github.com\u002Fen\u002Fpackages\u002Fworking-with-a-github-packages-registry\u002Fworking-with-the-container-registry",[1411,1412],"dev-container","multi-arch-image","\u002Fglossary#container-registry",{"slug":1352,"term":1415,"definition":1416,"category":1331,"aliases":1417,"links":1421,"related":1424,"readMore":1425,"target":1425,"hasArticle":889},"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.",[1418,1419,1420],"deferred deep linking","universal links","Android App Links",[1422],{"kind":1364,"url":1423},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FMobile_deep_linking",[1343,1353],"\u002Fglossary\u002Fdeep-linking",{"slug":1411,"term":1427,"definition":1428,"category":1374,"aliases":1429,"links":1433,"related":1438,"readMore":-1,"target":1439,"hasArticle":1341},"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.",[1430,1431,1432],"devcontainer.json","Dev Containers","VS Code Dev Containers",[1434,1436],{"kind":1336,"url":1435},"https:\u002F\u002Fcontainers.dev\u002F",{"kind":1349,"url":1437},"https:\u002F\u002Fcode.visualstudio.com\u002Fdocs\u002Fdevcontainers\u002Fcontainers",[1399],"\u002Fglossary#dev-container",{"slug":1368,"term":1441,"definition":1442,"category":1331,"aliases":1443,"links":1446,"related":1451,"readMore":-1,"target":1452,"hasArticle":1341},"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\".",[1444,1445],"Elastic","ELK",[1447,1449],{"kind":1336,"url":1448},"https:\u002F\u002Fwww.elastic.co\u002Felasticsearch",{"kind":1364,"url":1450},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FElasticsearch",[1356],"\u002Fglossary#elasticsearch",{"slug":1454,"term":1455,"definition":1456,"category":1388,"aliases":1457,"links":1460,"related":1463,"readMore":-1,"target":1466,"hasArticle":1341},"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.",[1458,1459],"E2EE","end-to-end encrypted",[1461],{"kind":1364,"url":1462},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FEnd-to-end_encryption",[1464,1465],"tls","jwt","\u002Fglossary#end-to-end-encryption",{"slug":1468,"term":1469,"definition":1470,"category":1388,"aliases":1471,"links":1474,"related":1475,"readMore":-1,"target":1479,"hasArticle":1341},"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.",[1472,1473],"fanout","broadcast",[],[1476,1477,1478],"websocket","pub-sub","server-sent-events","\u002Fglossary#fan-out",{"slug":1481,"term":1482,"definition":1483,"category":1374,"aliases":1484,"links":1488,"related":1491,"readMore":-1,"target":1494,"hasArticle":1341},"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.",[1485,1486,1487],"feature flag","feature toggle","feature gating",[1489],{"kind":1364,"url":1490},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FFeature_toggle",[698,1492,1493],"white-label","multi-tenancy","\u002Fglossary#feature-flags",{"slug":1496,"term":1497,"definition":1498,"category":1388,"aliases":1499,"links":1503,"related":1506,"readMore":-1,"target":1507,"hasArticle":1341},"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.",[1500,1501,1502],"IEEE 754","double","floating-point arithmetic",[1504],{"kind":1364,"url":1505},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FIEEE_754",[],"\u002Fglossary#floating-point",{"slug":1509,"term":1510,"definition":1511,"category":1374,"aliases":1512,"links":1515,"related":1520,"readMore":-1,"target":1524,"hasArticle":1341},"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.",[1513,1514],"General Data Protection Regulation","data protection",[1516,1518],{"kind":1336,"url":1517},"https:\u002F\u002Fgdpr.eu\u002F",{"kind":1364,"url":1519},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FGeneral_Data_Protection_Regulation",[1521,1522,1523],"pci-dss","soc-2","hipaa","\u002Fglossary#gdpr",{"slug":638,"term":1526,"definition":1527,"category":1374,"aliases":1528,"links":1532,"related":1535,"readMore":-1,"target":1536,"hasArticle":1341},"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.",[1529,1530,1531],"golden tests","screenshot test","snapshot test",[1533],{"kind":1349,"url":1534},"https:\u002F\u002Fapi.flutter.dev\u002Fflutter\u002Fflutter_test\u002FmatchesGoldenFile.html",[1371],"\u002Fglossary#golden-test",{"slug":1396,"term":1538,"definition":1539,"category":1388,"aliases":1540,"links":1541,"related":1546,"readMore":-1,"target":1547,"hasArticle":1341},"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.",[],[1542,1544],{"kind":1336,"url":1543},"https:\u002F\u002Fgraphql.org\u002F",{"kind":1364,"url":1545},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FGraphQL",[1395],"\u002Fglossary#graphql",{"slug":1523,"term":1549,"definition":1550,"category":1374,"aliases":1551,"links":1553,"related":1556,"readMore":-1,"target":1557,"hasArticle":1341},"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.",[1552],"Health Insurance Portability and Accountability Act",[1554],{"kind":1364,"url":1555},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FHealth_Insurance_Portability_and_Accountability_Act",[1521,1509,1522],"\u002Fglossary#hipaa",{"slug":1559,"term":1560,"definition":1561,"category":1388,"aliases":1562,"links":1565,"related":1568,"readMore":-1,"target":1570,"hasArticle":1341},"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.",[1563,1564],"headless content management system","content API",[1566],{"kind":1364,"url":1567},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FHeadless_content_management_system",[1569,1395],"server-side-rendering","\u002Fglossary#headless-cms",{"slug":1339,"term":1097,"definition":1572,"category":1331,"aliases":1573,"links":1576,"related":1579,"readMore":-1,"target":1580,"hasArticle":1341},"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.",[1574,1099,1575],"HCE","contactless payments",[1577],{"kind":1349,"url":1578},"https:\u002F\u002Fdeveloper.android.com\u002Fdevelop\u002Fconnectivity\u002Fnfc\u002Fhce",[1521,1329],"\u002Fglossary#host-card-emulation",{"slug":1582,"term":1583,"definition":1584,"category":1331,"aliases":1585,"links":1586,"related":1589,"readMore":-1,"target":1591,"hasArticle":1341},"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.",[],[1587],{"kind":1349,"url":1588},"https:\u002F\u002Fdocs.flutter.dev\u002Fperf\u002Fimpeller",[1590],"skia","\u002Fglossary#impeller",{"slug":1593,"term":1594,"definition":1595,"category":1596,"aliases":1597,"links":1601,"related":1604,"readMore":-1,"target":1606,"hasArticle":1341},"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",[1598,1599,1600],"IAP","in-app purchases","in-app subscription",[1602],{"kind":1349,"url":1603},"https:\u002F\u002Fdeveloper.apple.com\u002Fin-app-purchase\u002F",[1605],"product-market-fit","\u002Fglossary#in-app-purchase",{"slug":1353,"term":1608,"definition":1609,"category":1331,"aliases":1610,"links":1611,"related":1614,"readMore":-1,"target":1615,"hasArticle":1341},"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.",[],[1612],{"kind":1349,"url":1613},"https:\u002F\u002Fdeveloper.android.com\u002Fgoogle\u002Fplay\u002Finstallreferrer",[1352,1343],"\u002Fglossary#install-referrer",{"slug":1465,"term":1617,"definition":1618,"category":1619,"aliases":1620,"links":1622,"related":1627,"readMore":-1,"target":1628,"hasArticle":1341},"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",[1621],"JSON Web Token",[1623,1625],{"kind":1336,"url":1624},"https:\u002F\u002Fjwt.io\u002F",{"kind":1364,"url":1626},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FJSON_Web_Token",[1521],"\u002Fglossary#jwt",{"slug":1630,"term":1631,"definition":1632,"category":1374,"aliases":1633,"links":1637,"related":1640,"readMore":-1,"target":1641,"hasArticle":1341},"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.",[1634,1635,1636],"Know Your Customer","AML","KYC\u002FAML",[1638],{"kind":1364,"url":1639},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FKnow_your_customer",[1521,1509],"\u002Fglossary#kyc",{"slug":76,"term":74,"definition":1643,"category":1331,"aliases":1644,"links":1646,"related":1647,"readMore":1648,"target":1648,"hasArticle":1341},"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.",[1645],"KMP",[],[],"\u002Ftechnologies\u002Fkmp",{"slug":218,"term":1650,"definition":1651,"category":1596,"aliases":1652,"links":1654,"related":1657,"readMore":-1,"target":1658,"hasArticle":1341},"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.",[1653],"minimum viable product",[1655],{"kind":1364,"url":1656},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FMinimum_viable_product",[1492],"\u002Fglossary#mvp",{"slug":1412,"term":1660,"definition":1661,"category":1388,"aliases":1662,"links":1666,"related":1669,"readMore":-1,"target":1670,"hasArticle":1341},"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.",[1663,1664,1665],"multi-arch build","multi-platform image","linux\u002Famd64 + linux\u002Farm64",[1667],{"kind":1349,"url":1668},"https:\u002F\u002Fdocs.docker.com\u002Fbuild\u002Fbuilding\u002Fmulti-platform\u002F",[1399],"\u002Fglossary#multi-arch-image",{"slug":1493,"term":1672,"definition":1673,"category":1388,"aliases":1674,"links":1677,"related":1680,"readMore":-1,"target":1681,"hasArticle":1341},"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.",[1675,1676],"multi-tenant","tenant",[1678],{"kind":1364,"url":1679},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FMultitenancy",[1492,1481],"\u002Fglossary#multi-tenancy",{"slug":1683,"term":1684,"definition":1685,"category":1619,"aliases":1686,"links":1690,"related":1695,"readMore":-1,"target":1696,"hasArticle":1341},"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.",[1687,1688,1689],"OAuth 2.0","social login","Sign in with Apple",[1691,1693],{"kind":1336,"url":1692},"https:\u002F\u002Foauth.net\u002F2\u002F",{"kind":1364,"url":1694},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FOAuth",[1465],"\u002Fglossary#oauth",{"slug":1367,"term":1698,"definition":1699,"category":1388,"aliases":1700,"links":1704,"related":1707,"readMore":-1,"target":1708,"hasArticle":1341},"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.",[1701,1702,1703],"S3","S3-compatible storage","blob storage",[1705],{"kind":1364,"url":1706},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FObject_storage",[1356],"\u002Fglossary#object-storage",{"slug":1521,"term":1710,"definition":1711,"category":1374,"aliases":1712,"links":1715,"related":1720,"readMore":-1,"target":1721,"hasArticle":1341},"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.",[1713,1714],"PCI DSS","Payment Card Industry Data Security Standard",[1716,1718],{"kind":1336,"url":1717},"https:\u002F\u002Fwww.pcisecuritystandards.org\u002F",{"kind":1364,"url":1719},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FPayment_Card_Industry_Data_Security_Standard",[1465],"\u002Fglossary#pci-dss",{"slug":1723,"term":1724,"definition":1725,"category":1331,"aliases":1726,"links":1729,"related":1732,"readMore":-1,"target":1733,"hasArticle":1341},"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.",[1727,1728],"platform channel","method channel",[1730],{"kind":1349,"url":1731},"https:\u002F\u002Fdocs.flutter.dev\u002Fplatform-integration\u002Fplatform-channels",[76],"\u002Fglossary#platform-channels",{"slug":1735,"term":1736,"definition":1737,"category":1619,"aliases":1738,"links":1741,"related":1744,"readMore":-1,"target":1745,"hasArticle":1341},"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.",[1739,1740],"PQC","post-quantum crypto",[1742],{"kind":1364,"url":1743},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FPost-quantum_cryptography",[1464,1454],"\u002Fglossary#post-quantum-cryptography",{"slug":1605,"term":1747,"definition":1748,"category":1596,"aliases":1749,"links":1752,"related":1755,"readMore":-1,"target":1757,"hasArticle":1341},"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.",[1750,1751],"PMF","product\u002Fmarket fit",[1753],{"kind":1364,"url":1754},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FProduct-market_fit",[218,1756],"time-to-market","\u002Fglossary#product-market-fit",{"slug":1759,"term":1760,"definition":1761,"category":1374,"aliases":1762,"links":1764,"related":1767,"readMore":-1,"target":1769,"hasArticle":1341},"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.",[1763],"injection attack",[1765],{"kind":1364,"url":1766},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FPrompt_injection",[1768],"rate-limiting","\u002Fglossary#prompt-injection",{"slug":1477,"term":1771,"definition":1772,"category":1388,"aliases":1773,"links":1776,"related":1779,"readMore":-1,"target":1780,"hasArticle":1341},"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.",[1774,1775],"publish\u002Fsubscribe","Google Cloud Pub\u002FSub",[1777],{"kind":1364,"url":1778},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FPublish%E2%80%93subscribe_pattern",[],"\u002Fglossary#pub-sub",{"slug":1395,"term":1782,"definition":1783,"category":1388,"aliases":1784,"links":1787,"related":1790,"readMore":-1,"target":1791,"hasArticle":1341},"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.",[1785,1786],"REST API","Representational State Transfer",[1788],{"kind":1364,"url":1789},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FREST",[1476,1478],"\u002Fglossary#rest",{"slug":1768,"term":1793,"definition":1794,"category":1374,"aliases":1795,"links":1798,"related":1801,"readMore":-1,"target":1802,"hasArticle":1341},"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.",[1796,1797],"rate limit","throttling",[1799],{"kind":1364,"url":1800},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FRate_limiting",[1759],"\u002Fglossary#rate-limiting",{"slug":1522,"term":1804,"definition":1805,"category":1374,"aliases":1806,"links":1809,"related":1812,"readMore":-1,"target":1813,"hasArticle":1341},"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.",[1807,1808],"SOC2","System and Organization Controls",[1810],{"kind":1364,"url":1811},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FSystem_and_Organization_Controls",[1521,1509,1523],"\u002Fglossary#soc-2",{"slug":1815,"term":1816,"definition":1817,"category":1596,"aliases":1818,"links":1821,"related":1824,"readMore":-1,"target":1825,"hasArticle":1341},"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.",[1819,1820],"Software as a Service","software-as-a-service",[1822],{"kind":1364,"url":1823},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FSoftware_as_a_service",[1493,1492],"\u002Fglossary#saas",{"slug":1478,"term":1827,"definition":1828,"category":1619,"aliases":1829,"links":1831,"related":1834,"readMore":-1,"target":1835,"hasArticle":1341},"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.",[1830],"SSE",[1832],{"kind":1364,"url":1833},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FServer-sent_events",[1476,1395],"\u002Fglossary#server-sent-events",{"slug":1569,"term":1837,"definition":1838,"category":1388,"aliases":1839,"links":1842,"related":1845,"readMore":-1,"target":1846,"hasArticle":1341},"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.",[1840,1841],"SSR","server-rendered",[1843],{"kind":1364,"url":1844},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FServer-side_scripting",[1559],"\u002Fglossary#server-side-rendering",{"slug":1590,"term":1848,"definition":1849,"category":1331,"aliases":1850,"links":1853,"related":1858,"readMore":-1,"target":1859,"hasArticle":1341},"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.",[1851,1852],"Skia Graphics Engine","skia-safe",[1854,1856],{"kind":1336,"url":1855},"https:\u002F\u002Fskia.org\u002F",{"kind":1364,"url":1857},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FSkia_Graphics_Engine",[1582],"\u002Fglossary#skia",{"slug":1861,"term":1862,"definition":1863,"category":1596,"aliases":1864,"links":1868,"related":1869,"readMore":-1,"target":1871,"hasArticle":1341},"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.",[1865,1866,1867],"team augmentation","dedicated developers","outstaffing",[],[1870,1756],"total-cost-of-ownership","\u002Fglossary#staff-augmentation",{"slug":698,"term":699,"definition":1873,"category":1374,"aliases":1874,"links":1877,"related":1878,"readMore":-1,"target":1879,"hasArticle":1341},"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.",[1875,1876],"phased release","canary release",[],[1481,1371],"\u002Fglossary#staged-rollout",{"slug":1304,"term":909,"definition":1881,"category":1388,"aliases":1882,"links":1885,"related":1888,"readMore":-1,"target":1889,"hasArticle":1341},"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.",[1307,1883,1884],"BLoC","Riverpod",[1886],{"kind":1349,"url":1887},"https:\u002F\u002Fdocs.flutter.dev\u002Fdata-and-backend\u002Fstate-mgmt\u002Foptions",[638],"\u002Fglossary#state-management",{"slug":1464,"term":1891,"definition":1892,"category":1619,"aliases":1893,"links":1897,"related":1900,"readMore":-1,"target":1901,"hasArticle":1341},"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.",[1894,1895,1896],"SSL","HTTPS","Transport Layer Security",[1898],{"kind":1364,"url":1899},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FTransport_Layer_Security",[1454,1465],"\u002Fglossary#tls",{"slug":1756,"term":1903,"definition":1904,"category":1596,"aliases":1905,"links":1907,"related":1910,"readMore":-1,"target":1911,"hasArticle":1341},"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.",[1906,1756],"TTM",[1908],{"kind":1364,"url":1909},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FTime_to_market",[218,1870],"\u002Fglossary#time-to-market",{"slug":1870,"term":1913,"definition":1914,"category":1596,"aliases":1915,"links":1918,"related":1921,"readMore":-1,"target":1922,"hasArticle":1341},"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.",[1916,1917],"TCO","cost of ownership",[1919],{"kind":1364,"url":1920},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FTotal_cost_of_ownership",[1756],"\u002Fglossary#total-cost-of-ownership",{"slug":1317,"term":917,"definition":1924,"category":1619,"aliases":1925,"links":1927,"related":1932,"readMore":-1,"target":1933,"hasArticle":1341},"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.",[1926],"Web Real-Time Communication",[1928,1930],{"kind":1336,"url":1929},"https:\u002F\u002Fwebrtc.org\u002F",{"kind":1364,"url":1931},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FWebRTC",[1323,1476],"\u002Fglossary#webrtc",{"slug":1476,"term":1935,"definition":1936,"category":1619,"aliases":1937,"links":1938,"related":1941,"readMore":-1,"target":1942,"hasArticle":1341},"WebSocket","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.",[],[1939],{"kind":1364,"url":1940},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FWebSocket",[1478,1395],"\u002Fglossary#websocket",{"slug":1492,"term":1944,"definition":1945,"category":1596,"aliases":1946,"links":1949,"related":1952,"readMore":1953,"target":1953,"hasArticle":889},"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.",[1947,1948],"white label","multi-tenant app",[1950],{"kind":1364,"url":1951},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FWhite-label_product",[218],"\u002Fglossary\u002Fwhite-label",{"slug":1323,"term":1955,"definition":1956,"category":1619,"aliases":1957,"links":1960,"related":1965,"readMore":-1,"target":1966,"hasArticle":1341},"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.",[1958,1959],"Jabber","Extensible Messaging and Presence Protocol",[1961,1963],{"kind":1336,"url":1962},"https:\u002F\u002Fxmpp.org\u002F",{"kind":1364,"url":1964},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FXMPP",[1317,1476],"\u002Fglossary#xmpp"]