[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"technologies":3,"\u002Fportfolio\u002Fjepta":167,"glossary":331},[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,"body":170,"categories":310,"client":312,"date":313,"description":314,"duration":315,"extension":316,"image":317,"links":319,"meta":320,"metaDescription":321,"navigation":322,"ogDescription":323,"path":324,"seo":325,"slug":326,"stem":327,"technologies":328,"updated":329,"__hash__":330},"projects_en\u002Fportfolio\u002Fjepta.md","Jepta",{"type":171,"value":172,"toc":293},"minimark",[173,178,182,185,189,193,196,201,204,208,216,220,223,227,230,234,241,245,248,252,255,258,271,275,279],[174,175,177],"h2",{"id":176},"project-overview","Project Overview",[179,180,181],"p",{},"Jepta is a hyperlocal social network built around the place you live. Instead of a global follower graph, it organizes people by proximity: chats attached to a street address or a building, group chats for the people who share it, and channels run by the bakery, the workshop or the club a few hundred meters away. Everything in the app — the chats you are offered, the channels in the feed, the posts you see first — is ranked by distance from where you are.",[179,183,184],{},"Netgineers GmbH came to us with the product defined and the backend under way, and needed the mobile side of it built: one Flutter codebase covering iOS and Android, for a product whose surface is unusually wide for a first release.",[186,187],"gallery",{":images":188},"[{\"url\": \"\u002Fprojects\u002Fjepta\u002Fimages\u002F01.webp\", \"alt\": \"Onboarding\"}, {\"url\": \"\u002Fprojects\u002Fjepta\u002Fimages\u002F02.webp\", \"alt\": \"Location Permission\"}, {\"url\": \"\u002Fprojects\u002Fjepta\u002Fimages\u002F03.webp\", \"alt\": \"Chats List\"}, {\"url\": \"\u002Fprojects\u002Fjepta\u002Fimages\u002F04.webp\", \"alt\": \"Channel Feed\"}, {\"url\": \"\u002Fprojects\u002Fjepta\u002Fimages\u002F05.webp\", \"alt\": \"Channel Info\"}, {\"url\": \"\u002Fprojects\u002Fjepta\u002Fimages\u002F06.webp\", \"alt\": \"Channel Chat\"}, {\"url\": \"\u002Fprojects\u002Fjepta\u002Fimages\u002F07.webp\", \"alt\": \"New Post\"}]",[174,190,192],{"id":191},"the-challenge","The Challenge",[179,194,195],{},"Two things made this more than a standard build.",[197,198,200],"h3",{"id":199},"scale-of-the-screen-surface","Scale of the screen surface",[179,202,203],{},"Jepta is not one feature with settings around it. Direct chats, group chats, address chats, a channel feed, channel profiles with opening hours and photo galleries, channel-to-user conversations, a post composer with per-post comment controls, an activity tab, a profile tab, search, adding contacts by QR code, location and permission flows — all of it in the first release, in a six-month window. At that count, screens stop being independent units of work: without a shared skeleton, every new one drags its own navigation quirks, its own loading and empty states, and its own copy of the same list.",[197,205,207],{"id":206},"real-time-everywhere","Real-time everywhere",[179,209,210,211,215],{},"Chat is the obvious place ",[212,213],"term",{"slug":214},"websocket"," connections show up, but in Jepta they are not confined to it. A channel post arriving, a comment count moving, an unread badge on the chats tab, a message marked as read — the same live connection drives all of them, across screens the user is not currently looking at. Handling that per screen would have meant a connection per screen and state that disagrees with itself the moment a user switches tabs.",[174,217,219],{"id":218},"our-approach","Our Approach",[179,221,222],{},"We treated both problems as one: build the shared parts first, then let screens be thin.",[197,224,226],{"id":225},"one-real-time-layer-many-consumers","One real-time layer, many consumers",[179,228,229],{},"The WebSocket connection lives below the UI as a single client owning its own lifecycle — connect, authenticate, heartbeat, reconnect with backoff, resubscribe. Screens do not open sockets; they subscribe to typed event streams and are handed updates. Messages sent while the connection is down are queued and flushed on reconnect rather than lost, and delivery state (sent, delivered, read) is tracked as part of the message model instead of being inferred from what happened to arrive. Because the layer is shared, a message landing in a chat the user has open and an unread badge incrementing on a tab they are not looking at are the same event handled once.",[197,231,233],{"id":232},"a-screen-skeleton-instead-of-screen-by-screen-craft","A screen skeleton instead of screen-by-screen craft",[179,235,236,237,240],{},"With that many surfaces, the win came from making them uniform: one navigation graph with typed routes, one ",[212,238],{"slug":239},"state-management"," pattern applied the same way in every feature, and a shared set of list, loading, empty and error states. New screens were mostly composition — which is what made the volume tractable inside the timeline, and what kept the app coherent rather than looking like twenty screens built by different hands.",[197,242,244],{"id":243},"location-as-a-first-class-input","Location as a first-class input",[179,246,247],{},"Proximity is not a filter bolted onto the feed, it is the product's organising principle, so the location layer had to be dependable: permission flows that degrade gracefully when a user says no, cached coordinates so the feed is never blank while a fix is acquired, and distance rendered close to where content appears (\"5 km away\" on a channel header) so the ranking is legible rather than mysterious.",[174,249,251],{"id":250},"results","Results",[179,253,254],{},"Jepta shipped to iOS and Android from a single Flutter codebase inside the six-month window, with the full feature set intact — chats, channels, posts, comments and the location-aware feed in the first release rather than staged across several.",[179,256,257],{},"The architecture is the part that outlived the deadline. Because the real-time layer, the navigation graph and the state pattern were built once and reused, adding a screen after launch stayed a small change instead of a new integration with the socket, the router and the cache. For a product whose roadmap is \"more surfaces\", that is the difference that compounds.",[259,260,265,268],"testimonial",{"author":261,"avatar":262,"linkedin":263,"role":264},"Evgeny Syrtsov","\u002Fclients\u002Fevgeny-syrtsov.png","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fevgeny-syrtsov\u002F","CEO, Netgineers GmbH",[179,266,267],{},"Six months for an app this wide was the part that worried me. Jepta is neighborhood chats, business channels, posts, comments and a feed that reorders itself around wherever you happen to be standing — a long list of screens, a fixed date, and the realistic expectation that half of it would slip into a second release.",[179,269,270],{},"Nerdy Production built the shared foundations first — one real-time layer, one navigation model — and after that every new screen was cheap. We launched on iOS and Android with the full feature set, chat has been dependable from day one, and extending the app since then has been a small job rather than a project. We got the product we specified, on the date we specified.",[174,272,274],{"id":273},"faq","FAQ",[276,277],"questions",{":items":278},"[{\"title\": \"What is Jepta?\", \"text\": \"Jepta is a hyperlocal communication app for German neighborhoods. It organizes people by proximity rather than by a global follower graph: chats tied to a street address or a building, group chats for the people who share one, and channels run by local businesses such as a bakery or a workshop. The chats, channels and posts a user is shown are ranked by distance from where they are.\"}, {\"title\": \"How do you build a Flutter app with a large number of screens?\", \"text\": \"Build the shared parts first and keep the screens thin. On Jepta that meant one navigation graph with typed routes, one state management pattern applied the same way in every feature, and a shared set of list, loading, empty and error states. New screens then become mostly composition rather than new integrations, which is what keeps the volume tractable on a deadline and stops the app looking like twenty screens built by different hands.\"}, {\"title\": \"How do you handle WebSocket connections across many screens in Flutter?\", \"text\": \"Put one connection below the UI as a single client that owns its own lifecycle: connect, authenticate, heartbeat, reconnect with backoff, resubscribe. Screens do not open sockets of their own; they subscribe to typed event streams and are handed updates. A message arriving in an open chat and an unread badge incrementing on a tab nobody is looking at are then the same event handled once, instead of one connection per screen and state that disagrees with itself.\"}, {\"title\": \"What happens to chat messages sent while the connection is down?\", \"text\": \"They are queued and flushed on reconnect rather than lost. Delivery state — sent, delivered, read — is tracked as part of the message model instead of being inferred from whatever happened to arrive, so the interface shows the real status of a message rather than a guess about it.\"}, {\"title\": \"How long does it take to build a large Flutter social app?\", \"text\": \"Jepta shipped to iOS and Android from a single Flutter codebase in six months, with chats, channels, posts, comments and the location-aware feed all in the first release rather than staged across several. The timeline held because the real-time layer, the navigation graph and the state pattern were built once and reused across every screen.\"}, {\"title\": \"Can a Flutter app rank content by location?\", \"text\": \"Yes, and on Jepta proximity is the organizing principle rather than a filter applied on top of the feed. That puts real requirements on the location layer: permission flows that degrade gracefully when a user declines, cached coordinates so the feed is never blank while a fix is acquired, and the distance shown next to the content it applies to so the ranking is legible rather than mysterious.\"}]",[179,280,281,282,287,288,292],{},"Jepta was built as part of our ",[283,284,286],"a",{"href":285},"\u002Fservices\u002Fflutter-app-development","Flutter app development"," service, and it is the anchor build behind our ",[283,289,291],{"href":290},"\u002Fservices\u002Fflutter-app-development\u002Fsocial","social & community app development"," practice — the same real-time layer, told from the community angle.",{"title":294,"searchDepth":295,"depth":295,"links":296},"",2,[297,298,303,308,309],{"id":176,"depth":295,"text":177},{"id":191,"depth":295,"text":192,"children":299},[300,302],{"id":199,"depth":301,"text":200},3,{"id":206,"depth":301,"text":207},{"id":218,"depth":295,"text":219,"children":304},[305,306,307],{"id":225,"depth":301,"text":226},{"id":232,"depth":301,"text":233},{"id":243,"depth":301,"text":244},{"id":250,"depth":295,"text":251},{"id":273,"depth":295,"text":274},[311],"mobile","Netgineers GmbH","2023-06-01","Jepta is a hyperlocal communication app for German neighborhoods. Neighbors talk in chats tied to their street or building, local businesses run channels with posts, opening hours and comments, and everything a user sees is ranked by how close it actually is. We built the Flutter app for iOS and Android — a large screen surface with a WebSocket layer behind every chat and channel.","6 Months","md",{"alt":169,"url":318},"\u002Fprojects\u002Fjepta\u002Fhero.webp",null,{},"Jepta — a hyperlocal Flutter app for German neighborhoods: address-based chats, local business channels and a location-aware feed on iOS and Android.",true,"Neighborhood chat that knows where you are — a Flutter app on iOS and Android, WebSocket-backed messaging, and channels for the shops on your street.","\u002Fportfolio\u002Fjepta",{"title":169,"description":314},"jepta","portfolio\u002Fjepta",[41,18],"2026-09-05","yqXTSOsutWTaOavR9VLMcbITvyklhNYNpTgVRZLw2cw",[332,347,360,375,389,403,419,431,445,458,472,484,500,513,530,543,554,564,577,589,600,615,624,637,650,657,668,680,691,706,718,731,743,755,767,779,790,801,812,823,835,845,856,869,881,890,902,914,924,935,949,958,969],{"slug":333,"term":334,"definition":335,"category":336,"aliases":337,"links":339,"related":343,"readMore":-1,"target":345,"hasArticle":346},"aosp","AOSP","The Android Open Source Project — Android without the Google layer on top, which anyone may fork. Point-of-sale terminals, kiosks and in-car systems run on forks of it, and working at that level exposes parts of the OS an app developer never sees.","platform",[338],"Android Open Source Project",[340],{"kind":341,"url":342},"website","https:\u002F\u002Fsource.android.com\u002F",[344],"host-card-emulation","\u002Fglossary#aosp",false,{"slug":348,"term":349,"definition":350,"category":336,"aliases":351,"links":352,"related":356,"readMore":-1,"target":359,"hasArticle":346},"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.",[],[353],{"kind":354,"url":355},"documentation","https:\u002F\u002Fdeveloper.apple.com\u002Fapp-clips\u002F",[357,358],"deep-linking","install-referrer","\u002Fglossary#app-clips",{"slug":361,"term":362,"definition":363,"category":336,"aliases":364,"links":365,"related":371,"readMore":-1,"target":374,"hasArticle":346},"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.",[],[366,368],{"kind":341,"url":367},"https:\u002F\u002Fcloud.google.com\u002Fbigquery",{"kind":369,"url":370},"wikipedia","https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FBigQuery",[372,373],"object-storage","elasticsearch","\u002Fglossary#bigquery",{"slug":376,"term":377,"definition":378,"category":379,"aliases":380,"links":384,"related":387,"readMore":-1,"target":388,"hasArticle":346},"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",[381,382,383],"CI","continuous integration","continuous delivery",[385],{"kind":369,"url":386},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FCI\u002FCD",[],"\u002Fglossary#ci-cd",{"slug":390,"term":391,"definition":392,"category":393,"aliases":394,"links":396,"related":399,"readMore":-1,"target":402,"hasArticle":346},"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",[395],"Create, Read, Update, Delete",[397],{"kind":369,"url":398},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FCreate,_read,_update_and_delete",[400,401],"rest","graphql","\u002Fglossary#crud",{"slug":404,"term":405,"definition":406,"category":393,"aliases":407,"links":412,"related":415,"readMore":-1,"target":418,"hasArticle":346},"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.",[408,409,410,411],"image registry","Docker registry","GHCR","ghcr.io",[413],{"kind":354,"url":414},"https:\u002F\u002Fdocs.github.com\u002Fen\u002Fpackages\u002Fworking-with-a-github-packages-registry\u002Fworking-with-the-container-registry",[416,417],"dev-container","multi-arch-image","\u002Fglossary#container-registry",{"slug":357,"term":420,"definition":421,"category":336,"aliases":422,"links":426,"related":429,"readMore":430,"target":430,"hasArticle":322},"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.",[423,424,425],"deferred deep linking","universal links","Android App Links",[427],{"kind":369,"url":428},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FMobile_deep_linking",[348,358],"\u002Fglossary\u002Fdeep-linking",{"slug":416,"term":432,"definition":433,"category":379,"aliases":434,"links":438,"related":443,"readMore":-1,"target":444,"hasArticle":346},"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.",[435,436,437],"devcontainer.json","Dev Containers","VS Code Dev Containers",[439,441],{"kind":341,"url":440},"https:\u002F\u002Fcontainers.dev\u002F",{"kind":354,"url":442},"https:\u002F\u002Fcode.visualstudio.com\u002Fdocs\u002Fdevcontainers\u002Fcontainers",[404],"\u002Fglossary#dev-container",{"slug":373,"term":446,"definition":447,"category":336,"aliases":448,"links":451,"related":456,"readMore":-1,"target":457,"hasArticle":346},"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\".",[449,450],"Elastic","ELK",[452,454],{"kind":341,"url":453},"https:\u002F\u002Fwww.elastic.co\u002Felasticsearch",{"kind":369,"url":455},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FElasticsearch",[361],"\u002Fglossary#elasticsearch",{"slug":459,"term":460,"definition":461,"category":393,"aliases":462,"links":465,"related":468,"readMore":-1,"target":471,"hasArticle":346},"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.",[463,464],"E2EE","end-to-end encrypted",[466],{"kind":369,"url":467},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FEnd-to-end_encryption",[469,470],"tls","jwt","\u002Fglossary#end-to-end-encryption",{"slug":473,"term":474,"definition":475,"category":393,"aliases":476,"links":479,"related":480,"readMore":-1,"target":483,"hasArticle":346},"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.",[477,478],"fanout","broadcast",[],[214,481,482],"pub-sub","server-sent-events","\u002Fglossary#fan-out",{"slug":485,"term":486,"definition":487,"category":379,"aliases":488,"links":492,"related":495,"readMore":-1,"target":499,"hasArticle":346},"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.",[489,490,491],"feature flag","feature toggle","feature gating",[493],{"kind":369,"url":494},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FFeature_toggle",[496,497,498],"staged-rollout","white-label","multi-tenancy","\u002Fglossary#feature-flags",{"slug":501,"term":502,"definition":503,"category":393,"aliases":504,"links":508,"related":511,"readMore":-1,"target":512,"hasArticle":346},"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.",[505,506,507],"IEEE 754","double","floating-point arithmetic",[509],{"kind":369,"url":510},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FIEEE_754",[],"\u002Fglossary#floating-point",{"slug":514,"term":515,"definition":516,"category":379,"aliases":517,"links":520,"related":525,"readMore":-1,"target":529,"hasArticle":346},"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.",[518,519],"General Data Protection Regulation","data protection",[521,523],{"kind":341,"url":522},"https:\u002F\u002Fgdpr.eu\u002F",{"kind":369,"url":524},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FGeneral_Data_Protection_Regulation",[526,527,528],"pci-dss","soc-2","hipaa","\u002Fglossary#gdpr",{"slug":531,"term":532,"definition":533,"category":379,"aliases":534,"links":538,"related":541,"readMore":-1,"target":542,"hasArticle":346},"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.",[535,536,537],"golden tests","screenshot test","snapshot test",[539],{"kind":354,"url":540},"https:\u002F\u002Fapi.flutter.dev\u002Fflutter\u002Fflutter_test\u002FmatchesGoldenFile.html",[376],"\u002Fglossary#golden-test",{"slug":401,"term":544,"definition":545,"category":393,"aliases":546,"links":547,"related":552,"readMore":-1,"target":553,"hasArticle":346},"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.",[],[548,550],{"kind":341,"url":549},"https:\u002F\u002Fgraphql.org\u002F",{"kind":369,"url":551},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FGraphQL",[400],"\u002Fglossary#graphql",{"slug":528,"term":555,"definition":556,"category":379,"aliases":557,"links":559,"related":562,"readMore":-1,"target":563,"hasArticle":346},"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.",[558],"Health Insurance Portability and Accountability Act",[560],{"kind":369,"url":561},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FHealth_Insurance_Portability_and_Accountability_Act",[526,514,527],"\u002Fglossary#hipaa",{"slug":565,"term":566,"definition":567,"category":393,"aliases":568,"links":571,"related":574,"readMore":-1,"target":576,"hasArticle":346},"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.",[569,570],"headless content management system","content API",[572],{"kind":369,"url":573},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FHeadless_content_management_system",[575,400],"server-side-rendering","\u002Fglossary#headless-cms",{"slug":344,"term":578,"definition":579,"category":336,"aliases":580,"links":584,"related":587,"readMore":-1,"target":588,"hasArticle":346},"Host Card Emulation","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.",[581,582,583],"HCE","EMV Contactless","contactless payments",[585],{"kind":354,"url":586},"https:\u002F\u002Fdeveloper.android.com\u002Fdevelop\u002Fconnectivity\u002Fnfc\u002Fhce",[526,333],"\u002Fglossary#host-card-emulation",{"slug":590,"term":591,"definition":592,"category":336,"aliases":593,"links":594,"related":597,"readMore":-1,"target":599,"hasArticle":346},"impeller","Impeller","The rendering engine Flutter uses today, default on iOS since 2023 and on Android since 2024. It compiles its shaders ahead of time instead of during the first animation, which removed the shader-compilation jank that was Flutter's most visible production problem.",[],[595],{"kind":354,"url":596},"https:\u002F\u002Fdocs.flutter.dev\u002Fperf\u002Fimpeller",[598],"skia","\u002Fglossary#impeller",{"slug":601,"term":602,"definition":603,"category":604,"aliases":605,"links":609,"related":612,"readMore":-1,"target":614,"hasArticle":346},"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",[606,607,608],"IAP","in-app purchases","in-app subscription",[610],{"kind":354,"url":611},"https:\u002F\u002Fdeveloper.apple.com\u002Fin-app-purchase\u002F",[613],"product-market-fit","\u002Fglossary#in-app-purchase",{"slug":358,"term":616,"definition":617,"category":336,"aliases":618,"links":619,"related":622,"readMore":-1,"target":623,"hasArticle":346},"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.",[],[620],{"kind":354,"url":621},"https:\u002F\u002Fdeveloper.android.com\u002Fgoogle\u002Fplay\u002Finstallreferrer",[357,348],"\u002Fglossary#install-referrer",{"slug":470,"term":625,"definition":626,"category":627,"aliases":628,"links":630,"related":635,"readMore":-1,"target":636,"hasArticle":346},"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",[629],"JSON Web Token",[631,633],{"kind":341,"url":632},"https:\u002F\u002Fjwt.io\u002F",{"kind":369,"url":634},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FJSON_Web_Token",[526],"\u002Fglossary#jwt",{"slug":638,"term":639,"definition":640,"category":379,"aliases":641,"links":645,"related":648,"readMore":-1,"target":649,"hasArticle":346},"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.",[642,643,644],"Know Your Customer","AML","KYC\u002FAML",[646],{"kind":369,"url":647},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FKnow_your_customer",[526,514],"\u002Fglossary#kyc",{"slug":76,"term":74,"definition":651,"category":336,"aliases":652,"links":654,"related":655,"readMore":656,"target":656,"hasArticle":346},"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.",[653],"KMP",[],[],"\u002Ftechnologies\u002Fkmp",{"slug":658,"term":659,"definition":660,"category":604,"aliases":661,"links":663,"related":666,"readMore":-1,"target":667,"hasArticle":346},"mvp","MVP","The smallest version of a product that can go in front of real users and still answer the question you built it to answer. A decision about scope, not about quality — an MVP still has to work.",[662],"minimum viable product",[664],{"kind":369,"url":665},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FMinimum_viable_product",[497],"\u002Fglossary#mvp",{"slug":417,"term":669,"definition":670,"category":393,"aliases":671,"links":675,"related":678,"readMore":-1,"target":679,"hasArticle":346},"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.",[672,673,674],"multi-arch build","multi-platform image","linux\u002Famd64 + linux\u002Farm64",[676],{"kind":354,"url":677},"https:\u002F\u002Fdocs.docker.com\u002Fbuild\u002Fbuilding\u002Fmulti-platform\u002F",[404],"\u002Fglossary#multi-arch-image",{"slug":498,"term":681,"definition":682,"category":393,"aliases":683,"links":686,"related":689,"readMore":-1,"target":690,"hasArticle":346},"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.",[684,685],"multi-tenant","tenant",[687],{"kind":369,"url":688},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FMultitenancy",[497,485],"\u002Fglossary#multi-tenancy",{"slug":692,"term":693,"definition":694,"category":627,"aliases":695,"links":699,"related":704,"readMore":-1,"target":705,"hasArticle":346},"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.",[696,697,698],"OAuth 2.0","social login","Sign in with Apple",[700,702],{"kind":341,"url":701},"https:\u002F\u002Foauth.net\u002F2\u002F",{"kind":369,"url":703},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FOAuth",[470],"\u002Fglossary#oauth",{"slug":372,"term":707,"definition":708,"category":393,"aliases":709,"links":713,"related":716,"readMore":-1,"target":717,"hasArticle":346},"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.",[710,711,712],"S3","S3-compatible storage","blob storage",[714],{"kind":369,"url":715},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FObject_storage",[361],"\u002Fglossary#object-storage",{"slug":526,"term":719,"definition":720,"category":379,"aliases":721,"links":724,"related":729,"readMore":-1,"target":730,"hasArticle":346},"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.",[722,723],"PCI DSS","Payment Card Industry Data Security Standard",[725,727],{"kind":341,"url":726},"https:\u002F\u002Fwww.pcisecuritystandards.org\u002F",{"kind":369,"url":728},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FPayment_Card_Industry_Data_Security_Standard",[470],"\u002Fglossary#pci-dss",{"slug":732,"term":733,"definition":734,"category":336,"aliases":735,"links":738,"related":741,"readMore":-1,"target":742,"hasArticle":346},"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.",[736,737],"platform channel","method channel",[739],{"kind":354,"url":740},"https:\u002F\u002Fdocs.flutter.dev\u002Fplatform-integration\u002Fplatform-channels",[76],"\u002Fglossary#platform-channels",{"slug":744,"term":745,"definition":746,"category":627,"aliases":747,"links":750,"related":753,"readMore":-1,"target":754,"hasArticle":346},"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.",[748,749],"PQC","post-quantum crypto",[751],{"kind":369,"url":752},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FPost-quantum_cryptography",[469,459],"\u002Fglossary#post-quantum-cryptography",{"slug":613,"term":756,"definition":757,"category":604,"aliases":758,"links":761,"related":764,"readMore":-1,"target":766,"hasArticle":346},"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.",[759,760],"PMF","product\u002Fmarket fit",[762],{"kind":369,"url":763},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FProduct-market_fit",[658,765],"time-to-market","\u002Fglossary#product-market-fit",{"slug":768,"term":769,"definition":770,"category":379,"aliases":771,"links":773,"related":776,"readMore":-1,"target":778,"hasArticle":346},"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.",[772],"injection attack",[774],{"kind":369,"url":775},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FPrompt_injection",[777],"rate-limiting","\u002Fglossary#prompt-injection",{"slug":481,"term":780,"definition":781,"category":393,"aliases":782,"links":785,"related":788,"readMore":-1,"target":789,"hasArticle":346},"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.",[783,784],"publish\u002Fsubscribe","Google Cloud Pub\u002FSub",[786],{"kind":369,"url":787},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FPublish%E2%80%93subscribe_pattern",[],"\u002Fglossary#pub-sub",{"slug":400,"term":791,"definition":792,"category":393,"aliases":793,"links":796,"related":799,"readMore":-1,"target":800,"hasArticle":346},"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.",[794,795],"REST API","Representational State Transfer",[797],{"kind":369,"url":798},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FREST",[214,482],"\u002Fglossary#rest",{"slug":777,"term":802,"definition":803,"category":379,"aliases":804,"links":807,"related":810,"readMore":-1,"target":811,"hasArticle":346},"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.",[805,806],"rate limit","throttling",[808],{"kind":369,"url":809},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FRate_limiting",[768],"\u002Fglossary#rate-limiting",{"slug":527,"term":813,"definition":814,"category":379,"aliases":815,"links":818,"related":821,"readMore":-1,"target":822,"hasArticle":346},"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.",[816,817],"SOC2","System and Organization Controls",[819],{"kind":369,"url":820},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FSystem_and_Organization_Controls",[526,514,528],"\u002Fglossary#soc-2",{"slug":824,"term":825,"definition":826,"category":604,"aliases":827,"links":830,"related":833,"readMore":-1,"target":834,"hasArticle":346},"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.",[828,829],"Software as a Service","software-as-a-service",[831],{"kind":369,"url":832},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FSoftware_as_a_service",[498,497],"\u002Fglossary#saas",{"slug":482,"term":836,"definition":837,"category":627,"aliases":838,"links":840,"related":843,"readMore":-1,"target":844,"hasArticle":346},"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.",[839],"SSE",[841],{"kind":369,"url":842},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FServer-sent_events",[214,400],"\u002Fglossary#server-sent-events",{"slug":575,"term":846,"definition":847,"category":393,"aliases":848,"links":851,"related":854,"readMore":-1,"target":855,"hasArticle":346},"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.",[849,850],"SSR","server-rendered",[852],{"kind":369,"url":853},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FServer-side_scripting",[565],"\u002Fglossary#server-side-rendering",{"slug":598,"term":857,"definition":858,"category":336,"aliases":859,"links":862,"related":867,"readMore":-1,"target":868,"hasArticle":346},"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.",[860,861],"Skia Graphics Engine","skia-safe",[863,865],{"kind":341,"url":864},"https:\u002F\u002Fskia.org\u002F",{"kind":369,"url":866},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FSkia_Graphics_Engine",[590],"\u002Fglossary#skia",{"slug":870,"term":871,"definition":872,"category":604,"aliases":873,"links":877,"related":878,"readMore":-1,"target":880,"hasArticle":346},"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.",[874,875,876],"team augmentation","dedicated developers","outstaffing",[],[879,765],"total-cost-of-ownership","\u002Fglossary#staff-augmentation",{"slug":496,"term":882,"definition":883,"category":379,"aliases":884,"links":887,"related":888,"readMore":-1,"target":889,"hasArticle":346},"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.",[885,886],"phased release","canary release",[],[485,376],"\u002Fglossary#staged-rollout",{"slug":239,"term":891,"definition":892,"category":393,"aliases":893,"links":897,"related":900,"readMore":-1,"target":901,"hasArticle":346},"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.",[894,895,896],"state management","BLoC","Riverpod",[898],{"kind":354,"url":899},"https:\u002F\u002Fdocs.flutter.dev\u002Fdata-and-backend\u002Fstate-mgmt\u002Foptions",[531],"\u002Fglossary#state-management",{"slug":469,"term":903,"definition":904,"category":627,"aliases":905,"links":909,"related":912,"readMore":-1,"target":913,"hasArticle":346},"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.",[906,907,908],"SSL","HTTPS","Transport Layer Security",[910],{"kind":369,"url":911},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FTransport_Layer_Security",[459,470],"\u002Fglossary#tls",{"slug":765,"term":915,"definition":916,"category":604,"aliases":917,"links":919,"related":922,"readMore":-1,"target":923,"hasArticle":346},"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.",[918,765],"TTM",[920],{"kind":369,"url":921},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FTime_to_market",[658,879],"\u002Fglossary#time-to-market",{"slug":879,"term":925,"definition":926,"category":604,"aliases":927,"links":930,"related":933,"readMore":-1,"target":934,"hasArticle":346},"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.",[928,929],"TCO","cost of ownership",[931],{"kind":369,"url":932},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FTotal_cost_of_ownership",[765],"\u002Fglossary#total-cost-of-ownership",{"slug":936,"term":937,"definition":938,"category":627,"aliases":939,"links":941,"related":946,"readMore":-1,"target":948,"hasArticle":346},"webrtc","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.",[940],"Web Real-Time Communication",[942,944],{"kind":341,"url":943},"https:\u002F\u002Fwebrtc.org\u002F",{"kind":369,"url":945},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FWebRTC",[947,214],"xmpp","\u002Fglossary#webrtc",{"slug":214,"term":950,"definition":951,"category":627,"aliases":952,"links":953,"related":956,"readMore":-1,"target":957,"hasArticle":346},"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.",[],[954],{"kind":369,"url":955},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FWebSocket",[482,400],"\u002Fglossary#websocket",{"slug":497,"term":959,"definition":960,"category":604,"aliases":961,"links":964,"related":967,"readMore":968,"target":968,"hasArticle":322},"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.",[962,963],"white label","multi-tenant app",[965],{"kind":369,"url":966},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FWhite-label_product",[658],"\u002Fglossary\u002Fwhite-label",{"slug":947,"term":970,"definition":971,"category":627,"aliases":972,"links":975,"related":980,"readMore":-1,"target":981,"hasArticle":346},"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.",[973,974],"Jabber","Extensible Messaging and Presence Protocol",[976,978],{"kind":341,"url":977},"https:\u002F\u002Fxmpp.org\u002F",{"kind":369,"url":979},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FXMPP",[936,214],"\u002Fglossary#xmpp"]