[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"technologies":3,"\u002Fblog\u002Fflutter-vs-react-native-2026":167,"team-members":873,"blog-topics":1216,"mdc--12ftuw-key":1258,"glossary":1373},[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":855,"extension":856,"hero":857,"meta":860,"metaDescription":861,"metaTitle":862,"navigation":863,"ogDescription":864,"path":865,"seo":866,"slug":867,"stem":868,"summary":869,"timestamp":870,"topic":41,"updated":871,"__hash__":872},"blog_en\u002Fblog\u002Fflutter-vs-react-native-2026.md","Flutter vs React Native in 2026: The Honest Engineering Tradeoffs","nixan",{"type":172,"value":173,"toc":825},"minimark",[174,188,196,208,211,216,219,222,244,246,250,253,259,275,281,287,293,296,298,302,307,310,315,332,338,342,348,351,374,379,383,386,416,421,425,428,431,451,456,460,463,489,496,501,505,508,539,544,548,551,564,569,573,576,600,605,607,611,628,641,645,665,667,671,678,680,684,691,696,698,702,705,733,736,744,760,762,766,770,773,777,780,784,787,791,794,798,808,812,815],[175,176,177,181,182,187],"p",{},[178,179,180],"strong",{},"TL;DR."," In 2026, both Flutter and React Native are production-grade. Neither \"wins.\" The right choice is determined by your team, your UI requirements, how many surfaces you need (mobile only? mobile + web? desktop? embedded?), and how your hiring pipeline looks. We build in Flutter at ",[183,184,186],"a",{"href":185},"\u002F","Nerdy.pro"," because the economics work for our clients — but we've shipped real React Native work too, and this post is our honest comparison of where each one earns its place.",[175,189,190,191,195],{},"If you just want the answer: skip to ",[183,192,194],{"href":193},"#the-short-decision-framework","the decision framework",". If you want the engineering depth behind it, keep reading.",[175,197,198,199,202,203,207],{},"Comparing Flutter to ",[178,200,201],{},"native"," iOS\u002FAndroid (Swift, Kotlin) rather than to React Native? That's a separate decision — we cover it in ",[183,204,206],{"href":205},"\u002Fblog\u002Fflutter-vs-native-2026","Flutter vs Native in 2026",".",[209,210],"hr",{},[212,213,215],"h2",{"id":214},"why-we-wrote-this-post-and-why-its-different","Why we wrote this post (and why it's different)",[175,217,218],{},"Search \"flutter vs react native 2026\" and you'll find mostly the same listicle, rewritten a hundred times: a feature-matrix table, a handful of out-of-date talking points about \"the JS bridge,\" and a recommendation suspiciously aligned with whichever framework the author's agency sells.",[175,220,221],{},"We're a Flutter-first agency. We are not neutral. But we've used React Native enough — on production apps with real users — to tell you when it's the right answer. This post exists because our clients deserve a decision, not a sales pitch, and because the honest answer is more useful than the tribal one.",[175,223,224,225,229,230,229,234,238,239,243],{},"Where we give an opinion, it's grounded in work we've actually shipped. Four of those apps are public: ",[183,226,228],{"href":227},"\u002Fportfolio\u002Farcana","Arcana",", ",[183,231,233],{"href":232},"\u002Fportfolio\u002Fyoumi","YouMi",[183,235,237],{"href":236},"\u002Fportfolio\u002Fextraetf","ExtraETF",", and ",[183,240,242],{"href":241},"\u002Fportfolio\u002Fformtastic","Formtastic",". We'll refer to them below.",[209,245],{},[212,247,249],{"id":248},"what-actually-changed-between-2023-and-2026","What actually changed between 2023 and 2026",[175,251,252],{},"Most comparison posts are still arguing about things that got fixed. Before we compare anything, here's what you need to know about the current state of both frameworks.",[175,254,255,258],{},[178,256,257],{},"React Native's New Architecture is the default now, not an experiment."," Fabric (the new renderer), TurboModules (the new native module system), and the Bridgeless mode shipped in React Native 0.76 as defaults in late 2024. The \"JS bridge bottleneck\" argument that dominated 2020–2023 discourse is largely obsolete. Modern RN calls into native code synchronously through JSI, and the serialization overhead people used to complain about is gone on any project that has adopted the New Architecture. If your reference points are Airbnb's 2018 blog post or Discord's early criticisms, throw them out.",[175,260,261,270,271,274],{},[178,262,263,264,269],{},"Flutter's ",[265,266,268],"term",{"slug":267},"impeller","Impeller"," is no longer the \"new\" renderer."," Impeller replaced ",[265,272],{"slug":273},"skia"," as the default on iOS in 2023 and became the default on Android in 2024. It eliminated the shader-compilation jank that was Flutter's most visible production problem for years. If your last serious look at Flutter was 2022, the rendering story has changed materially.",[175,276,277,280],{},[178,278,279],{},"Expo is effectively the standard way to ship React Native now."," The \"bare React Native CLI\" workflow still exists, but in practice, new RN projects are Expo projects. Expo Router, EAS Build, and Expo's prebuild system have made RN's previously painful DX much closer to Flutter's. Comparisons that don't mention Expo are comparing against a version of RN that 2026 teams rarely use.",[175,282,283,286],{},[178,284,285],{},"Flutter on web, desktop, and embedded is real, but nuanced."," Flutter Web is production-ready for internal tools, admin panels, and app-like experiences — not for content sites or anything SEO-dependent. Flutter desktop (macOS, Windows, Linux) is stable. Flutter embedded has a real ecosystem (cars, kiosks, appliances). React Native's web story (via react-native-web, Solito, or Expo Router's web output) is also real but remains community-led rather than core.",[175,288,289,292],{},[178,290,291],{},"The hiring landscape has narrowed the gap."," In 2022, \"there are 10× more React devs than Dart devs\" was the standard counter-argument against Flutter. That's still directionally true, but the Flutter talent pool has matured dramatically. For senior roles — the people actually setting architecture — both frameworks have plenty of qualified engineers.",[175,294,295],{},"With that baseline set, let's compare.",[209,297],{},[212,299,301],{"id":300},"eight-dimensions-that-actually-matter","Eight dimensions that actually matter",[303,304,306],"h3",{"id":305},"_1-ui-fidelity-and-design-control","1. UI fidelity and design control",[175,308,309],{},"Flutter paints every pixel itself. React Native renders platform-native views (UIView on iOS, Android Views or Compose interop on Android).",[175,311,312],{},[178,313,314],{},"What this means in practice:",[316,317,318,325],"ul",{},[319,320,321,322,324],"li",{},"If your design system is bespoke — custom animations, non-standard controls, pixel-perfect identical look across iOS and Android — Flutter will be dramatically faster to implement. This was decisive for ",[183,323,228],{"href":227},", where the UI intentionally doesn't conform to either platform's conventions.",[319,326,327,328,331],{},"If your product needs to feel ",[329,330,201],"em",{}," — system-level context menus, native iOS navigation transitions, exact platform accessibility semantics — React Native has a real advantage. A banking app or a health app that users expect to feel like a \"normal\" iOS app will be easier to get right in RN.",[175,333,334,337],{},[178,335,336],{},"Honest call:"," RN wins if platform-native feel is a brand value. Flutter wins if design-system consistency is a brand value. Neither wins if you don't have a strong opinion.",[303,339,341],{"id":340},"_2-performance-and-rendering-architecture","2. Performance and rendering architecture",[175,343,344,345],{},"With both frameworks on their modern architectures (Impeller for Flutter, Fabric + Bridgeless for RN), raw rendering performance is close enough that ",[178,346,347],{},"most teams will not notice a difference in a typical CRUD app.",[175,349,350],{},"Where the gap still shows up:",[316,352,353,362,368],{},[319,354,355,358,359,361],{},[178,356,357],{},"High-frequency animation and custom drawing"," — Flutter's architecture (directly painting on the GPU, no reconciliation through a native view tree) still wins. If you're building a drawing app, a map-heavy product, a charting library, or a game-adjacent UI, Flutter is the right tool. We used this argument to choose Flutter for ",[183,360,237],{"href":236},", where the chart-heavy investor UI would have been painful in RN.",[319,363,364,367],{},[178,365,366],{},"Startup time on low-end Android"," — Flutter historically had a larger binary size and slower cold start. That's mostly solved in 2026, but on sub-2GB-RAM devices in emerging markets, RN with Hermes still tends to boot faster.",[319,369,370,373],{},[178,371,372],{},"Native module hot path"," — RN's JSI now makes sync native calls cheap. For apps whose performance is dominated by many small native calls (heavy hardware integration, IoT, BLE control), RN is measurably simpler.",[175,375,376,378],{},[178,377,336],{}," Flutter is the safer choice for animation-heavy or graphically complex UIs. RN is the safer choice if you're on tight binary-size budgets or have lots of native-module chatter.",[303,380,382],{"id":381},"_3-platform-breadth","3. Platform breadth",[175,384,385],{},"This is where Flutter is simply ahead in 2026.",[316,387,388,394,404,410],{},[319,389,390,393],{},[178,391,392],{},"Mobile (iOS + Android)"," — parity.",[319,395,396,399,400,403],{},[178,397,398],{},"Web"," — Flutter Web is core; RN Web exists as a community effort (react-native-web). If web is a first-class surface for you and you're not willing to maintain a parallel React codebase, Flutter is easier to reason about. If web is your ",[329,401,402],{},"primary"," surface and mobile is an afterthought, neither is the right answer — you want Next.js or Remix with native wrappers.",[319,405,406,409],{},[178,407,408],{},"Desktop (macOS, Windows, Linux)"," — Flutter is production-ready. RN-macOS and RN-Windows exist and are maintained by Microsoft, but are behind Flutter in library ecosystem completeness.",[319,411,412,415],{},[178,413,414],{},"Embedded (cars, kiosks, appliances)"," — Flutter has the only real story here. Toyota, BMW, Canonical, and others ship Flutter on embedded hardware. RN does not target this space.",[175,417,418,420],{},[178,419,336],{}," If you need more than iOS + Android, Flutter. If iOS + Android is the whole roadmap forever, neither platform has a breadth advantage.",[303,422,424],{"id":423},"_4-ecosystem-and-libraries","4. Ecosystem and libraries",[175,426,427],{},"React Native's ecosystem is larger and more mature in absolute terms. The npm ecosystem is JavaScript's, and RN inherits it.",[175,429,430],{},"Practical implications:",[316,432,433,439,445],{},[319,434,435,438],{},[178,436,437],{},"SDK coverage"," — Payment providers, analytics tools, auth services, CRM integrations almost always ship an RN SDK. Some ship a Flutter SDK too, but RN is the safer bet if your app's value lives in third-party integrations.",[319,440,441,444],{},[178,442,443],{},"Component libraries"," — RN has more off-the-shelf UI kits (especially tied to React's Web ecosystem). Flutter's component library is more curated but smaller in raw count.",[319,446,447,450],{},[178,448,449],{},"Package quality variance"," — Both ecosystems have quality issues in the long tail. Flutter's pub.dev has better typing and stronger null-safety guarantees than a typical npm package. If you've been burned by unmaintained RN libraries, that's a real concern.",[175,452,453,455],{},[178,454,336],{}," RN wins on ecosystem breadth. Flutter wins on ecosystem consistency.",[303,457,459],{"id":458},"_5-hiring-team-cost-and-ramp-up","5. Hiring, team cost, and ramp-up",[175,461,462],{},"This is where most decisions are actually made, even if the technical arguments get more airtime.",[316,464,465,471,477,483],{},[319,466,467,470],{},[178,468,469],{},"Pool size"," — More JavaScript\u002FReact engineers exist than Dart engineers. This is structural and won't change.",[319,472,473,476],{},[178,474,475],{},"Ramp-up from web"," — A React developer can contribute to an RN codebase in days. A Flutter codebase requires learning Dart (easy) and Flutter's widget model (takes a few weeks to stop fighting it).",[319,478,479,482],{},[178,480,481],{},"Senior talent"," — For senior roles, the pool-size argument weakens. Good senior mobile engineers are rare in both ecosystems.",[319,484,485,488],{},[178,486,487],{},"Agency pricing"," — In our experience pricing projects, Flutter agencies and RN agencies quote within 10% of each other for comparable scope. The cost difference is almost entirely ecosystem-dependent (see dimension 4) and project-specific, not framework-intrinsic.",[175,490,491,492,207],{},"For a detailed breakdown of how these variables translate into actual project cost, see our companion post: ",[183,493,495],{"href":494},"\u002Fblog\u002Fflutter-app-development-cost-2026","Flutter App Development Cost in 2026: Real Numbers from Real Projects",[175,497,498,500],{},[178,499,336],{}," If you already have a React team, the ramp cost for RN is near-zero. Don't retrain them on Dart just to use Flutter. If you're hiring fresh, the choice is closer than pool-size arguments suggest.",[303,502,504],{"id":503},"_6-developer-experience-and-tooling","6. Developer experience and tooling",[175,506,507],{},"Close, but with different flavor.",[316,509,510,516,522,528],{},[319,511,512,515],{},[178,513,514],{},"Hot reload"," — Both are fast. Flutter's is still marginally quicker and more reliable in our experience, especially after state-heavy changes.",[319,517,518,521],{},[178,519,520],{},"Build system"," — Expo (for RN) has closed most of the historical gap. A greenfield Expo project is genuinely pleasant. A bare-RN project is still rougher than a Flutter project at day one.",[319,523,524,527],{},[178,525,526],{},"Language"," — Dart is a small, predictable language. TypeScript is more powerful but more complex. This is personal preference; neither is clearly better for shipping apps.",[319,529,530,533,534,538],{},[178,531,532],{},"Tooling maturity"," — Flutter's IDE tooling (via ",[535,536,537],"code",{},"flutter doctor",", DevTools, and the Dart analyzer) is tightly integrated and usually the source of truth. RN's tooling depends more on which layers you pick (Metro, Hermes, Expo, Reanimated, etc.), which is more powerful but requires more judgment.",[175,540,541,543],{},[178,542,336],{}," Flutter's DX is more opinionated and a bit smoother out of the box. RN's DX is more configurable and rewards teams that know what they want.",[303,545,547],{"id":546},"_7-long-term-maintenance-and-upgrade-pain","7. Long-term maintenance and upgrade pain",[175,549,550],{},"A cross-platform framework is a 3-to-5-year decision. Upgrade cost matters more than most founders expect.",[316,552,553,558],{},[319,554,555,557],{},[178,556,39],{}," — Breaking changes are rare and well-signposted. Two-year-old Flutter codebases upgrade cleanly in a day of work.",[319,559,560,563],{},[178,561,562],{},"React Native"," — Historically upgrading RN was painful (the \"Upgrade Helper\" became famous for the wrong reasons). The New Architecture migration, now largely complete, was a multi-quarter undertaking for large teams. Expo has smoothed the upgrade path significantly, but RN still requires more upgrade discipline than Flutter.",[175,565,566,568],{},[178,567,336],{}," Flutter is the lower-maintenance choice over a 3-year horizon. The gap narrows if you stay on Expo's managed workflow.",[303,570,572],{"id":571},"_8-app-store-review-and-platform-policy-edge-cases","8. App Store review and platform-policy edge cases",[175,574,575],{},"Less famous, but expensive when it bites.",[316,577,578,588,594],{},[319,579,580,583,584,587],{},[178,581,582],{},"Apple 4.2.6 (the \"commercialized template\" rule)"," — Bites both frameworks equally. Neither framework triggers 4.2.6 on its own; it's triggered by how apps are differentiated from each other. Relevant mostly if you're running a ",[265,585,586],{"slug":586},"white-label"," or multi-tenant strategy.",[319,589,590,593],{},[178,591,592],{},"Binary size"," — RN apps tend to ship smaller than Flutter apps on Android. Usually not decisive, but a real consideration for apps with aggressive install-conversion targets.",[319,595,596,599],{},[178,597,598],{},"Accessibility"," — RN inherits the platform's native accessibility tree, which makes it easier to pass accessibility audits in enterprise sales. Flutter has its own accessibility layer that's good but requires more explicit care.",[175,601,602,604],{},[178,603,336],{}," For enterprise-sold products with strict accessibility or binary-size requirements, RN starts slightly ahead. For everything else, it's a wash.",[209,606],{},[212,608,610],{"id":609},"pick-flutter-if","Pick Flutter if…",[316,612,613,616,619,622,625],{},[319,614,615],{},"You want pixel-perfect UI consistency across iOS and Android (and often web + desktop).",[319,617,618],{},"Your product is UI-heavy, animation-heavy, or does custom rendering (charts, canvases, games, drawing tools).",[319,620,621],{},"You need more than mobile — web, desktop, or embedded are on the roadmap.",[319,623,624],{},"You value low upgrade and maintenance cost over 3–5 years.",[319,626,627],{},"You don't already have a React team.",[175,629,630,631,635,636,640],{},"This is why most of the projects in our ",[183,632,634],{"href":633},"\u002Fportfolio","portfolio"," are built in Flutter — it's the core of our ",[183,637,639],{"href":638},"\u002Fservices\u002Fflutter-app-development","Flutter app development"," practice.",[212,642,644],{"id":643},"pick-react-native-if","Pick React Native if…",[316,646,647,650,656,659,662],{},[319,648,649],{},"You already have a React or JavaScript team and want to minimize retraining.",[319,651,652,653,655],{},"Your product needs to feel ",[329,654,201],{}," — banking, healthcare, system utilities, or any context where users expect conformity to platform conventions.",[319,657,658],{},"Your app's value lives in third-party SDKs (payments, analytics, niche integrations) and you want the largest possible library surface.",[319,660,661],{},"You want to share code with a React web app without maintaining two codebases.",[319,663,664],{},"You ship primarily on Android with tight install-conversion KPIs and binary size is a measured concern.",[209,666],{},[212,668,670],{"id":669},"the-short-decision-framework","The short decision framework",[175,672,673,674,677],{},"If you want one paragraph, here it is. ",[178,675,676],{},"Pick React Native if your team is already React, your product should feel native, or your value lives in third-party SDKs. Pick Flutter if you own your design system, your roadmap extends beyond iOS + Android, or you want the lowest maintenance cost over the next three years."," If both halves of that sentence apply, the tiebreaker is team composition: use what your senior engineers will be fastest in.",[209,679],{},[212,681,683],{"id":682},"cost-implications","Cost implications",[175,685,686,687,690],{},"Framework choice influences cost, but usually less than product scope, design complexity, and integration count. The same ",[265,688],{"slug":689},"mvp"," built well in either framework will land within ±10% of the other in our pricing.",[175,692,693,694,207],{},"Where the cost gap becomes real is the long tail: maintenance, upgrade pain, and the engineering time spent wrapping native SDKs that don't ship a first-class package for your chosen framework. We wrote a separate post dissecting this with numbers from our own projects: ",[183,695,495],{"href":494},[209,697],{},[212,699,701],{"id":700},"how-we-approach-the-decision-at-nerdypro","How we approach the decision at Nerdy.pro",[175,703,704],{},"When a new client asks us whether they should use Flutter or React Native, we run a 30-minute call where we look at:",[706,707,708,713,718,723,728],"ol",{},[319,709,710],{},[178,711,712],{},"Who is on your team today, and who will maintain this in two years?",[319,714,715],{},[178,716,717],{},"What surfaces do you need to ship on — mobile only, or mobile + web + desktop?",[319,719,720],{},[178,721,722],{},"What are your three largest third-party integrations, and which frameworks do they support?",[319,724,725],{},[178,726,727],{},"How platform-native does the product need to feel?",[319,729,730],{},[178,731,732],{},"What's your timeline, and what's your cost ceiling?",[175,734,735],{},"If the answers strongly favor React Native, we say so and help you find a good RN shop. If they favor Flutter, we quote the project. If they're ambiguous — which is common — we build a small proof-of-concept in whichever framework the team is more likely to maintain.",[175,737,738,739,743],{},"If you'd like us to run this exercise on your product, ",[183,740,742],{"href":741},"\u002Fcontact","book a discovery call",". No slide deck, no pitch — just a technical call to get the decision right.",[175,745,746,747,750,751,229,753,229,755,238,757,759],{},"You can also see how this thinking plays out in practice by browsing ",[183,748,749],{"href":633},"our portfolio",": ",[183,752,228],{"href":227},[183,754,233],{"href":232},[183,756,237],{"href":236},[183,758,242],{"href":241}," each chose Flutter for a specific reason that we'd be happy to walk through on a call.",[209,761],{},[212,763,765],{"id":764},"faq","FAQ",[303,767,769],{"id":768},"is-react-native-dead-in-2026","Is React Native dead in 2026?",[175,771,772],{},"No. Meta continues to invest in it, the New Architecture shipped as default in 2024, and Expo has made the developer experience substantially better. React Native is growing, not declining. Anyone telling you otherwise is selling you something.",[303,774,776],{"id":775},"is-flutter-still-slower-to-start-than-native-on-android","Is Flutter still slower to start than native on Android?",[175,778,779],{},"Cold-start latency on low-end Android devices is Flutter's remaining weak spot. On mid-range and flagship devices, startup time is indistinguishable from native in a well-built app. If sub-2GB-RAM Android devices in emerging markets are a primary user segment, benchmark before committing.",[303,781,783],{"id":782},"should-i-use-flutter-for-a-content-heavy-website","Should I use Flutter for a content-heavy website?",[175,785,786],{},"No. Use Next.js, Remix, or another HTML-first framework. Flutter Web paints on canvas, which is bad for SEO and accessibility on content sites. Flutter Web is excellent for app-like experiences (dashboards, admin panels, interactive tools), not for blogs or marketing sites.",[303,788,790],{"id":789},"can-i-migrate-from-react-native-to-flutter-or-vice-versa","Can I migrate from React Native to Flutter (or vice versa)?",[175,792,793],{},"Yes, but it's effectively a rewrite. There are no meaningful shared artifacts between the two stacks. Budget it as a greenfield project, not a migration, and ask whether the switch solves a real problem before committing. In most cases, the pain of your current framework is not framework-level — it's architectural, and rewriting into the other framework just buys you the same architectural problems in a different language.",[303,795,797],{"id":796},"what-about-kotlin-multiplatform-or-swift-based-cross-platform","What about Kotlin Multiplatform or Swift-based cross-platform?",[175,799,800,803,804,207],{},[265,801,802],{"slug":76},"KMP"," is a credible third option for teams that want native UI on each platform while sharing business logic. It's narrower in scope than either Flutter or RN and is most compelling for organizations that already have strong Kotlin and Swift teams. We've evaluated it for clients but haven't yet shipped production work on it. The full comparison is now its own post: ",[183,805,807],{"href":806},"\u002Fblog\u002Fflutter-vs-kotlin-multiplatform-2026","Flutter vs Kotlin Multiplatform in 2026",[303,809,811],{"id":810},"does-the-choice-matter-for-an-mvp","Does the choice matter for an MVP?",[175,813,814],{},"Less than you think. The cost and timeline of a typical MVP (8–16 weeks) is dominated by scope decisions, not framework decisions. Pick the framework your team will ship fastest in, and revisit the choice at product-market fit when the real engineering decisions start.",[816,817,818],"post-credits",{},[175,819,820,821,824],{},"Want us to apply this framework to your product? ",[183,822,823],{"href":741},"Book a 30-minute call"," and we'll give you an honest recommendation, even if it means sending you to someone else.",{"title":826,"searchDepth":827,"depth":827,"links":828},"",2,[829,830,831,842,843,844,845,846,847],{"id":214,"depth":827,"text":215},{"id":248,"depth":827,"text":249},{"id":300,"depth":827,"text":301,"children":832},[833,835,836,837,838,839,840,841],{"id":305,"depth":834,"text":306},3,{"id":340,"depth":834,"text":341},{"id":381,"depth":834,"text":382},{"id":423,"depth":834,"text":424},{"id":458,"depth":834,"text":459},{"id":503,"depth":834,"text":504},{"id":546,"depth":834,"text":547},{"id":571,"depth":834,"text":572},{"id":609,"depth":827,"text":610},{"id":643,"depth":827,"text":644},{"id":669,"depth":827,"text":670},{"id":682,"depth":827,"text":683},{"id":700,"depth":827,"text":701},{"id":764,"depth":827,"text":765,"children":848},[849,850,851,852,853,854],{"id":768,"depth":834,"text":769},{"id":775,"depth":834,"text":776},{"id":782,"depth":834,"text":783},{"id":789,"depth":834,"text":790},{"id":796,"depth":834,"text":797},{"id":810,"depth":834,"text":811},"TL;DR. In 2026, both Flutter and React Native are production-grade. Neither \"wins.\" The right choice is determined by your team, your UI requirements, how many surfaces you need (mobile only? mobile + web? desktop? embedded?), and how your hiring pipeline looks. We build in Flutter at Nerdy.pro because the economics work for our clients — but we've shipped real React Native work too, and this post is our honest comparison of where each one earns its place.","md",{"type":858,"src":859},"image","\u002Fblog\u002Fflutter-vs-react-native-2026.webp",{},"A Flutter agency's honest comparison of Flutter and React Native in 2026: cost, performance, UX, maintenance, and a framework for deciding.","Flutter vs React Native in 2026",true,"A Flutter agency on when we would pick React Native instead. Eight dimensions, examples from apps we shipped, and no pretence that one always wins.","\u002Fblog\u002Fflutter-vs-react-native-2026",{"title":169,"description":855},"flutter-vs-react-native-2026","blog\u002Fflutter-vs-react-native-2026","A Flutter shop's honest take on when to pick React Native instead — 8 dimensions compared, with real examples from apps we've shipped.","2026-04-20T11:25:20Z","2026-09-04T09:00:00Z","k0MxLLx6MW38mTC-LvmaZO_ypW4lnetfgdOpaMiWnpk",[874,931,979,1029,1118,1170],{"id":875,"bio":876,"expertise":881,"extension":897,"links":898,"meta":902,"metaDescription":903,"name":908,"ogDescription":911,"photo":916,"role":917,"seniority":922,"skills":923,"slug":924,"specialization":925,"stem":924,"__hash__":930},"team_members\u002Fdima.yaml",{"en":877,"ru":878,"es":879,"nl":880},"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",[882,885,890,892],{"en":883,"ru":883,"es":884,"nl":883},"State management","Gestión de estado",{"en":886,"ru":887,"es":888,"nl":889},"Application architecture","Архитектура приложений","Arquitectura de aplicaciones","Applicatiearchitectuur",{"en":891,"ru":891,"es":891,"nl":891},"WebRTC",{"en":893,"ru":894,"es":895,"nl":896},"XMPP messaging","Обмен сообщениями по XMPP","Mensajería XMPP","Berichten via XMPP","yaml",[899],{"type":900,"address":901},"email","konopatov@nerdy.pro",{},{"en":904,"ru":905,"es":906,"nl":907},"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":909,"ru":910,"es":909,"nl":909},"Dima","Дима",{"en":912,"ru":913,"es":914,"nl":915},"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":918,"ru":919,"es":920,"nl":921},"Lead Flutter Developer","Ведущий Flutter-разработчик","Lead de desarrollo Flutter","Lead Flutter-developer","lead",[41,18,155,160,90,111,150,95],"dima",{"en":926,"ru":927,"es":928,"nl":929},"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":932,"bio":933,"expertise":938,"extension":897,"links":949,"meta":950,"metaDescription":951,"name":956,"ogDescription":959,"photo":964,"role":965,"seniority":970,"skills":971,"slug":972,"specialization":973,"stem":972,"__hash__":978},"team_members\u002Fmasha.yaml",{"en":934,"ru":935,"es":936,"nl":937},"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",[939,944],{"en":940,"ru":941,"es":942,"nl":943},"UI\u002FUX design","UI\u002FUX-дизайн","Diseño UI\u002FUX","UI\u002FUX-ontwerp",{"en":945,"ru":946,"es":947,"nl":948},"Product copywriting","Продуктовый копирайтинг","Redacción de producto","Productteksten",null,{},{"en":952,"ru":953,"es":954,"nl":955},"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":957,"ru":958,"es":957,"nl":957},"Masha","Маша",{"en":960,"ru":961,"es":962,"nl":963},"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":966,"ru":967,"es":968,"nl":969},"Flutter Developer","Flutter-разработчик","Desarrolladora Flutter","Flutter-developer","middle",[41,18],"masha",{"en":974,"ru":975,"es":976,"nl":977},"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":980,"bio":981,"expertise":986,"extension":897,"links":997,"meta":1000,"metaDescription":1001,"name":1006,"ogDescription":1009,"photo":1014,"role":1015,"seniority":1020,"skills":1021,"slug":1022,"specialization":1023,"stem":1022,"__hash__":1028},"team_members\u002Fmaxim.yaml",{"en":982,"ru":983,"es":984,"nl":985},"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",[987,992],{"en":988,"ru":989,"es":990,"nl":991},"Automated testing","Автоматизированное тестирование","Testing automatizado","Geautomatiseerd testen",{"en":993,"ru":994,"es":995,"nl":996},"High-load backend systems","Высоконагруженные бэкенд-системы","Sistemas backend de alta carga","Backendsystemen met hoge belasting",[998],{"type":900,"address":999},"maxim@nerdy.pro",{},{"en":1002,"ru":1003,"es":1004,"nl":1005},"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":1007,"ru":1008,"es":1007,"nl":1007},"Maxim","Максим",{"en":1010,"ru":1011,"es":1012,"nl":1013},"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":1016,"ru":1017,"es":1018,"nl":1019},"Senior Software Engineer","Старший инженер-программист","Ingeniero de software senior","Senior software engineer","senior",[41,18,51,106,155,13,150],"maxim",{"en":1024,"ru":1025,"es":1026,"nl":1027},"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":1030,"bio":1031,"expertise":1036,"extension":897,"links":1078,"meta":1090,"metaDescription":1091,"name":1096,"ogDescription":1099,"photo":1104,"role":1105,"seniority":1110,"skills":1111,"slug":170,"specialization":1112,"stem":170,"__hash__":1117},"team_members\u002Fnixan.yaml",{"en":1032,"ru":1033,"es":1034,"nl":1035},"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",[1037,1042,1047,1052,1057,1062,1067,1072,1074,1076],{"en":1038,"ru":1039,"es":1040,"nl":1041},"iOS development","Разработка под iOS","Desarrollo iOS","iOS-ontwikkeling",{"en":1043,"ru":1044,"es":1045,"nl":1046},"Software architecture","Архитектура ПО","Arquitectura de software","Softwarearchitectuur",{"en":1048,"ru":1049,"es":1050,"nl":1051},"Engineering team leadership","Руководство инженерными командами","Liderazgo de equipos de ingeniería","Leidinggeven aan engineeringteams",{"en":1053,"ru":1054,"es":1055,"nl":1056},"Payment systems","Платёжные системы","Sistemas de pago","Betaalsystemen",{"en":1058,"ru":1059,"es":1060,"nl":1061},"Card processing","Карточный процессинг","Procesamiento de tarjetas","Kaartverwerking",{"en":1063,"ru":1064,"es":1065,"nl":1066},"PCI-DSS compliance","Соответствие PCI-DSS","Cumplimiento de PCI-DSS","Naleving van PCI-DSS",{"en":1068,"ru":1069,"es":1070,"nl":1071},"NFC and contactless payments","NFC и бесконтактные платежи","NFC y pagos contactless","NFC en contactloos betalen",{"en":1073,"ru":1073,"es":1073,"nl":1073},"Host Card Emulation",{"en":1075,"ru":1075,"es":1075,"nl":1075},"EMV Contactless",{"en":1077,"ru":1077,"es":1077,"nl":1077},"AOSP",[1079,1082,1085,1088],{"type":1080,"url":1081},"github","https:\u002F\u002Fgithub.com\u002Fthenixan",{"type":1083,"url":1084},"linkedin","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fthenixan\u002F",{"type":1086,"url":1087},"telegram","https:\u002F\u002Ft.me\u002Fthenixan",{"type":900,"address":1089},"nixan@nerdy.pro",{},{"en":1092,"ru":1093,"es":1094,"nl":1095},"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":1097,"ru":1098,"es":1097,"nl":1097},"Ilya Nixan","Илья Никсан",{"en":1100,"ru":1101,"es":1102,"nl":1103},"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":1106,"ru":1107,"es":1108,"nl":1109},"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":1113,"ru":1114,"es":1115,"nl":1116},"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":1119,"bio":1120,"expertise":1125,"extension":897,"links":1137,"meta":1142,"metaDescription":1143,"name":1148,"ogDescription":1151,"photo":1156,"role":1157,"seniority":1020,"skills":1162,"slug":1163,"specialization":1164,"stem":1163,"__hash__":1169},"team_members\u002Froma.yaml",{"en":1121,"ru":1122,"es":1123,"nl":1124},"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",[1126,1127,1132],{"en":1038,"ru":1039,"es":1040,"nl":1041},{"en":1128,"ru":1129,"es":1130,"nl":1131},"Applied AI","Прикладной AI","IA aplicada","Toegepaste AI",{"en":1133,"ru":1134,"es":1135,"nl":1136},"ERP and CRM systems","ERP- и CRM-системы","Sistemas ERP y CRM","ERP- en CRM-systemen",[1138,1140],{"type":1083,"url":1139},"https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fromanbatler\u002F",{"type":900,"address":1141},"roma@nerdy.pro",{},{"en":1144,"ru":1145,"es":1146,"nl":1147},"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":1149,"ru":1150,"es":1149,"nl":1149},"Roman","Рома",{"en":1152,"ru":1153,"es":1154,"nl":1155},"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":1158,"ru":1159,"es":1160,"nl":1161},"Senior Mobile Developer","Старший мобильный разработчик","Desarrollador móvil senior","Senior mobiele developer",[7,41,18,141,146,106],"roma",{"en":1165,"ru":1166,"es":1167,"nl":1168},"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":1171,"bio":1172,"expertise":1177,"extension":897,"links":949,"meta":1188,"metaDescription":1189,"name":1194,"ogDescription":1197,"photo":1202,"role":1203,"seniority":1020,"skills":1208,"slug":1209,"specialization":1210,"stem":1209,"__hash__":1215},"team_members\u002Fxsox.yaml",{"en":1173,"ru":1174,"es":1175,"nl":1176},"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",[1178,1183],{"en":1179,"ru":1180,"es":1181,"nl":1182},"API design","Проектирование API","Diseño de APIs","API-ontwerp",{"en":1184,"ru":1185,"es":1186,"nl":1187},"Data modelling","Моделирование данных","Modelado de datos","Datamodellering",{},{"en":1190,"ru":1191,"es":1192,"nl":1193},"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":1195,"ru":1196,"es":1195,"nl":1195},"Eugene Xsox","Женя Xsox",{"en":1198,"ru":1199,"es":1200,"nl":1201},"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":1204,"ru":1205,"es":1206,"nl":1207},"Senior Backend Developer","Старший бэкенд-разработчик","Desarrollador backend senior","Senior backenddeveloper",[106,24,41,18,155,160,90,150],"xsox",{"en":1211,"ru":1212,"es":1213,"nl":1214},"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",[1217,1226,1233,1238,1248],{"id":1218,"extension":897,"meta":1219,"name":1220,"slug":1224,"stem":1224,"__hash__":1225},"blog_topics\u002Fcybersecurity.yaml",{},{"en":1221,"ru":1222,"es":1223,"nl":1221},"Cybersecurity","Кибербезопасность","Ciberseguridad","cybersecurity","kt1rdsMy5W4b9MvGHm6mZVCr0inHidEuqaosPYmmk4E",{"id":1227,"extension":897,"meta":1228,"name":1229,"slug":1231,"stem":1231,"__hash__":1232},"blog_topics\u002Fdevops.yaml",{},{"en":1230,"ru":1230,"es":1230,"nl":1230},"DevOps","devops","D3mxlZuFHKCGeszKZuWCiQmHmP5EiCvzg1qEAIQhnyU",{"id":1234,"extension":897,"meta":1235,"name":1236,"slug":41,"stem":41,"__hash__":1237},"blog_topics\u002Fflutter.yaml",{},{"en":39,"ru":39,"es":39,"nl":39},"OOeALAmwFuEqByuJvTGk4g15FIHENPfYMdpfZh_HTAE",{"id":1239,"extension":897,"meta":1240,"name":1241,"slug":1246,"stem":1246,"__hash__":1247},"blog_topics\u002Ffor-founders.yaml",{},{"en":1242,"ru":1243,"es":1244,"nl":1245},"For Founders","Для основателей","Para fundadores","Voor oprichters","for-founders","lp2u6Ol2qF4DGxpB83HxbbGzWioT-e40mJhD4lr28-U",{"id":1249,"extension":897,"meta":1250,"name":1251,"slug":1256,"stem":1256,"__hash__":1257},"blog_topics\u002Fsoftware-engineering.yaml",{},{"en":1252,"ru":1253,"es":1254,"nl":1255},"Software Engineering","Разработка ПО","Ingeniería de software","Software-engineering","software-engineering","aZMb3aUDptoFQk_cEE6l5H4wrYcgZuBYUubmKqOAaaU",{"data":1259,"body":1260},{},{"type":1261,"children":1262},"root",[1263,1270,1288,1299,1324],{"type":1264,"tag":175,"props":1265,"children":1266},"element",{},[1267],{"type":1268,"value":1269},"text","Ilya founded Nerdy Production and leads its engineering. He has been building software since 2010 and shipping production Flutter since 2018.",{"type":1264,"tag":175,"props":1271,"children":1272},{},[1273,1275,1279,1281,1286],{"type":1268,"value":1274},"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":1264,"tag":265,"props":1276,"children":1278},{"slug":1277},"pci-dss",[],{"type":1268,"value":1280}," scope, and contactless payments — including building contactless card payments on Android via ",{"type":1264,"tag":265,"props":1282,"children":1284},{"slug":1283},"host-card-emulation",[1285],{"type":1268,"value":1073},{"type":1268,"value":1287}," over ISO\u002FIEC 14443, with EMV Contactless (Visa PayWave) on top.",{"type":1264,"tag":175,"props":1289,"children":1290},{},[1291,1293,1297],{"type":1268,"value":1292},"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":1264,"tag":265,"props":1294,"children":1296},{"slug":1295},"aosp",[],{"type":1268,"value":1298},", giving him a low-level view of Android most app developers never touch.",{"type":1264,"tag":175,"props":1300,"children":1301},{},[1302,1304,1308,1310,1314,1316,1322],{"type":1268,"value":1303},"Today he leads delivery on the agency's flagship apps — from the chart-heavy fintech UI of ",{"type":1264,"tag":183,"props":1305,"children":1306},{"href":236},[1307],{"type":1268,"value":237},{"type":1268,"value":1309}," to the fully custom design system of ",{"type":1264,"tag":183,"props":1311,"children":1312},{"href":227},[1313],{"type":1268,"value":228},{"type":1268,"value":1315},". He writes most of the essays on this blog and maintains the agency's open-source work, including the ",{"type":1264,"tag":183,"props":1317,"children":1319},{"href":1318},"\u002Fopen-source\u002Fdxpdf",[1320],{"type":1268,"value":1321},"dxpdf",{"type":1268,"value":1323}," DOCX-to-PDF engine.",{"type":1264,"tag":175,"props":1325,"children":1326},{},[1327,1329,1334,1336,1341,1342,1347,1348,1353,1354,1359,1360,1365,1366,1371],{"type":1268,"value":1328},"He works across ",{"type":1264,"tag":183,"props":1330,"children":1332},{"href":1331},"\u002Ftechnologies\u002Fflutter",[1333],{"type":1268,"value":39},{"type":1268,"value":1335},", native iOS and Android, ",{"type":1264,"tag":183,"props":1337,"children":1339},{"href":1338},"\u002Ftechnologies\u002Fgo",[1340],{"type":1268,"value":49},{"type":1268,"value":229},{"type":1264,"tag":183,"props":1343,"children":1345},{"href":1344},"\u002Ftechnologies\u002Frust",[1346],{"type":1268,"value":124},{"type":1268,"value":229},{"type":1264,"tag":183,"props":1349,"children":1351},{"href":1350},"\u002Ftechnologies\u002Ftypescript",[1352],{"type":1268,"value":153},{"type":1268,"value":229},{"type":1264,"tag":183,"props":1355,"children":1357},{"href":1356},"\u002Ftechnologies\u002Fkotlin",[1358],{"type":1268,"value":69},{"type":1268,"value":229},{"type":1264,"tag":183,"props":1361,"children":1363},{"href":1362},"\u002Ftechnologies\u002Fkubernetes",[1364],{"type":1268,"value":78},{"type":1268,"value":238},{"type":1264,"tag":183,"props":1367,"children":1369},{"href":1368},"\u002Ftechnologies\u002Fdocker",[1370],{"type":1268,"value":27},{"type":1268,"value":1372},", with a focus on app architecture, cross-platform delivery, and building teams that ship.",[1374,1386,1399,1414,1428,1442,1458,1470,1484,1497,1511,1524,1539,1552,1568,1581,1592,1602,1615,1625,1633,1648,1657,1670,1683,1689,1699,1711,1722,1737,1749,1762,1774,1786,1798,1810,1821,1832,1843,1854,1866,1876,1887,1900,1912,1921,1933,1945,1955,1966,1979,1988,1999],{"slug":1295,"term":1077,"definition":1375,"category":1376,"aliases":1377,"links":1379,"related":1383,"readMore":-1,"target":1384,"hasArticle":1385},"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",[1378],"Android Open Source Project",[1380],{"kind":1381,"url":1382},"website","https:\u002F\u002Fsource.android.com\u002F",[1283],"\u002Fglossary#aosp",false,{"slug":1387,"term":1388,"definition":1389,"category":1376,"aliases":1390,"links":1391,"related":1395,"readMore":-1,"target":1398,"hasArticle":1385},"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.",[],[1392],{"kind":1393,"url":1394},"documentation","https:\u002F\u002Fdeveloper.apple.com\u002Fapp-clips\u002F",[1396,1397],"deep-linking","install-referrer","\u002Fglossary#app-clips",{"slug":1400,"term":1401,"definition":1402,"category":1376,"aliases":1403,"links":1404,"related":1410,"readMore":-1,"target":1413,"hasArticle":1385},"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.",[],[1405,1407],{"kind":1381,"url":1406},"https:\u002F\u002Fcloud.google.com\u002Fbigquery",{"kind":1408,"url":1409},"wikipedia","https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FBigQuery",[1411,1412],"object-storage","elasticsearch","\u002Fglossary#bigquery",{"slug":1415,"term":1416,"definition":1417,"category":1418,"aliases":1419,"links":1423,"related":1426,"readMore":-1,"target":1427,"hasArticle":1385},"ci-cd","CI\u002FCD","Automation that builds, tests and ships every change without anyone running commands by hand. On mobile it is what turns a release into a button press instead of an afternoon of someone else being unavailable.","practice",[1420,1421,1422],"CI","continuous integration","continuous delivery",[1424],{"kind":1408,"url":1425},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FCI\u002FCD",[],"\u002Fglossary#ci-cd",{"slug":1429,"term":1430,"definition":1431,"category":1432,"aliases":1433,"links":1435,"related":1438,"readMore":-1,"target":1441,"hasArticle":1385},"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",[1434],"Create, Read, Update, Delete",[1436],{"kind":1408,"url":1437},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FCreate,_read,_update_and_delete",[1439,1440],"rest","graphql","\u002Fglossary#crud",{"slug":1443,"term":1444,"definition":1445,"category":1432,"aliases":1446,"links":1451,"related":1454,"readMore":-1,"target":1457,"hasArticle":1385},"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.",[1447,1448,1449,1450],"image registry","Docker registry","GHCR","ghcr.io",[1452],{"kind":1393,"url":1453},"https:\u002F\u002Fdocs.github.com\u002Fen\u002Fpackages\u002Fworking-with-a-github-packages-registry\u002Fworking-with-the-container-registry",[1455,1456],"dev-container","multi-arch-image","\u002Fglossary#container-registry",{"slug":1396,"term":1459,"definition":1460,"category":1376,"aliases":1461,"links":1465,"related":1468,"readMore":1469,"target":1469,"hasArticle":863},"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.",[1462,1463,1464],"deferred deep linking","universal links","Android App Links",[1466],{"kind":1408,"url":1467},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FMobile_deep_linking",[1387,1397],"\u002Fglossary\u002Fdeep-linking",{"slug":1455,"term":1471,"definition":1472,"category":1418,"aliases":1473,"links":1477,"related":1482,"readMore":-1,"target":1483,"hasArticle":1385},"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.",[1474,1475,1476],"devcontainer.json","Dev Containers","VS Code Dev Containers",[1478,1480],{"kind":1381,"url":1479},"https:\u002F\u002Fcontainers.dev\u002F",{"kind":1393,"url":1481},"https:\u002F\u002Fcode.visualstudio.com\u002Fdocs\u002Fdevcontainers\u002Fcontainers",[1443],"\u002Fglossary#dev-container",{"slug":1412,"term":1485,"definition":1486,"category":1376,"aliases":1487,"links":1490,"related":1495,"readMore":-1,"target":1496,"hasArticle":1385},"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\".",[1488,1489],"Elastic","ELK",[1491,1493],{"kind":1381,"url":1492},"https:\u002F\u002Fwww.elastic.co\u002Felasticsearch",{"kind":1408,"url":1494},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FElasticsearch",[1400],"\u002Fglossary#elasticsearch",{"slug":1498,"term":1499,"definition":1500,"category":1432,"aliases":1501,"links":1504,"related":1507,"readMore":-1,"target":1510,"hasArticle":1385},"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.",[1502,1503],"E2EE","end-to-end encrypted",[1505],{"kind":1408,"url":1506},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FEnd-to-end_encryption",[1508,1509],"tls","jwt","\u002Fglossary#end-to-end-encryption",{"slug":1512,"term":1513,"definition":1514,"category":1432,"aliases":1515,"links":1518,"related":1519,"readMore":-1,"target":1523,"hasArticle":1385},"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.",[1516,1517],"fanout","broadcast",[],[1520,1521,1522],"websocket","pub-sub","server-sent-events","\u002Fglossary#fan-out",{"slug":1525,"term":1526,"definition":1527,"category":1418,"aliases":1528,"links":1532,"related":1535,"readMore":-1,"target":1538,"hasArticle":1385},"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.",[1529,1530,1531],"feature flag","feature toggle","feature gating",[1533],{"kind":1408,"url":1534},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FFeature_toggle",[1536,586,1537],"staged-rollout","multi-tenancy","\u002Fglossary#feature-flags",{"slug":1540,"term":1541,"definition":1542,"category":1432,"aliases":1543,"links":1547,"related":1550,"readMore":-1,"target":1551,"hasArticle":1385},"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.",[1544,1545,1546],"IEEE 754","double","floating-point arithmetic",[1548],{"kind":1408,"url":1549},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FIEEE_754",[],"\u002Fglossary#floating-point",{"slug":1553,"term":1554,"definition":1555,"category":1418,"aliases":1556,"links":1559,"related":1564,"readMore":-1,"target":1567,"hasArticle":1385},"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.",[1557,1558],"General Data Protection Regulation","data protection",[1560,1562],{"kind":1381,"url":1561},"https:\u002F\u002Fgdpr.eu\u002F",{"kind":1408,"url":1563},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FGeneral_Data_Protection_Regulation",[1277,1565,1566],"soc-2","hipaa","\u002Fglossary#gdpr",{"slug":1569,"term":1570,"definition":1571,"category":1418,"aliases":1572,"links":1576,"related":1579,"readMore":-1,"target":1580,"hasArticle":1385},"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.",[1573,1574,1575],"golden tests","screenshot test","snapshot test",[1577],{"kind":1393,"url":1578},"https:\u002F\u002Fapi.flutter.dev\u002Fflutter\u002Fflutter_test\u002FmatchesGoldenFile.html",[1415],"\u002Fglossary#golden-test",{"slug":1440,"term":1582,"definition":1583,"category":1432,"aliases":1584,"links":1585,"related":1590,"readMore":-1,"target":1591,"hasArticle":1385},"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.",[],[1586,1588],{"kind":1381,"url":1587},"https:\u002F\u002Fgraphql.org\u002F",{"kind":1408,"url":1589},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FGraphQL",[1439],"\u002Fglossary#graphql",{"slug":1566,"term":1593,"definition":1594,"category":1418,"aliases":1595,"links":1597,"related":1600,"readMore":-1,"target":1601,"hasArticle":1385},"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.",[1596],"Health Insurance Portability and Accountability Act",[1598],{"kind":1408,"url":1599},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FHealth_Insurance_Portability_and_Accountability_Act",[1277,1553,1565],"\u002Fglossary#hipaa",{"slug":1603,"term":1604,"definition":1605,"category":1432,"aliases":1606,"links":1609,"related":1612,"readMore":-1,"target":1614,"hasArticle":1385},"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.",[1607,1608],"headless content management system","content API",[1610],{"kind":1408,"url":1611},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FHeadless_content_management_system",[1613,1439],"server-side-rendering","\u002Fglossary#headless-cms",{"slug":1283,"term":1073,"definition":1616,"category":1376,"aliases":1617,"links":1620,"related":1623,"readMore":-1,"target":1624,"hasArticle":1385},"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.",[1618,1075,1619],"HCE","contactless payments",[1621],{"kind":1393,"url":1622},"https:\u002F\u002Fdeveloper.android.com\u002Fdevelop\u002Fconnectivity\u002Fnfc\u002Fhce",[1277,1295],"\u002Fglossary#host-card-emulation",{"slug":267,"term":268,"definition":1626,"category":1376,"aliases":1627,"links":1628,"related":1631,"readMore":-1,"target":1632,"hasArticle":1385},"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.",[],[1629],{"kind":1393,"url":1630},"https:\u002F\u002Fdocs.flutter.dev\u002Fperf\u002Fimpeller",[273],"\u002Fglossary#impeller",{"slug":1634,"term":1635,"definition":1636,"category":1637,"aliases":1638,"links":1642,"related":1645,"readMore":-1,"target":1647,"hasArticle":1385},"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",[1639,1640,1641],"IAP","in-app purchases","in-app subscription",[1643],{"kind":1393,"url":1644},"https:\u002F\u002Fdeveloper.apple.com\u002Fin-app-purchase\u002F",[1646],"product-market-fit","\u002Fglossary#in-app-purchase",{"slug":1397,"term":1649,"definition":1650,"category":1376,"aliases":1651,"links":1652,"related":1655,"readMore":-1,"target":1656,"hasArticle":1385},"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.",[],[1653],{"kind":1393,"url":1654},"https:\u002F\u002Fdeveloper.android.com\u002Fgoogle\u002Fplay\u002Finstallreferrer",[1396,1387],"\u002Fglossary#install-referrer",{"slug":1509,"term":1658,"definition":1659,"category":1660,"aliases":1661,"links":1663,"related":1668,"readMore":-1,"target":1669,"hasArticle":1385},"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",[1662],"JSON Web Token",[1664,1666],{"kind":1381,"url":1665},"https:\u002F\u002Fjwt.io\u002F",{"kind":1408,"url":1667},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FJSON_Web_Token",[1277],"\u002Fglossary#jwt",{"slug":1671,"term":1672,"definition":1673,"category":1418,"aliases":1674,"links":1678,"related":1681,"readMore":-1,"target":1682,"hasArticle":1385},"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.",[1675,1676,1677],"Know Your Customer","AML","KYC\u002FAML",[1679],{"kind":1408,"url":1680},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FKnow_your_customer",[1277,1553],"\u002Fglossary#kyc",{"slug":76,"term":74,"definition":1684,"category":1376,"aliases":1685,"links":1686,"related":1687,"readMore":1688,"target":1688,"hasArticle":1385},"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.",[802],[],[],"\u002Ftechnologies\u002Fkmp",{"slug":689,"term":1690,"definition":1691,"category":1637,"aliases":1692,"links":1694,"related":1697,"readMore":-1,"target":1698,"hasArticle":1385},"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.",[1693],"minimum viable product",[1695],{"kind":1408,"url":1696},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FMinimum_viable_product",[586],"\u002Fglossary#mvp",{"slug":1456,"term":1700,"definition":1701,"category":1432,"aliases":1702,"links":1706,"related":1709,"readMore":-1,"target":1710,"hasArticle":1385},"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.",[1703,1704,1705],"multi-arch build","multi-platform image","linux\u002Famd64 + linux\u002Farm64",[1707],{"kind":1393,"url":1708},"https:\u002F\u002Fdocs.docker.com\u002Fbuild\u002Fbuilding\u002Fmulti-platform\u002F",[1443],"\u002Fglossary#multi-arch-image",{"slug":1537,"term":1712,"definition":1713,"category":1432,"aliases":1714,"links":1717,"related":1720,"readMore":-1,"target":1721,"hasArticle":1385},"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.",[1715,1716],"multi-tenant","tenant",[1718],{"kind":1408,"url":1719},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FMultitenancy",[586,1525],"\u002Fglossary#multi-tenancy",{"slug":1723,"term":1724,"definition":1725,"category":1660,"aliases":1726,"links":1730,"related":1735,"readMore":-1,"target":1736,"hasArticle":1385},"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.",[1727,1728,1729],"OAuth 2.0","social login","Sign in with Apple",[1731,1733],{"kind":1381,"url":1732},"https:\u002F\u002Foauth.net\u002F2\u002F",{"kind":1408,"url":1734},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FOAuth",[1509],"\u002Fglossary#oauth",{"slug":1411,"term":1738,"definition":1739,"category":1432,"aliases":1740,"links":1744,"related":1747,"readMore":-1,"target":1748,"hasArticle":1385},"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.",[1741,1742,1743],"S3","S3-compatible storage","blob storage",[1745],{"kind":1408,"url":1746},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FObject_storage",[1400],"\u002Fglossary#object-storage",{"slug":1277,"term":1750,"definition":1751,"category":1418,"aliases":1752,"links":1755,"related":1760,"readMore":-1,"target":1761,"hasArticle":1385},"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.",[1753,1754],"PCI DSS","Payment Card Industry Data Security Standard",[1756,1758],{"kind":1381,"url":1757},"https:\u002F\u002Fwww.pcisecuritystandards.org\u002F",{"kind":1408,"url":1759},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FPayment_Card_Industry_Data_Security_Standard",[1509],"\u002Fglossary#pci-dss",{"slug":1763,"term":1764,"definition":1765,"category":1376,"aliases":1766,"links":1769,"related":1772,"readMore":-1,"target":1773,"hasArticle":1385},"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.",[1767,1768],"platform channel","method channel",[1770],{"kind":1393,"url":1771},"https:\u002F\u002Fdocs.flutter.dev\u002Fplatform-integration\u002Fplatform-channels",[76],"\u002Fglossary#platform-channels",{"slug":1775,"term":1776,"definition":1777,"category":1660,"aliases":1778,"links":1781,"related":1784,"readMore":-1,"target":1785,"hasArticle":1385},"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.",[1779,1780],"PQC","post-quantum crypto",[1782],{"kind":1408,"url":1783},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FPost-quantum_cryptography",[1508,1498],"\u002Fglossary#post-quantum-cryptography",{"slug":1646,"term":1787,"definition":1788,"category":1637,"aliases":1789,"links":1792,"related":1795,"readMore":-1,"target":1797,"hasArticle":1385},"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.",[1790,1791],"PMF","product\u002Fmarket fit",[1793],{"kind":1408,"url":1794},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FProduct-market_fit",[689,1796],"time-to-market","\u002Fglossary#product-market-fit",{"slug":1799,"term":1800,"definition":1801,"category":1418,"aliases":1802,"links":1804,"related":1807,"readMore":-1,"target":1809,"hasArticle":1385},"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.",[1803],"injection attack",[1805],{"kind":1408,"url":1806},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FPrompt_injection",[1808],"rate-limiting","\u002Fglossary#prompt-injection",{"slug":1521,"term":1811,"definition":1812,"category":1432,"aliases":1813,"links":1816,"related":1819,"readMore":-1,"target":1820,"hasArticle":1385},"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.",[1814,1815],"publish\u002Fsubscribe","Google Cloud Pub\u002FSub",[1817],{"kind":1408,"url":1818},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FPublish%E2%80%93subscribe_pattern",[],"\u002Fglossary#pub-sub",{"slug":1439,"term":1822,"definition":1823,"category":1432,"aliases":1824,"links":1827,"related":1830,"readMore":-1,"target":1831,"hasArticle":1385},"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.",[1825,1826],"REST API","Representational State Transfer",[1828],{"kind":1408,"url":1829},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FREST",[1520,1522],"\u002Fglossary#rest",{"slug":1808,"term":1833,"definition":1834,"category":1418,"aliases":1835,"links":1838,"related":1841,"readMore":-1,"target":1842,"hasArticle":1385},"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.",[1836,1837],"rate limit","throttling",[1839],{"kind":1408,"url":1840},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FRate_limiting",[1799],"\u002Fglossary#rate-limiting",{"slug":1565,"term":1844,"definition":1845,"category":1418,"aliases":1846,"links":1849,"related":1852,"readMore":-1,"target":1853,"hasArticle":1385},"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.",[1847,1848],"SOC2","System and Organization Controls",[1850],{"kind":1408,"url":1851},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FSystem_and_Organization_Controls",[1277,1553,1566],"\u002Fglossary#soc-2",{"slug":1855,"term":1856,"definition":1857,"category":1637,"aliases":1858,"links":1861,"related":1864,"readMore":-1,"target":1865,"hasArticle":1385},"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.",[1859,1860],"Software as a Service","software-as-a-service",[1862],{"kind":1408,"url":1863},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FSoftware_as_a_service",[1537,586],"\u002Fglossary#saas",{"slug":1522,"term":1867,"definition":1868,"category":1660,"aliases":1869,"links":1871,"related":1874,"readMore":-1,"target":1875,"hasArticle":1385},"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.",[1870],"SSE",[1872],{"kind":1408,"url":1873},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FServer-sent_events",[1520,1439],"\u002Fglossary#server-sent-events",{"slug":1613,"term":1877,"definition":1878,"category":1432,"aliases":1879,"links":1882,"related":1885,"readMore":-1,"target":1886,"hasArticle":1385},"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.",[1880,1881],"SSR","server-rendered",[1883],{"kind":1408,"url":1884},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FServer-side_scripting",[1603],"\u002Fglossary#server-side-rendering",{"slug":273,"term":1888,"definition":1889,"category":1376,"aliases":1890,"links":1893,"related":1898,"readMore":-1,"target":1899,"hasArticle":1385},"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.",[1891,1892],"Skia Graphics Engine","skia-safe",[1894,1896],{"kind":1381,"url":1895},"https:\u002F\u002Fskia.org\u002F",{"kind":1408,"url":1897},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FSkia_Graphics_Engine",[267],"\u002Fglossary#skia",{"slug":1901,"term":1902,"definition":1903,"category":1637,"aliases":1904,"links":1908,"related":1909,"readMore":-1,"target":1911,"hasArticle":1385},"staff-augmentation","Staff augmentation","A hiring model where engineers from an outside partner join your team and work under your management — in your repository, your sprints, your process — instead of delivering a project of their own. You buy capacity; the code and the context stay with you.",[1905,1906,1907],"team augmentation","dedicated developers","outstaffing",[],[1910,1796],"total-cost-of-ownership","\u002Fglossary#staff-augmentation",{"slug":1536,"term":1913,"definition":1914,"category":1418,"aliases":1915,"links":1918,"related":1919,"readMore":-1,"target":1920,"hasArticle":1385},"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.",[1916,1917],"phased release","canary release",[],[1525,1415],"\u002Fglossary#staged-rollout",{"slug":1922,"term":883,"definition":1923,"category":1432,"aliases":1924,"links":1928,"related":1931,"readMore":-1,"target":1932,"hasArticle":1385},"state-management","How an app decides where a value lives, who is allowed to change it, and which parts of the screen redraw when it does. In Flutter the choice between Riverpod, BLoC and Provider is among the first architectural decisions and the hardest to revisit.",[1925,1926,1927],"state management","BLoC","Riverpod",[1929],{"kind":1393,"url":1930},"https:\u002F\u002Fdocs.flutter.dev\u002Fdata-and-backend\u002Fstate-mgmt\u002Foptions",[1569],"\u002Fglossary#state-management",{"slug":1508,"term":1934,"definition":1935,"category":1660,"aliases":1936,"links":1940,"related":1943,"readMore":-1,"target":1944,"hasArticle":1385},"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.",[1937,1938,1939],"SSL","HTTPS","Transport Layer Security",[1941],{"kind":1408,"url":1942},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FTransport_Layer_Security",[1498,1509],"\u002Fglossary#tls",{"slug":1796,"term":1946,"definition":1947,"category":1637,"aliases":1948,"links":1950,"related":1953,"readMore":-1,"target":1954,"hasArticle":1385},"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.",[1949,1796],"TTM",[1951],{"kind":1408,"url":1952},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FTime_to_market",[689,1910],"\u002Fglossary#time-to-market",{"slug":1910,"term":1956,"definition":1957,"category":1637,"aliases":1958,"links":1961,"related":1964,"readMore":-1,"target":1965,"hasArticle":1385},"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.",[1959,1960],"TCO","cost of ownership",[1962],{"kind":1408,"url":1963},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FTotal_cost_of_ownership",[1796],"\u002Fglossary#total-cost-of-ownership",{"slug":1967,"term":891,"definition":1968,"category":1660,"aliases":1969,"links":1971,"related":1976,"readMore":-1,"target":1978,"hasArticle":1385},"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.",[1970],"Web Real-Time Communication",[1972,1974],{"kind":1381,"url":1973},"https:\u002F\u002Fwebrtc.org\u002F",{"kind":1408,"url":1975},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FWebRTC",[1977,1520],"xmpp","\u002Fglossary#webrtc",{"slug":1520,"term":1980,"definition":1981,"category":1660,"aliases":1982,"links":1983,"related":1986,"readMore":-1,"target":1987,"hasArticle":1385},"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.",[],[1984],{"kind":1408,"url":1985},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FWebSocket",[1522,1439],"\u002Fglossary#websocket",{"slug":586,"term":1989,"definition":1990,"category":1637,"aliases":1991,"links":1994,"related":1997,"readMore":1998,"target":1998,"hasArticle":863},"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.",[1992,1993],"white label","multi-tenant app",[1995],{"kind":1408,"url":1996},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FWhite-label_product",[689],"\u002Fglossary\u002Fwhite-label",{"slug":1977,"term":2000,"definition":2001,"category":1660,"aliases":2002,"links":2005,"related":2010,"readMore":-1,"target":2011,"hasArticle":1385},"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.",[2003,2004],"Jabber","Extensible Messaging and Presence Protocol",[2006,2008],{"kind":1381,"url":2007},"https:\u002F\u002Fxmpp.org\u002F",{"kind":1408,"url":2009},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FXMPP",[1967,1520],"\u002Fglossary#xmpp"]