[{"data":1,"prerenderedAt":251},["ShallowReactive",2],{"home-work":3},[4,106,183],{"id":5,"title":6,"body":7,"client":78,"description":72,"extension":79,"meta":80,"navigation":81,"order":82,"outcomes":83,"path":88,"sector":89,"seo":90,"services":91,"stack":95,"stem":101,"summary":102,"tone":103,"year":104,"__hash__":105},"work\u002Fwork\u002Ffleet-management-platform.md","Re-architecting a fleet management ecosystem in Flutter",{"type":8,"value":9,"toc":71},"minimark",[10,15,19,23,52,58,62,65],[11,12,14],"h2",{"id":13},"the-challenge","The challenge",[16,17,18],"p",{},"A growing fleet-management platform needed its mobile apps to keep pace with the product: drivers in the field, managers in the office, and a backend handling live vehicle data. Feature work was slowed by duplicated logic and platform-specific edge cases.",[11,20,22],{"id":21},"the-approach","The approach",[24,25,26,34,40,46],"ul",{},[27,28,29,33],"li",{},[30,31,32],"strong",{},"Audit first."," Mapped every screen, API call and native dependency to decide what moves to Flutter and what must stay native.",[27,35,36,39],{},[30,37,38],{},"Flutter core, native edges."," Shared business logic and UI in Flutter; background location, sensors and OS integrations in dedicated Kotlin and Swift modules behind platform channels.",[27,41,42,45],{},[30,43,44],{},"Modular architecture."," Feature modules with clear boundaries, so teams can work in parallel without stepping on each other.",[27,47,48,51],{},[30,49,50],{},"Incremental rollout."," Modules shipped behind flags while the existing app kept serving users.",[53,54,55],"blockquote",{},[16,56,57],{},"The goal was never \"rewrite in Flutter\". It was: ship features once, and make the native parts boring.",[11,59,61],{"id":60},"the-result","The result",[16,63,64],{},"The platform now runs on a single, well-structured Flutter codebase with a thin native layer — easier to extend, faster to release, and documented well enough for the wider team to own.",[16,66,67],{},[68,69,70],"em",{},"Replace this text with your own details and, where you can, real figures (release frequency, crash-free rate, time saved).",{"title":72,"searchDepth":73,"depth":73,"links":74},"",2,[75,76,77],{"id":13,"depth":73,"text":14},{"id":21,"depth":73,"text":22},{"id":60,"depth":73,"text":61},"Paris-based fleet SaaS (under NDA)","md",{},true,1,[84,85,86,87],"One shared Flutter codebase for Android and iOS","Native Kotlin & Swift modules for background location and device features","A modular architecture new developers can onboard into quickly","Release pipeline that ships both stores from a single branch","\u002Fwork\u002Ffleet-management-platform","Fleet & logistics",{"title":6,"description":72},[92,93,94],"Architecture","Mobile migration","Native modules",[96,97,98,99,100],"Flutter","Kotlin","Swift","Node.js","Firebase","work\u002Ffleet-management-platform","One Flutter codebase for drivers and managers, with native Kotlin & Swift modules where the hardware demands it.","amber","2024 — now","o_1NWlmBurAhrNSxg2kwKfjrgRBR5cYCRPcCvNDaRq8",{"id":107,"title":108,"body":109,"client":159,"description":72,"extension":79,"meta":160,"navigation":81,"order":73,"outcomes":161,"path":166,"sector":167,"seo":168,"services":169,"stack":173,"stem":178,"summary":179,"tone":180,"year":181,"__hash__":182},"work\u002Fwork\u002Fgps-telemetry-pipeline.md","A real-time GPS telemetry pipeline for connected vehicles",{"type":8,"value":110,"toc":154},[111,113,116,118,144,146,149],[11,112,14],{"id":13},[16,114,115],{},"GPS trackers speak low-level binary protocols over TCP. The project needed its own ingestion layer — reliable, observable and fast enough to power live maps — instead of depending on a third-party gateway.",[11,117,22],{"id":21},[24,119,120,126,132,138],{},[27,121,122,125],{},[30,123,124],{},"Protocol-first."," Implemented Teltonika codec parsing, acknowledgements and connection handling on a Node.js TCP server.",[27,127,128,131],{},[30,129,130],{},"Redis as the live layer."," Latest positions and event streams written to Redis so apps and dashboards read without hitting the decoder.",[27,133,134,137],{},[30,135,136],{},"Design reviews with the team."," Key choices — data model, retention, export format — agreed with the people who run it.",[27,139,140,143],{},[30,141,142],{},"Ops from day one."," Docker images, logging and health checks so the pipeline can be run by someone other than its author.",[11,145,61],{"id":60},[16,147,148],{},"A lean, self-owned telemetry backbone that feeds live tracking and reporting, and gives the product full control over its vehicle data.",[16,150,151],{},[68,152,153],{},"Replace this text with your own details and real metrics (devices connected, messages per second, latency).",{"title":72,"searchDepth":73,"depth":73,"links":155},[156,157,158],{"id":13,"depth":73,"text":14},{"id":21,"depth":73,"text":22},{"id":60,"depth":73,"text":61},"Fleet telematics project (under NDA)",{},[162,163,164,165],"Direct TCP ingestion of Teltonika device protocols","Decoded positions and events available in near real time via Redis","Export tooling for reporting and downstream systems","Containerised deployment that is simple to operate","\u002Fwork\u002Fgps-telemetry-pipeline","IoT & telematics",{"title":108,"description":72},[170,171,172],"Backend architecture","IoT ingestion","Data export",[99,174,175,176,177],"TCP","Teltonika","Redis","Docker","work\u002Fgps-telemetry-pipeline","A Node.js TCP server that ingests Teltonika tracker data, decodes it and streams positions into Redis for live maps and reports.","ink","2025","ra_TfOYpsvE0wLbeiYFgec-d85RVX3SwNgEnk0elU6A",{"id":184,"title":185,"body":186,"client":230,"description":72,"extension":79,"meta":231,"navigation":81,"order":232,"outcomes":233,"path":237,"sector":238,"seo":239,"services":240,"stack":244,"stem":246,"summary":247,"tone":248,"year":249,"__hash__":250},"work\u002Fwork\u002Fhealthcare-marketplace.md","Building a healthcare marketplace app",{"type":8,"value":187,"toc":225},[188,190,193,195,215,217,220],[11,189,14],{"id":13},[16,191,192],{},"Docnet needed a mobile product that makes finding and booking healthcare providers simple — on both Android and iOS, without the cost of two native teams.",[11,194,22],{"id":21},[24,196,197,203,209],{},[27,198,199,202],{},[30,200,201],{},"Product-minded scoping."," Focused the first release on the flows that matter: search, provider profile, booking.",[27,204,205,208],{},[30,206,207],{},"Flutter for speed."," One codebase, consistent UI, fast iteration with the client.",[27,210,211,214],{},[30,212,213],{},"API-first."," A clear contract between app and backend so features can be added without rework.",[11,216,61],{"id":60},[16,218,219],{},"A cross-platform marketplace app delivered as a freelance engagement, built to grow with the business.",[16,221,222],{},[68,223,224],{},"Confirm with the client before publishing their name, and add real figures where you can.",{"title":72,"searchDepth":73,"depth":73,"links":226},[227,228,229],{"id":13,"depth":73,"text":14},{"id":21,"depth":73,"text":22},{"id":60,"depth":73,"text":61},"Docnet",{},3,[234,235,236],"Cross-platform patient app from a single Flutter codebase","Provider discovery, profiles and booking flows","Clean API integration ready for future features","\u002Fwork\u002Fhealthcare-marketplace","Healthcare",{"title":185,"description":72},[241,242,243],"Consulting","Mobile development","Backend integration",[96,245,100],"REST APIs","work\u002Fhealthcare-marketplace","A mobile marketplace connecting patients with healthcare providers — booking, profiles and messaging in one Flutter app.","paper","2024","iI5rRZavaUdQIiEgFUZCBxW1NDO2v3jAmyy5bW_ckS0",1793685242419]