[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"technologies":3,"\u002Fblog\u002Fhire-flutter-developers-2026":167,"team-members":845,"blog-topics":1187,"mdc--12ftuw-key":1229,"glossary":1344},[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":827,"extension":828,"hero":829,"meta":832,"metaDescription":833,"metaTitle":834,"navigation":835,"ogDescription":836,"path":837,"seo":838,"slug":839,"stem":840,"summary":841,"timestamp":842,"topic":41,"updated":843,"__hash__":844},"blog_en\u002Fblog\u002Fhire-flutter-developers-2026.md","Hire Flutter Developers in 2026: In-House vs Agency vs Staff Augmentation","nixan",{"type":172,"value":173,"toc":813},"minimark",[174,191,194,199,340,344,355,361,401,411,421,434,438,445,448,455,459,462,469,499,502,506,514,521,524,536,540,543,563,566,570,573,583,612,622,626,629,680,691,695,698,738,741,745,769,773,776,794,802],[175,176,177,181,182,185,186,190],"p",{},[178,179,180],"strong",{},"TL;DR."," There are three ways to hire Flutter talent in 2026, and the right one depends on what you're actually buying. ",[178,183,184],{},"Hire in-house when Flutter is core to your product for years and you want to own the code and the knowledge. Hire an agency when you need a defined product shipped fast with the least management overhead. Use staff augmentation when you already have a team that can manage engineers and just need more Flutter capacity."," The one-line decision rule: ",[187,188,189],"em",{},"if the mobile app is the business, build in-house; if you need it built, hire an agency; if you need it built faster, augment your team."," Everything below is the detail behind that sentence — real 2026 rate ranges, hidden costs, and a checklist for vetting whoever you hire.",[175,192,193],{},"We run a Flutter-first agency, we place engineers into client teams, and we've watched all three models succeed and fail up close. This post is the honest version, including the parts where the answer is \"don't hire us.\"",[195,196,198],"h2",{"id":197},"the-three-models-at-a-glance","The three models at a glance",[200,201,202,220],"table",{},[203,204,205],"thead",{},[206,207,208,211,214,217],"tr",{},[209,210],"th",{},[209,212,213],{},"In-house",[209,215,216],{},"Agency",[209,218,219],{},"Staff augmentation",[221,222,223,240,256,272,288,308,324],"tbody",{},[206,224,225,231,234,237],{},[226,227,228],"td",{},[178,229,230],{},"Upfront cost",[226,232,233],{},"Highest — recruiting fees, salaries, benefits, equipment before a line ships",[226,235,236],{},"Medium — scoped project fee, predictable",[226,238,239],{},"Low — pay per engineer, per month, start\u002Fstop fast",[206,241,242,247,250,253],{},[226,243,244],{},[178,245,246],{},"Time-to-productive",[226,248,249],{},"Slowest — 2–4 months to hire, then ramp",[226,251,252],{},"Fastest for a whole product — team is pre-formed",[226,254,255],{},"Fast — days to a couple of weeks per engineer",[206,257,258,263,266,269],{},[226,259,260],{},[178,261,262],{},"Management overhead",[226,264,265],{},"High — you own hiring, retention, career growth, sprint planning",[226,267,268],{},"Lowest — the agency manages delivery",[226,270,271],{},"Medium — you manage the engineers day-to-day",[206,273,274,279,282,285],{},[226,275,276],{},[178,277,278],{},"Flexibility \u002F scaling",[226,280,281],{},"Low — hiring and firing are slow and expensive",[226,283,284],{},"Medium — scope up\u002Fdown at contract boundaries",[226,286,287],{},"Highest — add or drop engineers month to month",[206,289,290,295,298,301],{},[226,291,292],{},[178,293,294],{},"Code ownership & knowledge retention",[226,296,297],{},"Best — knowledge stays in the building",[226,299,300],{},"Weakest by default — knowledge can walk out at handoff",[226,302,303,304,307],{},"Strong — code and context live in ",[187,305,306],{},"your"," repo and team",[206,309,310,315,318,321],{},[226,311,312],{},[178,313,314],{},"Best-fit scenario",[226,316,317],{},"Flutter is core product, multi-year roadmap",[226,319,320],{},"Defined product, fixed deadline, minimal internal capacity",[226,322,323],{},"Existing team needs more Flutter throughput now",[206,325,326,331,334,337],{},[226,327,328],{},[178,329,330],{},"Biggest risk",[226,332,333],{},"Slow, expensive, and you own a bad hire",[226,335,336],{},"Lock-in and a knowledge cliff at handoff",[226,338,339],{},"You still have to manage them — augmentation isn't autopilot",[195,341,343],{"id":342},"what-does-it-actually-cost-to-hire-a-flutter-developer-in-2026","What does it actually cost to hire a Flutter developer in 2026?",[175,345,346,347,350,351,354],{},"Cost depends more on ",[187,348,349],{},"where"," and ",[187,352,353],{},"how"," you hire than on the framework. Here are the ranges we see in the market in 2026.",[175,356,357,360],{},[178,358,359],{},"Agency (blended hourly, by region)."," This is the all-in rate for a team that includes engineering, project management, and usually design:",[362,363,364,376,384,392],"ul",{},[365,366,367,370,371,375],"li",{},[178,368,369],{},"US-based agencies:"," ",[372,373],"price",{":value-usd":374},"{\"min\":150,\"max\":250}","\u002Fhour",[365,377,378,370,381,375],{},[178,379,380],{},"Western Europe (UK, Germany, Netherlands):",[372,382],{":value-usd":383},"{\"min\":100,\"max\":180}",[365,385,386,370,389,375],{},[178,387,388],{},"Eastern Europe:",[372,390],{":value-usd":391},"{\"min\":50,\"max\":95}",[365,393,394,370,397,400],{},[178,395,396],{},"South\u002FSoutheast Asia:",[372,398],{":value-usd":399},"{\"min\":25,\"max\":55}","\u002Fhour (wider quality variance)",[175,402,403,406,407,410],{},[178,404,405],{},"In-house (annual salary, typical 2026 market ranges)."," A senior Flutter engineer costs roughly $120k–$180k+ in the US, €60k–€100k in Western Europe, and $35k–$70k in Eastern Europe. Then multiply by ",[178,408,409],{},"1.25–1.4×"," for the fully loaded cost — payroll taxes, benefits, equipment, software, and office or remote overhead. A $150k salary is a ~$190k cost. On top of that, budget a one-time recruiting cost of 15–25% of first-year salary if you use an agency or in-house recruiter.",[175,412,413,416,417,420],{},[178,414,415],{},"Staff augmentation (per engineer, monthly)."," Augmentation typically lands ",[178,418,419],{},"10–30% below"," a full agency project rate for the same seniority, because you're buying the engineer's time, not the whole delivery wrapper (PM, QA lead, design). You avoid recruiting fees and long-term employment liability entirely — you pay a monthly rate and can stop when the work is done.",[175,422,423,424,427,428,433],{},"One number holds across all three models: ",[178,425,426],{},"Flutter cuts build cost roughly 30–40% versus two separate native apps",", because one codebase covers iOS, Android, and often web. That saving is the same whoever you hire — it's a property of the framework, not the hiring model. If you're pricing an actual build, we broke the whole thing down by tier in ",[429,430,432],"a",{"href":431},"\u002Fblog\u002Fflutter-app-development-cost-2026","Flutter App Development Cost in 2026",".",[195,435,437],{"id":436},"when-does-hiring-in-house-make-sense","When does hiring in-house make sense?",[175,439,440,441,444],{},"Hire in-house when the mobile app ",[187,442,443],{},"is"," the product, not a project — when your roadmap runs for years, the app is where your competitive advantage lives, and you'll be shipping continuously long after v1. You want that knowledge inside the building.",[175,446,447],{},"In-house wins on the things that compound: institutional memory, deep product context, and engineers who care because it's their product too. Nobody understands the weird edge case in your onboarding flow better than the person who's been maintaining it for two years.",[175,449,450,451,454],{},"The catch is that in-house is the slowest and most expensive way to ",[187,452,453],{},"start",". You're paying recruiting fees, salaries, and benefits for months before meaningful code ships, and a single bad senior hire can set you back a full quarter. Build in-house when you can afford to optimize for the long game over the fast start.",[195,456,458],{"id":457},"when-is-an-agency-the-right-call","When is an agency the right call?",[175,460,461],{},"Hire an agency when you have a defined product to ship, a deadline, and little internal capacity to manage a build yourself. A good agency is a pre-assembled team — engineers, a project manager, a designer, QA — that you point at a scope and get a shipped app back, without hiring anyone yourself.",[175,463,464,465,468],{},"The agency model's real value isn't the code — it's the ",[187,466,467],{},"management overhead you don't carry",". You don't recruit, run sprint planning, or cover for someone on vacation. You approve scope and review demos. For a founder without a technical co-founder, that's the whole point.",[175,470,471,472,477,478,484,485,488,489,493,494,498],{},"Agencies are the right call for ",[473,474,476],"term",{"slug":475},"mvp","MVPs"," (typically ",[429,479,480],{"href":431},[481,482],"service-price",{"service":483},"flutter-app-development\u002Fmvp",") and full business apps (",[481,486],{"service":487},"flutter-app-development\u002Fbusiness",") where the goal is \"get this shipped well, fast.\" We've done exactly this for clients like ",[429,490,492],{"href":491},"\u002Fportfolio\u002Fextraetf","ExtraETF"," (a chart-heavy fintech app) and ",[429,495,497],{"href":496},"\u002Fportfolio\u002Fyoumi","YouMi"," — a defined product delivered by a team that had shipped that risk category before.",[175,500,501],{},"Where agencies stop being the answer: when you need long-term ownership and the app never really \"ends.\" At that point you're renting a team forever, and the knowledge-retention math starts favoring in-house or augmentation.",[195,503,505],{"id":504},"when-is-staff-augmentation-the-best-fit","When is staff augmentation the best fit?",[175,507,508,509,513],{},"Flutter ",[473,510,512],{"slug":511},"staff-augmentation","staff augmentation"," is when you embed one or more vetted Flutter engineers directly into your existing team — they work in your repo, your sprints, and your Slack, under your management, but they're employed and supplied by an external partner. You're extending a team you already have, not outsourcing a project.",[175,515,516,517,520],{},"This is the right fit when you have an engineering function that ",[187,518,519],{},"works"," — a tech lead, a codebase, a process — and the only thing you're short on is Flutter throughput. Maybe you need to hit a launch date, cover a parental leave, or add mobile to a backend-strong team. Augmentation gives you senior Flutter capacity in days instead of the months an in-house hire takes, and the code and context stay in your repo, not a vendor's.",[175,522,523],{},"It's also the most flexible model by a wide margin. Scale from one engineer to four for a crunch, then back down, on monthly boundaries — no severance, no recruiting cycle. That flexibility is the whole product.",[175,525,526,527,531,532,535],{},"The honest limit: augmentation only works if you can actually manage engineers. If you don't have someone to own architecture, review PRs, and run planning, augmented engineers will drift — and you'll get agency-quality problems at augmentation prices. If that's you, hire an agency instead. This is our primary ",[429,528,530],{"href":529},"\u002Fservices\u002Fteam-augmentation","team augmentation"," offering, and it's also the model we'll talk you ",[187,533,534],{},"out"," of if you don't have the management capacity to make it work.",[195,537,539],{"id":538},"how-fast-can-each-model-get-you-shipping","How fast can each model get you shipping?",[175,541,542],{},"Speed-to-first-commit ranks in a clear order, and it's often the deciding factor.",[362,544,545,551,557],{},[365,546,547,550],{},[178,548,549],{},"Staff augmentation: days to ~2 weeks."," A vetted engineer who already knows Flutter joins your existing setup. The ramp is your codebase and domain, not the language or the tooling.",[365,552,553,556],{},[178,554,555],{},"Agency: 1–3 weeks to kickoff, then continuous."," The team is pre-formed, so there's no hiring delay — the lead time is scoping and contracts, after which a whole team moves at once.",[365,558,559,562],{},[178,560,561],{},"In-house: 2–4 months before real code, sometimes more."," Sourcing, interviewing, notice periods, then ramp. For senior Flutter engineers the search runs longer — the pool is real but competitive.",[175,564,565],{},"If your constraint is a date, that ordering matters more than the hourly rate. The cheapest engineer who starts in three months isn't cheaper than a pricier one who starts next week — not if the delay costs you a launch window.",[195,567,569],{"id":568},"what-are-the-hidden-costs-and-failure-modes-of-each","What are the hidden costs and failure modes of each?",[175,571,572],{},"Every model has a failure mode that doesn't show up in the quote. Here are the ones that actually bite.",[175,574,575,578,579,582],{},[178,576,577],{},"In-house hidden costs."," Recruiting is slow and expensive — 15–25% of first-year salary in fees, plus weeks of your senior engineers' time interviewing. Then there's ",[178,580,581],{},"bus factor",": if one person owns all the Flutter knowledge and leaves, you have a crisis, not an inconvenience. And a mis-hire is the most expensive mistake of all — months of salary, lost momentum, and the search to run again.",[175,584,585,588,589,592,593,596,597,600,601,603,604,607,608,611],{},[178,586,587],{},"Agency hidden costs."," The big two are ",[178,590,591],{},"lock-in"," and the ",[178,594,595],{},"knowledge cliff",". If the agency owns the codebase, the ",[473,598],{"slug":599},"ci-cd",", and all the tribal knowledge, moving away from them is painful by design. Protect yourself contractually: code in ",[187,602,306],{}," repos from day one, documented handoff, no critical infrastructure only they can access. The other failure mode is the mismatch where a ",[372,605],{"value-usd":606},"30000"," MVP gets quoted at ",[372,609],{"value-usd":610},"200000"," — shops that only sell at one price point. If the estimate doesn't match the scope, the agency either doesn't understand the scope or doesn't want to.",[175,613,614,617,618,621],{},[178,615,616],{},"Staff augmentation hidden costs."," The load you can't outsource is ",[178,619,620],{},"management",". Augmented engineers need onboarding, code review, and direction like any team member — skip it and quality slips before you notice. There's a real ramp cost while they learn your domain, plus a communication tax across a distant timezone. Augmentation is capacity, not autopilot; you're trading a hiring burden for a management one.",[195,623,625],{"id":624},"how-do-you-vet-a-flutter-developer-or-team","How do you vet a Flutter developer or team?",[175,627,628],{},"Whether you're interviewing an in-house candidate, an agency, or an augmentation engineer, the signal is the same. Ask for evidence, not adjectives.",[362,630,631,637,648,662,668,674],{},[365,632,633,636],{},[178,634,635],{},"Real shipped apps."," Ask for App Store and Google Play links, not screenshots — then download them. Do they feel fast? Do they handle offline, errors, and slow networks gracefully? Shipped-and-live beats a polished portfolio deck.",[365,638,639,642,643,647],{},[178,640,641],{},"pub.dev and open-source footprint."," Published packages, meaningful contributions, or answered issues signal someone who operates in the ecosystem, not just consumes it. ",[429,644,646],{"href":645},"\u002Fopen-source","Ours are public"," if you want a reference point for what \"maintained\" looks like.",[365,649,650,657,658,661],{},[178,651,652,656],{},[473,653,655],{"slug":654},"state-management","State-management"," fluency."," They should have a ",[187,659,660],{},"reasoned"," opinion on Riverpod vs. BLoC vs. Provider — not \"I use X because it's what I know.\" Dogma is a yellow flag; tradeoff-awareness is a green one.",[365,663,664,667],{},[178,665,666],{},"CI\u002FCD and release discipline."," Can they set up automated builds, signing, and store deployment? Do they use feature flags and staged rollouts? Shipping is a skill separate from coding — it's where junior teams quietly bleed time.",[365,669,670,673],{},[178,671,672],{},"Testing."," Ask what they test and why. \"We test everything\" is as much a warning sign as \"we don't test.\" You want judgment about where tests earn their keep.",[365,675,676,679],{},[178,677,678],{},"Platform-channel and native experience."," Real apps eventually need native code — an iOS SDK, an Android permission quirk, a native module. Someone who's never left the Dart layer will stall the first time you hit the platform boundary.",[175,681,682,683,350,687,433],{},"Still deciding between Flutter and something else before you hire for it? We cover that in ",[429,684,686],{"href":685},"\u002Fblog\u002Fflutter-vs-react-native-2026","Flutter vs React Native in 2026",[429,688,690],{"href":689},"\u002Fblog\u002Fflutter-vs-native-2026","Flutter vs Native in 2026",[195,692,694],{"id":693},"a-decision-framework-four-questions","A decision framework: four questions",[175,696,697],{},"Answer these in order. The first \"yes\" that fits routes you to a model.",[699,700,701,711,720,729],"ol",{},[365,702,703,706,707,710],{},[178,704,705],{},"Is this app core to your business for the next 3+ years, and can you wait 2–4 months to staff it?"," → ",[178,708,709],{},"Hire in-house."," You want the knowledge in the building, and you can afford the slow start.",[365,712,713,706,716,719],{},[178,714,715],{},"Do you need a defined product shipped on a deadline, with little internal engineering to manage it?",[178,717,718],{},"Hire an agency."," Buy the team and the management overhead, not just the code.",[365,721,722,706,725,728],{},[178,723,724],{},"Do you already have a working engineering team that just needs more Flutter capacity — and someone to manage it?",[178,726,727],{},"Use staff augmentation."," Extend the team you have.",[365,730,731,706,734,737],{},[178,732,733],{},"Are you unsure whether the idea is even worth building yet?",[178,735,736],{},"Start with an agency-built MVP."," It's the fastest way to a real answer, and you're not committing to a hire before you know you need one.",[175,739,740],{},"If two answers fit, the tiebreaker is management capacity: augmentation and in-house both assume you can run engineers. If you can't, an agency is the honest choice.",[195,742,744],{"id":743},"faq","FAQ",[746,747,749],"questions",{":items":748},"[{\"title\":\"How much does it cost to hire a Flutter developer?\",\"slot\":\"rates\",\"text\":\"In 2026, blended agency rates run $150–250\u002Fhour in the US, $100–180 in Western Europe, $50–95 in Eastern Europe, and $25–55 in South\u002FSoutheast Asia. In-house senior salaries run roughly $120k–180k+ (US), €60k–100k (Western Europe), and $35k–70k (Eastern Europe), plus 25–40% for fully loaded cost. Staff augmentation typically costs 10–30% less than a full agency rate because you're buying the engineer, not the whole delivery team.\"},{\"title\":\"Is it cheaper to hire in-house or an agency?\",\"text\":\"It depends on time horizon. An agency is cheaper to start — no recruiting fees, no salaries before code ships, and no long-term liability. In-house is cheaper per hour once you've hired, so it wins over multiple years of continuous work. For a one-time build, an agency is almost always cheaper all-in; for a multi-year core product, in-house usually wins.\"},{\"title\":\"What is Flutter staff augmentation?\",\"text\":\"Flutter staff augmentation is when you embed one or more vetted Flutter engineers directly into your existing team. They work in your repository, your sprints, and under your management, but they're employed and supplied by an external partner. It's a way to add Flutter capacity in days without the recruiting time or long-term commitment of a full-time hire, while keeping the code and knowledge inside your own team.\"},{\"title\":\"How long does it take to onboard a Flutter developer?\",\"text\":\"A staff-augmentation engineer who already knows Flutter is typically productive in your codebase within days to two weeks — the ramp is your domain, not the language. An agency team kicks off in 1–3 weeks. A new in-house hire takes 2–4 months from starting the search to shipping real code, because of sourcing, interviewing, and notice periods.\"},{\"title\":\"How do I know if a Flutter developer is good?\",\"text\":\"Ask for live App Store and Google Play links and actually use the apps — test them on slow networks and offline. Look for a pub.dev or open-source footprint, a reasoned opinion on state management (Riverpod vs. BLoC vs. Provider), and real CI\u002FCD and release experience. The strongest signal is platform-channel work: someone who has integrated native iOS\u002FAndroid code has hit the hard parts of real apps.\"},{\"title\":\"In-house vs outsource Flutter — which should a startup choose?\",\"text\":\"Most early-stage startups should outsource the first build to an agency, then hire in-house once the product has traction and the roadmap is clear. Outsourcing gets you to market faster and defers the cost and risk of hiring before you know what you need. Switch to in-house when the app becomes core to the business and you'll be shipping continuously for years.\"},{\"title\":\"Can I hire a dedicated Flutter team without hiring employees?\",\"text\":\"Yes. A dedicated Flutter team through an agency or staff augmentation gives you engineers who work only on your product, without the employment liability, recruiting time, or benefits overhead of full-time hires. With augmentation the team works inside your processes and repo; with an agency they work as a managed unit. Both let you scale the team up or down at contract boundaries.\"}]",[750,751,753],"template",{"v-slot:rates_body":752},"",[175,754,755,756,759,760,762,763,765,766,768],{},"In 2026, blended agency rates run ",[372,757],{":value-usd":374,"format":758},"full","\u002Fhour in the US, ",[372,761],{":value-usd":383,"format":758}," in Western Europe, ",[372,764],{":value-usd":391,"format":758}," in Eastern Europe, and ",[372,767],{":value-usd":399,"format":758}," in South\u002FSoutheast Asia. In-house senior salaries run roughly $120k–180k+ (US), €60k–100k (Western Europe), and $35k–70k (Eastern Europe), plus 25–40% for fully loaded cost. Staff augmentation typically costs 10–30% less than a full agency rate because you're buying the engineer, not the whole delivery team.",[195,770,772],{"id":771},"which-model-fits-you","Which model fits you?",[175,774,775],{},"Not sure which of the three is right? That's the normal state — the answer depends on your timeline, your existing team, and how central this app is to the business. We're happy to talk it through honestly, even when the answer is \"hire in-house\" or \"you need an agency, not us.\"",[175,777,778,779,783,784,788,789,791,792,433],{},"If it turns out to be augmentation, that's our wedge: we place vetted Flutter engineers into your team, in your repo and your sprints, with the code and knowledge staying yours. If it's a defined product you'd rather hand off, that's our ",[429,780,782],{"href":781},"\u002Fservices\u002Fflutter-app-development","Flutter app development"," practice — see the kind of work it produces in ",[429,785,787],{"href":786},"\u002Fportfolio\u002Farcana","Arcana",", ",[429,790,492],{"href":491},", and ",[429,793,497],{"href":496},[175,795,796,797,801],{},"Either way, ",[429,798,800],{"href":799},"\u002Fcontact","tell us what you're building"," and we'll give you a straight recommendation on the model — not a pitch for the most expensive one.",[803,804,805],"post-credits",{},[175,806,807,808,812],{},"Ilya Nixan is Founder & Lead Developer at ",[429,809,811],{"href":810},"\u002F","Nerdy Production",", a Flutter-first agency that ships apps across fintech, healthcare, and retail — and places Flutter engineers into client teams.",{"title":752,"searchDepth":814,"depth":814,"links":815},2,[816,817,818,819,820,821,822,823,824,825,826],{"id":197,"depth":814,"text":198},{"id":342,"depth":814,"text":343},{"id":436,"depth":814,"text":437},{"id":457,"depth":814,"text":458},{"id":504,"depth":814,"text":505},{"id":538,"depth":814,"text":539},{"id":568,"depth":814,"text":569},{"id":624,"depth":814,"text":625},{"id":693,"depth":814,"text":694},{"id":743,"depth":814,"text":744},{"id":771,"depth":814,"text":772},"TL;DR. There are three ways to hire Flutter talent in 2026, and the right one depends on what you're actually buying. Hire in-house when Flutter is core to your product for years and you want to own the code and the knowledge. Hire an agency when you need a defined product shipped fast with the least management overhead. Use staff augmentation when you already have a team that can manage engineers and just need more Flutter capacity. The one-line decision rule: if the mobile app is the business, build in-house; if you need it built, hire an agency; if you need it built faster, augment your team. Everything below is the detail behind that sentence — real 2026 rate ranges, hidden costs, and a checklist for vetting whoever you hire.","md",{"type":830,"src":831},"image","\u002Fblog\u002Fhire-flutter-developers-2026.webp",{},"Hire Flutter developers in 2026: in-house vs agency vs staff augmentation, compared on cost, speed, and risk — with rate ranges and a decision framework.","Hire Flutter Developers: In-House vs Agency vs Augmentation",true,"In-house, agency, or staff augmentation — what each really costs, how fast each moves, and which risk you are taking on. With 2026 rate ranges.","\u002Fblog\u002Fhire-flutter-developers-2026",{"title":169,"description":827},"hire-flutter-developers-2026","blog\u002Fhire-flutter-developers-2026","Three ways to hire Flutter talent in 2026 — in-house, agency, or staff augmentation — compared on cost, speed, and risk, with real rate ranges and a decision framework for founders and CTOs.","2026-07-03T10:18:26Z",null,"iQwZ_fb7RLiU0YG_Z3wkT4aw5qf_J7R3lpRDkhJKHfI",[846,903,950,1000,1089,1141],{"id":847,"bio":848,"expertise":853,"extension":869,"links":870,"meta":874,"metaDescription":875,"name":880,"ogDescription":883,"photo":888,"role":889,"seniority":894,"skills":895,"slug":896,"specialization":897,"stem":896,"__hash__":902},"team_members\u002Fdima.yaml",{"en":849,"ru":850,"es":851,"nl":852},"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",[854,857,862,864],{"en":855,"ru":855,"es":856,"nl":855},"State management","Gestión de estado",{"en":858,"ru":859,"es":860,"nl":861},"Application architecture","Архитектура приложений","Arquitectura de aplicaciones","Applicatiearchitectuur",{"en":863,"ru":863,"es":863,"nl":863},"WebRTC",{"en":865,"ru":866,"es":867,"nl":868},"XMPP messaging","Обмен сообщениями по XMPP","Mensajería XMPP","Berichten via XMPP","yaml",[871],{"type":872,"address":873},"email","konopatov@nerdy.pro",{},{"en":876,"ru":877,"es":878,"nl":879},"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":881,"ru":882,"es":881,"nl":881},"Dima","Дима",{"en":884,"ru":885,"es":886,"nl":887},"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":890,"ru":891,"es":892,"nl":893},"Lead Flutter Developer","Ведущий Flutter-разработчик","Lead de desarrollo Flutter","Lead Flutter-developer","lead",[41,18,155,160,90,111,150,95],"dima",{"en":898,"ru":899,"es":900,"nl":901},"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":904,"bio":905,"expertise":910,"extension":869,"links":843,"meta":921,"metaDescription":922,"name":927,"ogDescription":930,"photo":935,"role":936,"seniority":941,"skills":942,"slug":943,"specialization":944,"stem":943,"__hash__":949},"team_members\u002Fmasha.yaml",{"en":906,"ru":907,"es":908,"nl":909},"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",[911,916],{"en":912,"ru":913,"es":914,"nl":915},"UI\u002FUX design","UI\u002FUX-дизайн","Diseño UI\u002FUX","UI\u002FUX-ontwerp",{"en":917,"ru":918,"es":919,"nl":920},"Product copywriting","Продуктовый копирайтинг","Redacción de producto","Productteksten",{},{"en":923,"ru":924,"es":925,"nl":926},"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":928,"ru":929,"es":928,"nl":928},"Masha","Маша",{"en":931,"ru":932,"es":933,"nl":934},"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":937,"ru":938,"es":939,"nl":940},"Flutter Developer","Flutter-разработчик","Desarrolladora Flutter","Flutter-developer","middle",[41,18],"masha",{"en":945,"ru":946,"es":947,"nl":948},"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":951,"bio":952,"expertise":957,"extension":869,"links":968,"meta":971,"metaDescription":972,"name":977,"ogDescription":980,"photo":985,"role":986,"seniority":991,"skills":992,"slug":993,"specialization":994,"stem":993,"__hash__":999},"team_members\u002Fmaxim.yaml",{"en":953,"ru":954,"es":955,"nl":956},"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",[958,963],{"en":959,"ru":960,"es":961,"nl":962},"Automated testing","Автоматизированное тестирование","Testing automatizado","Geautomatiseerd testen",{"en":964,"ru":965,"es":966,"nl":967},"High-load backend systems","Высоконагруженные бэкенд-системы","Sistemas backend de alta carga","Backendsystemen met hoge belasting",[969],{"type":872,"address":970},"maxim@nerdy.pro",{},{"en":973,"ru":974,"es":975,"nl":976},"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":978,"ru":979,"es":978,"nl":978},"Maxim","Максим",{"en":981,"ru":982,"es":983,"nl":984},"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":987,"ru":988,"es":989,"nl":990},"Senior Software Engineer","Старший инженер-программист","Ingeniero de software senior","Senior software engineer","senior",[41,18,51,106,155,13,150],"maxim",{"en":995,"ru":996,"es":997,"nl":998},"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":1001,"bio":1002,"expertise":1007,"extension":869,"links":1049,"meta":1061,"metaDescription":1062,"name":1067,"ogDescription":1070,"photo":1075,"role":1076,"seniority":1081,"skills":1082,"slug":170,"specialization":1083,"stem":170,"__hash__":1088},"team_members\u002Fnixan.yaml",{"en":1003,"ru":1004,"es":1005,"nl":1006},"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",[1008,1013,1018,1023,1028,1033,1038,1043,1045,1047],{"en":1009,"ru":1010,"es":1011,"nl":1012},"iOS development","Разработка под iOS","Desarrollo iOS","iOS-ontwikkeling",{"en":1014,"ru":1015,"es":1016,"nl":1017},"Software architecture","Архитектура ПО","Arquitectura de software","Softwarearchitectuur",{"en":1019,"ru":1020,"es":1021,"nl":1022},"Engineering team leadership","Руководство инженерными командами","Liderazgo de equipos de ingeniería","Leidinggeven aan engineeringteams",{"en":1024,"ru":1025,"es":1026,"nl":1027},"Payment systems","Платёжные системы","Sistemas de pago","Betaalsystemen",{"en":1029,"ru":1030,"es":1031,"nl":1032},"Card processing","Карточный процессинг","Procesamiento de tarjetas","Kaartverwerking",{"en":1034,"ru":1035,"es":1036,"nl":1037},"PCI-DSS compliance","Соответствие PCI-DSS","Cumplimiento de PCI-DSS","Naleving van PCI-DSS",{"en":1039,"ru":1040,"es":1041,"nl":1042},"NFC and contactless payments","NFC и бесконтактные платежи","NFC y pagos contactless","NFC en contactloos betalen",{"en":1044,"ru":1044,"es":1044,"nl":1044},"Host Card Emulation",{"en":1046,"ru":1046,"es":1046,"nl":1046},"EMV Contactless",{"en":1048,"ru":1048,"es":1048,"nl":1048},"AOSP",[1050,1053,1056,1059],{"type":1051,"url":1052},"github","https:\u002F\u002Fgithub.com\u002Fthenixan",{"type":1054,"url":1055},"linkedin","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fthenixan\u002F",{"type":1057,"url":1058},"telegram","https:\u002F\u002Ft.me\u002Fthenixan",{"type":872,"address":1060},"nixan@nerdy.pro",{},{"en":1063,"ru":1064,"es":1065,"nl":1066},"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":1068,"ru":1069,"es":1068,"nl":1068},"Ilya Nixan","Илья Никсан",{"en":1071,"ru":1072,"es":1073,"nl":1074},"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":1077,"ru":1078,"es":1079,"nl":1080},"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],{"en":1084,"ru":1085,"es":1086,"nl":1087},"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":1090,"bio":1091,"expertise":1096,"extension":869,"links":1108,"meta":1113,"metaDescription":1114,"name":1119,"ogDescription":1122,"photo":1127,"role":1128,"seniority":991,"skills":1133,"slug":1134,"specialization":1135,"stem":1134,"__hash__":1140},"team_members\u002Froma.yaml",{"en":1092,"ru":1093,"es":1094,"nl":1095},"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",[1097,1098,1103],{"en":1009,"ru":1010,"es":1011,"nl":1012},{"en":1099,"ru":1100,"es":1101,"nl":1102},"Applied AI","Прикладной AI","IA aplicada","Toegepaste AI",{"en":1104,"ru":1105,"es":1106,"nl":1107},"ERP and CRM systems","ERP- и CRM-системы","Sistemas ERP y CRM","ERP- en CRM-systemen",[1109,1111],{"type":1054,"url":1110},"https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fromanbatler\u002F",{"type":872,"address":1112},"roma@nerdy.pro",{},{"en":1115,"ru":1116,"es":1117,"nl":1118},"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":1120,"ru":1121,"es":1120,"nl":1120},"Roman","Рома",{"en":1123,"ru":1124,"es":1125,"nl":1126},"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":1129,"ru":1130,"es":1131,"nl":1132},"Senior Mobile Developer","Старший мобильный разработчик","Desarrollador móvil senior","Senior mobiele developer",[7,41,18,141,146,106],"roma",{"en":1136,"ru":1137,"es":1138,"nl":1139},"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":1142,"bio":1143,"expertise":1148,"extension":869,"links":843,"meta":1159,"metaDescription":1160,"name":1165,"ogDescription":1168,"photo":1173,"role":1174,"seniority":991,"skills":1179,"slug":1180,"specialization":1181,"stem":1180,"__hash__":1186},"team_members\u002Fxsox.yaml",{"en":1144,"ru":1145,"es":1146,"nl":1147},"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",[1149,1154],{"en":1150,"ru":1151,"es":1152,"nl":1153},"API design","Проектирование API","Diseño de APIs","API-ontwerp",{"en":1155,"ru":1156,"es":1157,"nl":1158},"Data modelling","Моделирование данных","Modelado de datos","Datamodellering",{},{"en":1161,"ru":1162,"es":1163,"nl":1164},"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":1166,"ru":1167,"es":1166,"nl":1166},"Eugene Xsox","Женя Xsox",{"en":1169,"ru":1170,"es":1171,"nl":1172},"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":1175,"ru":1176,"es":1177,"nl":1178},"Senior Backend Developer","Старший бэкенд-разработчик","Desarrollador backend senior","Senior backenddeveloper",[106,24,41,18,155,160,90,150],"xsox",{"en":1182,"ru":1183,"es":1184,"nl":1185},"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",[1188,1197,1204,1209,1219],{"id":1189,"extension":869,"meta":1190,"name":1191,"slug":1195,"stem":1195,"__hash__":1196},"blog_topics\u002Fcybersecurity.yaml",{},{"en":1192,"ru":1193,"es":1194,"nl":1192},"Cybersecurity","Кибербезопасность","Ciberseguridad","cybersecurity","kt1rdsMy5W4b9MvGHm6mZVCr0inHidEuqaosPYmmk4E",{"id":1198,"extension":869,"meta":1199,"name":1200,"slug":1202,"stem":1202,"__hash__":1203},"blog_topics\u002Fdevops.yaml",{},{"en":1201,"ru":1201,"es":1201,"nl":1201},"DevOps","devops","D3mxlZuFHKCGeszKZuWCiQmHmP5EiCvzg1qEAIQhnyU",{"id":1205,"extension":869,"meta":1206,"name":1207,"slug":41,"stem":41,"__hash__":1208},"blog_topics\u002Fflutter.yaml",{},{"en":39,"ru":39,"es":39,"nl":39},"OOeALAmwFuEqByuJvTGk4g15FIHENPfYMdpfZh_HTAE",{"id":1210,"extension":869,"meta":1211,"name":1212,"slug":1217,"stem":1217,"__hash__":1218},"blog_topics\u002Ffor-founders.yaml",{},{"en":1213,"ru":1214,"es":1215,"nl":1216},"For Founders","Для основателей","Para fundadores","Voor oprichters","for-founders","lp2u6Ol2qF4DGxpB83HxbbGzWioT-e40mJhD4lr28-U",{"id":1220,"extension":869,"meta":1221,"name":1222,"slug":1227,"stem":1227,"__hash__":1228},"blog_topics\u002Fsoftware-engineering.yaml",{},{"en":1223,"ru":1224,"es":1225,"nl":1226},"Software Engineering","Разработка ПО","Ingeniería de software","Software-engineering","software-engineering","aZMb3aUDptoFQk_cEE6l5H4wrYcgZuBYUubmKqOAaaU",{"data":1230,"body":1231},{},{"type":1232,"children":1233},"root",[1234,1241,1259,1270,1295],{"type":1235,"tag":175,"props":1236,"children":1237},"element",{},[1238],{"type":1239,"value":1240},"text","Ilya founded Nerdy Production and leads its engineering. He has been building software since 2010 and shipping production Flutter since 2018.",{"type":1235,"tag":175,"props":1242,"children":1243},{},[1244,1246,1250,1252,1257],{"type":1239,"value":1245},"Before 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, ",{"type":1235,"tag":473,"props":1247,"children":1249},{"slug":1248},"pci-dss",[],{"type":1239,"value":1251}," scope, and contactless payments — including building contactless card payments on Android via ",{"type":1235,"tag":473,"props":1253,"children":1255},{"slug":1254},"host-card-emulation",[1256],{"type":1239,"value":1044},{"type":1239,"value":1258}," over ISO\u002FIEC 14443, with EMV Contactless (Visa PayWave) on top.",{"type":1235,"tag":175,"props":1260,"children":1261},{},[1262,1264,1268],{"type":1239,"value":1263},"He 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 ",{"type":1235,"tag":473,"props":1265,"children":1267},{"slug":1266},"aosp",[],{"type":1239,"value":1269},", giving him a low-level view of Android most app developers never touch.",{"type":1235,"tag":175,"props":1271,"children":1272},{},[1273,1275,1279,1281,1285,1287,1293],{"type":1239,"value":1274},"Today he leads delivery on the agency's flagship apps — from the chart-heavy fintech UI of ",{"type":1235,"tag":429,"props":1276,"children":1277},{"href":491},[1278],{"type":1239,"value":492},{"type":1239,"value":1280}," to the fully custom design system of ",{"type":1235,"tag":429,"props":1282,"children":1283},{"href":786},[1284],{"type":1239,"value":787},{"type":1239,"value":1286},". He writes most of the essays on this blog and maintains the agency's open-source work, including the ",{"type":1235,"tag":429,"props":1288,"children":1290},{"href":1289},"\u002Fopen-source\u002Fdxpdf",[1291],{"type":1239,"value":1292},"dxpdf",{"type":1239,"value":1294}," DOCX-to-PDF engine.",{"type":1235,"tag":175,"props":1296,"children":1297},{},[1298,1300,1305,1307,1312,1313,1318,1319,1324,1325,1330,1331,1336,1337,1342],{"type":1239,"value":1299},"He works across ",{"type":1235,"tag":429,"props":1301,"children":1303},{"href":1302},"\u002Ftechnologies\u002Fflutter",[1304],{"type":1239,"value":39},{"type":1239,"value":1306},", native iOS and Android, ",{"type":1235,"tag":429,"props":1308,"children":1310},{"href":1309},"\u002Ftechnologies\u002Fgo",[1311],{"type":1239,"value":49},{"type":1239,"value":788},{"type":1235,"tag":429,"props":1314,"children":1316},{"href":1315},"\u002Ftechnologies\u002Frust",[1317],{"type":1239,"value":124},{"type":1239,"value":788},{"type":1235,"tag":429,"props":1320,"children":1322},{"href":1321},"\u002Ftechnologies\u002Ftypescript",[1323],{"type":1239,"value":153},{"type":1239,"value":788},{"type":1235,"tag":429,"props":1326,"children":1328},{"href":1327},"\u002Ftechnologies\u002Fkotlin",[1329],{"type":1239,"value":69},{"type":1239,"value":788},{"type":1235,"tag":429,"props":1332,"children":1334},{"href":1333},"\u002Ftechnologies\u002Fkubernetes",[1335],{"type":1239,"value":78},{"type":1239,"value":791},{"type":1235,"tag":429,"props":1338,"children":1340},{"href":1339},"\u002Ftechnologies\u002Fdocker",[1341],{"type":1239,"value":27},{"type":1239,"value":1343},", with a focus on app architecture, cross-platform delivery, and building teams that ship.",[1345,1357,1370,1385,1398,1412,1428,1440,1454,1467,1481,1494,1510,1523,1539,1552,1563,1573,1586,1596,1607,1622,1631,1644,1657,1664,1674,1686,1697,1712,1724,1737,1749,1761,1773,1785,1796,1807,1818,1829,1841,1851,1862,1875,1884,1893,1904,1916,1926,1937,1950,1959,1970],{"slug":1266,"term":1048,"definition":1346,"category":1347,"aliases":1348,"links":1350,"related":1354,"readMore":-1,"target":1355,"hasArticle":1356},"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",[1349],"Android Open Source Project",[1351],{"kind":1352,"url":1353},"website","https:\u002F\u002Fsource.android.com\u002F",[1254],"\u002Fglossary#aosp",false,{"slug":1358,"term":1359,"definition":1360,"category":1347,"aliases":1361,"links":1362,"related":1366,"readMore":-1,"target":1369,"hasArticle":1356},"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.",[],[1363],{"kind":1364,"url":1365},"documentation","https:\u002F\u002Fdeveloper.apple.com\u002Fapp-clips\u002F",[1367,1368],"deep-linking","install-referrer","\u002Fglossary#app-clips",{"slug":1371,"term":1372,"definition":1373,"category":1347,"aliases":1374,"links":1375,"related":1381,"readMore":-1,"target":1384,"hasArticle":1356},"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.",[],[1376,1378],{"kind":1352,"url":1377},"https:\u002F\u002Fcloud.google.com\u002Fbigquery",{"kind":1379,"url":1380},"wikipedia","https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FBigQuery",[1382,1383],"object-storage","elasticsearch","\u002Fglossary#bigquery",{"slug":599,"term":1386,"definition":1387,"category":1388,"aliases":1389,"links":1393,"related":1396,"readMore":-1,"target":1397,"hasArticle":1356},"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",[1390,1391,1392],"CI","continuous integration","continuous delivery",[1394],{"kind":1379,"url":1395},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FCI\u002FCD",[],"\u002Fglossary#ci-cd",{"slug":1399,"term":1400,"definition":1401,"category":1402,"aliases":1403,"links":1405,"related":1408,"readMore":-1,"target":1411,"hasArticle":1356},"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",[1404],"Create, Read, Update, Delete",[1406],{"kind":1379,"url":1407},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FCreate,_read,_update_and_delete",[1409,1410],"rest","graphql","\u002Fglossary#crud",{"slug":1413,"term":1414,"definition":1415,"category":1402,"aliases":1416,"links":1421,"related":1424,"readMore":-1,"target":1427,"hasArticle":1356},"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.",[1417,1418,1419,1420],"image registry","Docker registry","GHCR","ghcr.io",[1422],{"kind":1364,"url":1423},"https:\u002F\u002Fdocs.github.com\u002Fen\u002Fpackages\u002Fworking-with-a-github-packages-registry\u002Fworking-with-the-container-registry",[1425,1426],"dev-container","multi-arch-image","\u002Fglossary#container-registry",{"slug":1367,"term":1429,"definition":1430,"category":1347,"aliases":1431,"links":1435,"related":1438,"readMore":1439,"target":1439,"hasArticle":835},"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.",[1432,1433,1434],"deferred deep linking","universal links","Android App Links",[1436],{"kind":1379,"url":1437},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FMobile_deep_linking",[1358,1368],"\u002Fglossary\u002Fdeep-linking",{"slug":1425,"term":1441,"definition":1442,"category":1388,"aliases":1443,"links":1447,"related":1452,"readMore":-1,"target":1453,"hasArticle":1356},"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.",[1444,1445,1446],"devcontainer.json","Dev Containers","VS Code Dev Containers",[1448,1450],{"kind":1352,"url":1449},"https:\u002F\u002Fcontainers.dev\u002F",{"kind":1364,"url":1451},"https:\u002F\u002Fcode.visualstudio.com\u002Fdocs\u002Fdevcontainers\u002Fcontainers",[1413],"\u002Fglossary#dev-container",{"slug":1383,"term":1455,"definition":1456,"category":1347,"aliases":1457,"links":1460,"related":1465,"readMore":-1,"target":1466,"hasArticle":1356},"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\".",[1458,1459],"Elastic","ELK",[1461,1463],{"kind":1352,"url":1462},"https:\u002F\u002Fwww.elastic.co\u002Felasticsearch",{"kind":1379,"url":1464},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FElasticsearch",[1371],"\u002Fglossary#elasticsearch",{"slug":1468,"term":1469,"definition":1470,"category":1402,"aliases":1471,"links":1474,"related":1477,"readMore":-1,"target":1480,"hasArticle":1356},"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.",[1472,1473],"E2EE","end-to-end encrypted",[1475],{"kind":1379,"url":1476},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FEnd-to-end_encryption",[1478,1479],"tls","jwt","\u002Fglossary#end-to-end-encryption",{"slug":1482,"term":1483,"definition":1484,"category":1402,"aliases":1485,"links":1488,"related":1489,"readMore":-1,"target":1493,"hasArticle":1356},"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.",[1486,1487],"fanout","broadcast",[],[1490,1491,1492],"websocket","pub-sub","server-sent-events","\u002Fglossary#fan-out",{"slug":1495,"term":1496,"definition":1497,"category":1388,"aliases":1498,"links":1502,"related":1505,"readMore":-1,"target":1509,"hasArticle":1356},"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.",[1499,1500,1501],"feature flag","feature toggle","feature gating",[1503],{"kind":1379,"url":1504},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FFeature_toggle",[1506,1507,1508],"staged-rollout","white-label","multi-tenancy","\u002Fglossary#feature-flags",{"slug":1511,"term":1512,"definition":1513,"category":1402,"aliases":1514,"links":1518,"related":1521,"readMore":-1,"target":1522,"hasArticle":1356},"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.",[1515,1516,1517],"IEEE 754","double","floating-point arithmetic",[1519],{"kind":1379,"url":1520},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FIEEE_754",[],"\u002Fglossary#floating-point",{"slug":1524,"term":1525,"definition":1526,"category":1388,"aliases":1527,"links":1530,"related":1535,"readMore":-1,"target":1538,"hasArticle":1356},"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.",[1528,1529],"General Data Protection Regulation","data protection",[1531,1533],{"kind":1352,"url":1532},"https:\u002F\u002Fgdpr.eu\u002F",{"kind":1379,"url":1534},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FGeneral_Data_Protection_Regulation",[1248,1536,1537],"soc-2","hipaa","\u002Fglossary#gdpr",{"slug":1540,"term":1541,"definition":1542,"category":1388,"aliases":1543,"links":1547,"related":1550,"readMore":-1,"target":1551,"hasArticle":1356},"golden-test","Golden test","A test that renders a widget and compares the result pixel for pixel against a stored reference image. In Flutter it is the cheapest way to answer whether a redesign broke the empty state at 320pt, in dark mode, at 200% text scale.",[1544,1545,1546],"golden tests","screenshot test","snapshot test",[1548],{"kind":1364,"url":1549},"https:\u002F\u002Fapi.flutter.dev\u002Fflutter\u002Fflutter_test\u002FmatchesGoldenFile.html",[599],"\u002Fglossary#golden-test",{"slug":1410,"term":1553,"definition":1554,"category":1402,"aliases":1555,"links":1556,"related":1561,"readMore":-1,"target":1562,"hasArticle":1356},"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.",[],[1557,1559],{"kind":1352,"url":1558},"https:\u002F\u002Fgraphql.org\u002F",{"kind":1379,"url":1560},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FGraphQL",[1409],"\u002Fglossary#graphql",{"slug":1537,"term":1564,"definition":1565,"category":1388,"aliases":1566,"links":1568,"related":1571,"readMore":-1,"target":1572,"hasArticle":1356},"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.",[1567],"Health Insurance Portability and Accountability Act",[1569],{"kind":1379,"url":1570},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FHealth_Insurance_Portability_and_Accountability_Act",[1248,1524,1536],"\u002Fglossary#hipaa",{"slug":1574,"term":1575,"definition":1576,"category":1402,"aliases":1577,"links":1580,"related":1583,"readMore":-1,"target":1585,"hasArticle":1356},"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.",[1578,1579],"headless content management system","content API",[1581],{"kind":1379,"url":1582},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FHeadless_content_management_system",[1584,1409],"server-side-rendering","\u002Fglossary#headless-cms",{"slug":1254,"term":1044,"definition":1587,"category":1347,"aliases":1588,"links":1591,"related":1594,"readMore":-1,"target":1595,"hasArticle":1356},"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.",[1589,1046,1590],"HCE","contactless payments",[1592],{"kind":1364,"url":1593},"https:\u002F\u002Fdeveloper.android.com\u002Fdevelop\u002Fconnectivity\u002Fnfc\u002Fhce",[1248,1266],"\u002Fglossary#host-card-emulation",{"slug":1597,"term":1598,"definition":1599,"category":1347,"aliases":1600,"links":1601,"related":1604,"readMore":-1,"target":1606,"hasArticle":1356},"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.",[],[1602],{"kind":1364,"url":1603},"https:\u002F\u002Fdocs.flutter.dev\u002Fperf\u002Fimpeller",[1605],"skia","\u002Fglossary#impeller",{"slug":1608,"term":1609,"definition":1610,"category":1611,"aliases":1612,"links":1616,"related":1619,"readMore":-1,"target":1621,"hasArticle":1356},"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",[1613,1614,1615],"IAP","in-app purchases","in-app subscription",[1617],{"kind":1364,"url":1618},"https:\u002F\u002Fdeveloper.apple.com\u002Fin-app-purchase\u002F",[1620],"product-market-fit","\u002Fglossary#in-app-purchase",{"slug":1368,"term":1623,"definition":1624,"category":1347,"aliases":1625,"links":1626,"related":1629,"readMore":-1,"target":1630,"hasArticle":1356},"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.",[],[1627],{"kind":1364,"url":1628},"https:\u002F\u002Fdeveloper.android.com\u002Fgoogle\u002Fplay\u002Finstallreferrer",[1367,1358],"\u002Fglossary#install-referrer",{"slug":1479,"term":1632,"definition":1633,"category":1634,"aliases":1635,"links":1637,"related":1642,"readMore":-1,"target":1643,"hasArticle":1356},"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",[1636],"JSON Web Token",[1638,1640],{"kind":1352,"url":1639},"https:\u002F\u002Fjwt.io\u002F",{"kind":1379,"url":1641},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FJSON_Web_Token",[1248],"\u002Fglossary#jwt",{"slug":1645,"term":1646,"definition":1647,"category":1388,"aliases":1648,"links":1652,"related":1655,"readMore":-1,"target":1656,"hasArticle":1356},"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.",[1649,1650,1651],"Know Your Customer","AML","KYC\u002FAML",[1653],{"kind":1379,"url":1654},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FKnow_your_customer",[1248,1524],"\u002Fglossary#kyc",{"slug":76,"term":74,"definition":1658,"category":1347,"aliases":1659,"links":1661,"related":1662,"readMore":1663,"target":1663,"hasArticle":1356},"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.",[1660],"KMP",[],[],"\u002Ftechnologies\u002Fkmp",{"slug":475,"term":1665,"definition":1666,"category":1611,"aliases":1667,"links":1669,"related":1672,"readMore":-1,"target":1673,"hasArticle":1356},"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.",[1668],"minimum viable product",[1670],{"kind":1379,"url":1671},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FMinimum_viable_product",[1507],"\u002Fglossary#mvp",{"slug":1426,"term":1675,"definition":1676,"category":1402,"aliases":1677,"links":1681,"related":1684,"readMore":-1,"target":1685,"hasArticle":1356},"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.",[1678,1679,1680],"multi-arch build","multi-platform image","linux\u002Famd64 + linux\u002Farm64",[1682],{"kind":1364,"url":1683},"https:\u002F\u002Fdocs.docker.com\u002Fbuild\u002Fbuilding\u002Fmulti-platform\u002F",[1413],"\u002Fglossary#multi-arch-image",{"slug":1508,"term":1687,"definition":1688,"category":1402,"aliases":1689,"links":1692,"related":1695,"readMore":-1,"target":1696,"hasArticle":1356},"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.",[1690,1691],"multi-tenant","tenant",[1693],{"kind":1379,"url":1694},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FMultitenancy",[1507,1495],"\u002Fglossary#multi-tenancy",{"slug":1698,"term":1699,"definition":1700,"category":1634,"aliases":1701,"links":1705,"related":1710,"readMore":-1,"target":1711,"hasArticle":1356},"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.",[1702,1703,1704],"OAuth 2.0","social login","Sign in with Apple",[1706,1708],{"kind":1352,"url":1707},"https:\u002F\u002Foauth.net\u002F2\u002F",{"kind":1379,"url":1709},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FOAuth",[1479],"\u002Fglossary#oauth",{"slug":1382,"term":1713,"definition":1714,"category":1402,"aliases":1715,"links":1719,"related":1722,"readMore":-1,"target":1723,"hasArticle":1356},"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.",[1716,1717,1718],"S3","S3-compatible storage","blob storage",[1720],{"kind":1379,"url":1721},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FObject_storage",[1371],"\u002Fglossary#object-storage",{"slug":1248,"term":1725,"definition":1726,"category":1388,"aliases":1727,"links":1730,"related":1735,"readMore":-1,"target":1736,"hasArticle":1356},"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.",[1728,1729],"PCI DSS","Payment Card Industry Data Security Standard",[1731,1733],{"kind":1352,"url":1732},"https:\u002F\u002Fwww.pcisecuritystandards.org\u002F",{"kind":1379,"url":1734},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FPayment_Card_Industry_Data_Security_Standard",[1479],"\u002Fglossary#pci-dss",{"slug":1738,"term":1739,"definition":1740,"category":1347,"aliases":1741,"links":1744,"related":1747,"readMore":-1,"target":1748,"hasArticle":1356},"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.",[1742,1743],"platform channel","method channel",[1745],{"kind":1364,"url":1746},"https:\u002F\u002Fdocs.flutter.dev\u002Fplatform-integration\u002Fplatform-channels",[76],"\u002Fglossary#platform-channels",{"slug":1750,"term":1751,"definition":1752,"category":1634,"aliases":1753,"links":1756,"related":1759,"readMore":-1,"target":1760,"hasArticle":1356},"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.",[1754,1755],"PQC","post-quantum crypto",[1757],{"kind":1379,"url":1758},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FPost-quantum_cryptography",[1478,1468],"\u002Fglossary#post-quantum-cryptography",{"slug":1620,"term":1762,"definition":1763,"category":1611,"aliases":1764,"links":1767,"related":1770,"readMore":-1,"target":1772,"hasArticle":1356},"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.",[1765,1766],"PMF","product\u002Fmarket fit",[1768],{"kind":1379,"url":1769},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FProduct-market_fit",[475,1771],"time-to-market","\u002Fglossary#product-market-fit",{"slug":1774,"term":1775,"definition":1776,"category":1388,"aliases":1777,"links":1779,"related":1782,"readMore":-1,"target":1784,"hasArticle":1356},"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.",[1778],"injection attack",[1780],{"kind":1379,"url":1781},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FPrompt_injection",[1783],"rate-limiting","\u002Fglossary#prompt-injection",{"slug":1491,"term":1786,"definition":1787,"category":1402,"aliases":1788,"links":1791,"related":1794,"readMore":-1,"target":1795,"hasArticle":1356},"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.",[1789,1790],"publish\u002Fsubscribe","Google Cloud Pub\u002FSub",[1792],{"kind":1379,"url":1793},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FPublish%E2%80%93subscribe_pattern",[],"\u002Fglossary#pub-sub",{"slug":1409,"term":1797,"definition":1798,"category":1402,"aliases":1799,"links":1802,"related":1805,"readMore":-1,"target":1806,"hasArticle":1356},"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.",[1800,1801],"REST API","Representational State Transfer",[1803],{"kind":1379,"url":1804},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FREST",[1490,1492],"\u002Fglossary#rest",{"slug":1783,"term":1808,"definition":1809,"category":1388,"aliases":1810,"links":1813,"related":1816,"readMore":-1,"target":1817,"hasArticle":1356},"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.",[1811,1812],"rate limit","throttling",[1814],{"kind":1379,"url":1815},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FRate_limiting",[1774],"\u002Fglossary#rate-limiting",{"slug":1536,"term":1819,"definition":1820,"category":1388,"aliases":1821,"links":1824,"related":1827,"readMore":-1,"target":1828,"hasArticle":1356},"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.",[1822,1823],"SOC2","System and Organization Controls",[1825],{"kind":1379,"url":1826},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FSystem_and_Organization_Controls",[1248,1524,1537],"\u002Fglossary#soc-2",{"slug":1830,"term":1831,"definition":1832,"category":1611,"aliases":1833,"links":1836,"related":1839,"readMore":-1,"target":1840,"hasArticle":1356},"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.",[1834,1835],"Software as a Service","software-as-a-service",[1837],{"kind":1379,"url":1838},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FSoftware_as_a_service",[1508,1507],"\u002Fglossary#saas",{"slug":1492,"term":1842,"definition":1843,"category":1634,"aliases":1844,"links":1846,"related":1849,"readMore":-1,"target":1850,"hasArticle":1356},"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.",[1845],"SSE",[1847],{"kind":1379,"url":1848},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FServer-sent_events",[1490,1409],"\u002Fglossary#server-sent-events",{"slug":1584,"term":1852,"definition":1853,"category":1402,"aliases":1854,"links":1857,"related":1860,"readMore":-1,"target":1861,"hasArticle":1356},"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.",[1855,1856],"SSR","server-rendered",[1858],{"kind":1379,"url":1859},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FServer-side_scripting",[1574],"\u002Fglossary#server-side-rendering",{"slug":1605,"term":1863,"definition":1864,"category":1347,"aliases":1865,"links":1868,"related":1873,"readMore":-1,"target":1874,"hasArticle":1356},"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.",[1866,1867],"Skia Graphics Engine","skia-safe",[1869,1871],{"kind":1352,"url":1870},"https:\u002F\u002Fskia.org\u002F",{"kind":1379,"url":1872},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FSkia_Graphics_Engine",[1597],"\u002Fglossary#skia",{"slug":511,"term":219,"definition":1876,"category":1611,"aliases":1877,"links":1880,"related":1881,"readMore":-1,"target":1883,"hasArticle":1356},"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.",[530,1878,1879],"dedicated developers","outstaffing",[],[1882,1771],"total-cost-of-ownership","\u002Fglossary#staff-augmentation",{"slug":1506,"term":1885,"definition":1886,"category":1388,"aliases":1887,"links":1890,"related":1891,"readMore":-1,"target":1892,"hasArticle":1356},"Staged rollout","Releasing a build to a small percentage of users first and widening only once the crash-free rate holds. A bad build caught at ten percent is a bad afternoon; the same build at a hundred percent is a bad week.",[1888,1889],"phased release","canary release",[],[1495,599],"\u002Fglossary#staged-rollout",{"slug":654,"term":855,"definition":1894,"category":1402,"aliases":1895,"links":1899,"related":1902,"readMore":-1,"target":1903,"hasArticle":1356},"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.",[1896,1897,1898],"state management","BLoC","Riverpod",[1900],{"kind":1364,"url":1901},"https:\u002F\u002Fdocs.flutter.dev\u002Fdata-and-backend\u002Fstate-mgmt\u002Foptions",[1540],"\u002Fglossary#state-management",{"slug":1478,"term":1905,"definition":1906,"category":1634,"aliases":1907,"links":1911,"related":1914,"readMore":-1,"target":1915,"hasArticle":1356},"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.",[1908,1909,1910],"SSL","HTTPS","Transport Layer Security",[1912],{"kind":1379,"url":1913},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FTransport_Layer_Security",[1468,1479],"\u002Fglossary#tls",{"slug":1771,"term":1917,"definition":1918,"category":1611,"aliases":1919,"links":1921,"related":1924,"readMore":-1,"target":1925,"hasArticle":1356},"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.",[1920,1771],"TTM",[1922],{"kind":1379,"url":1923},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FTime_to_market",[475,1882],"\u002Fglossary#time-to-market",{"slug":1882,"term":1927,"definition":1928,"category":1611,"aliases":1929,"links":1932,"related":1935,"readMore":-1,"target":1936,"hasArticle":1356},"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.",[1930,1931],"TCO","cost of ownership",[1933],{"kind":1379,"url":1934},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FTotal_cost_of_ownership",[1771],"\u002Fglossary#total-cost-of-ownership",{"slug":1938,"term":863,"definition":1939,"category":1634,"aliases":1940,"links":1942,"related":1947,"readMore":-1,"target":1949,"hasArticle":1356},"webrtc","The browser and mobile standard for sending audio, video and data directly between two devices, with servers involved only in introducing them to each other. It is what an in-app video call is built on when it is not a rented SDK.",[1941],"Web Real-Time Communication",[1943,1945],{"kind":1352,"url":1944},"https:\u002F\u002Fwebrtc.org\u002F",{"kind":1379,"url":1946},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FWebRTC",[1948,1490],"xmpp","\u002Fglossary#webrtc",{"slug":1490,"term":1951,"definition":1952,"category":1634,"aliases":1953,"links":1954,"related":1957,"readMore":-1,"target":1958,"hasArticle":1356},"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.",[],[1955],{"kind":1379,"url":1956},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FWebSocket",[1492,1409],"\u002Fglossary#websocket",{"slug":1507,"term":1960,"definition":1961,"category":1611,"aliases":1962,"links":1965,"related":1968,"readMore":1969,"target":1969,"hasArticle":835},"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.",[1963,1964],"white label","multi-tenant app",[1966],{"kind":1379,"url":1967},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FWhite-label_product",[475],"\u002Fglossary\u002Fwhite-label",{"slug":1948,"term":1971,"definition":1972,"category":1634,"aliases":1973,"links":1976,"related":1981,"readMore":-1,"target":1982,"hasArticle":1356},"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.",[1974,1975],"Jabber","Extensible Messaging and Presence Protocol",[1977,1979],{"kind":1352,"url":1978},"https:\u002F\u002Fxmpp.org\u002F",{"kind":1379,"url":1980},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FXMPP",[1938,1490],"\u002Fglossary#xmpp"]