[{"data":1,"prerenderedAt":245},["ShallowReactive",2],{"footer-learn-links":3,"site-prefooter-cta":16,"blog-\u002Fblog\u002Fjune-2026-newsletter\u002F":24,"related-blog-\u002Fblog\u002Fjune-2026-newsletter\u002F":204,"blog-author-\u002Fblog\u002Fjune-2026-newsletter\u002F":27},[4,7,10,13],{"title":5,"path":6},"What Is the Best Routing API?","\u002Flearn\u002Fbest-routing-api",{"title":8,"path":9},"What Is a GDPR-Compliant Mapping API?","\u002Flearn\u002Fgdpr-compliant-mapping-api",{"title":11,"path":12},"What Is Satellite Imagery Resolution?","\u002Flearn\u002Fsatellite-imagery-resolution",{"title":14,"path":15},"What Is Address Autocomplete?","\u002Flearn\u002Faddress-autocomplete",{"id":17,"extension":18,"heading":19,"meta":20,"stem":21,"text":22,"__hash__":23},"site\u002Fsite\u002Fprefooter-cta.yml","yml","Business Outcomes That Fuel Your Growth",{},"site\u002Fprefooter-cta","With Stadia Maps, you build the solutions that matter. Logistics platforms provide accurate ETAs, fleet management apps reduce fuel costs, and emergency dispatch systems improve response times.","XztWiZDFyAC0XCoeYLLQrcyaVmP8uvGWALRS354c9I4",{"id":25,"title":26,"abstract":27,"author":27,"body":28,"description":183,"extension":184,"head":27,"image":185,"imageAlt":26,"keywords":186,"meta":193,"modified":27,"navigation":194,"path":195,"proficiencyLevel":27,"published":196,"rawbody":197,"schemaOrg":27,"schemaType":27,"section":198,"seo":199,"stem":202,"__hash__":203},"blog\u002Fblog\u002Fjune-2026-newsletter.md","The Stadia Maps Newsletter №15 – June 2026",null,{"type":29,"value":30,"toc":167},"minimark",[31,36,39,44,53,57,82,84,88,96,98,102,110,113,120,123,130,133,140,143,145,149,152,158,160],[32,33,35],"h1",{"id":34},"the-stadia-maps-newsletter-15","The Stadia Maps Newsletter №15",[37,38],"hr",{},[40,41,43],"h2",{"id":42},"welcome-to-our-growing-leadership-team","Welcome to Our Growing Leadership Team",[45,46,47,48],"p",{},"Building a company around a conviction that maps are critical infrastructure, not an ad product, takes a particular kind of person, and two of them just joined Stadia Maps. Rob Yoegel and Rick Myers both spent years at Linode (now Akamai), building a developer-loved business in a market full of cynical alternatives. ",[49,50,52],"a",{"href":51},"\u002Fblog\u002Ftwo-leaders-join-stadia-maps\u002F","Read the full announcement here.",[40,54,56],{"id":55},"explore-our-platform","Explore Our Platform",[58,59,60,70,76],"ul",{},[61,62,63],"li",{},[49,64,69],{"href":65,"rel":66,"target":68},"https:\u002F\u002Fdocs.stadiamaps.com\u002F",[67],"external","_blank","API Documentation",[61,71,72],{},[49,73,75],{"href":74},"\u002Fproducts\u002F","Platform Features & Overview",[61,77,78],{},[49,79,81],{"href":80},"\u002Fblog\u002F","Company Blog",[37,83],{},[40,85,87],{"id":86},"we-updated-our-changelog-yes-really","We Updated Our Changelog (Yes, Really)",[45,89,90,91,95],{},"Moving forward, we're committing to keeping it current. If you want updates without checking back manually, ",[49,92,94],{"href":93},"\u002Fchangelog\u002F","our changelog now has a long-overdue RSS feed",", too.",[37,97],{},[40,99,101],{"id":100},"latest-from-our-blog","Latest From Our Blog",[103,104,106],"h3",{"id":105},"how-we-fixed-water-feature-rendering-across-all-zoom-levels-in-our-basemaps",[49,107,109],{"href":108},"\u002Fblog\u002Ffixing-missing-water-interactive-basemaps\u002F","How We Fixed Water Feature Rendering Across All Zoom Levels in Our Basemaps",[45,111,112],{},"We shipped a significant update to the data pipeline behind our Interactive Basemaps. The change fixes a class of visual inconsistencies at low- and mid-zoom levels, such as missing rivers, shifting coastlines, islands that suddenly appear, and major water features that pop into detail abruptly rather than transitioning smoothly.",[103,114,116],{"id":115},"the-invisible-costs-of-routing-privacy-pricing-and-avoiding-the-mau-trap",[49,117,119],{"href":118},"\u002Fblog\u002Finvisible-costs-of-routing-privacy-pricing-mau-trap\u002F","The Invisible Costs of Routing: Privacy, Pricing, and Avoiding the \"MAU\" Trap",[45,121,122],{},"Beyond performance, the long-term viability of any motor vehicle routing project hinges on two \"invisible\" variables: data privacy architecture and billing predictability. Stadia Maps eliminates the risks of third-party data harvesting and \"MAU\"-based pricing traps by providing a private-by-design infrastructure and transparent, usage-only billing.",[103,124,126],{"id":125},"beyond-the-car-routing-for-the-other-90-of-transport",[49,127,129],{"href":128},"\u002Fblog\u002Fbeyond-the-car-routing-for-specialized-fleets\u002F","Beyond the Car: Routing for the Other 90% of Transport",[45,131,132],{},"Standard \"car-first\" routing APIs often fail to account for the unique legal and physical constraints of specialized fleets. Stadia Maps bridges this gap by leveraging the Valhalla routing engine and OpenStreetMap data to provide granular, modal-specific routing for everything from 10-ton trucks and e-bikes to low-speed vehicles (LSVs).",[103,134,136],{"id":135},"why-basic-openstreetmap-routing-needs-real-time-traffic",[49,137,139],{"href":138},"\u002Fblog\u002Fwhy-osm-routing-needs-real-time-traffic\u002F","Why Basic OpenStreetMap Routing Needs Real-Time Traffic",[45,141,142],{},"OpenStreetMap (OSM) provides a world-class geographic foundation, but it remains a static dataset. Without real-time traffic integration, routing engines must rely on algorithmic proxies like road class and legal speed limits, which often lead to unreliable ETAs and logistics bottlenecks.",[37,144],{},[40,146,148],{"id":147},"whats-coming-next","What's Coming Next",[45,150,151],{},"In our next issue, we'll start a new blog series on Geocoding & Search and introduce a new feature highlighting some of our customers.",[45,153,154],{},[155,156,157],"em",{},"— Luke, Ian, and the entire Stadia Maps team",[37,159],{},[45,161,162,163],{},"Have feedback or questions? ",[49,164,166],{"href":165},"\u002Fsupport\u002F","We'd love to hear from you.",{"title":168,"searchDepth":169,"depth":169,"links":170},"",4,[171,173,174,175,182],{"id":42,"depth":172,"text":43},2,{"id":55,"depth":172,"text":56},{"id":86,"depth":172,"text":87},{"id":100,"depth":172,"text":101,"children":176},[177,179,180,181],{"id":105,"depth":178,"text":109},3,{"id":115,"depth":178,"text":119},{"id":125,"depth":178,"text":129},{"id":135,"depth":178,"text":139},{"id":147,"depth":172,"text":148},"Two new leaders join Stadia Maps, updated changelog with RSS feed, and latest blog posts on water features, routing privacy, and transportation alternatives.","md","\u002Fimages\u002Fog\u002Fjune-2026-newsletter.png",[187,188,189,190,191,192],"Stadia Maps Newsletter","Mapping Infrastructure","Routing APIs","Basemaps","Geocoding","Developer Platform",{},true,"\u002Fblog\u002Fjune-2026-newsletter","2026-06-30","---\ntitle: The Stadia Maps Newsletter №15 – June 2026\ndescription: Two new leaders join Stadia Maps, updated changelog with RSS feed, and latest blog posts on water features, routing privacy, and transportation alternatives.\nimage: \u002Fimages\u002Fog\u002Fjune-2026-newsletter.png\nimageAlt: The Stadia Maps Newsletter №15 – June 2026\nkeywords:\n  - Stadia Maps Newsletter\n  - Mapping Infrastructure\n  - Routing APIs\n  - Basemaps\n  - Geocoding\n  - Developer Platform\npublished: 2026-06-30\nsection: Newsletter\nseo:\n  title: Stadia Maps Newsletter №15 | June 2026 Updates\n  description: \"Latest from Stadia Maps: New leadership team, changelog RSS feed, improved water feature rendering, routing privacy, and multi-transport support.\"\n---\n\n# The Stadia Maps Newsletter №15\n\n---\n\n## Welcome to Our Growing Leadership Team\n\nBuilding a company around a conviction that maps are critical infrastructure, not an ad product, takes a particular kind of person, and two of them just joined Stadia Maps. Rob Yoegel and Rick Myers both spent years at Linode (now Akamai), building a developer-loved business in a market full of cynical alternatives. [Read the full announcement here.](\u002Fblog\u002Ftwo-leaders-join-stadia-maps\u002F)\n\n## Explore Our Platform\n\n- [API Documentation](https:\u002F\u002Fdocs.stadiamaps.com\u002F)\n- [Platform Features & Overview](\u002Fproducts\u002F)\n- [Company Blog](\u002Fblog\u002F)\n\n---\n\n## We Updated Our Changelog (Yes, Really)\n\nMoving forward, we're committing to keeping it current. If you want updates without checking back manually, [our changelog now has a long-overdue RSS feed](\u002Fchangelog\u002F), too.\n\n---\n\n## Latest From Our Blog\n\n### [How We Fixed Water Feature Rendering Across All Zoom Levels in Our Basemaps](\u002Fblog\u002Ffixing-missing-water-interactive-basemaps\u002F)\n\nWe shipped a significant update to the data pipeline behind our Interactive Basemaps. The change fixes a class of visual inconsistencies at low- and mid-zoom levels, such as missing rivers, shifting coastlines, islands that suddenly appear, and major water features that pop into detail abruptly rather than transitioning smoothly.\n\n### [The Invisible Costs of Routing: Privacy, Pricing, and Avoiding the \"MAU\" Trap](\u002Fblog\u002Finvisible-costs-of-routing-privacy-pricing-mau-trap\u002F)\n\nBeyond performance, the long-term viability of any motor vehicle routing project hinges on two \"invisible\" variables: data privacy architecture and billing predictability. Stadia Maps eliminates the risks of third-party data harvesting and \"MAU\"-based pricing traps by providing a private-by-design infrastructure and transparent, usage-only billing.\n\n### [Beyond the Car: Routing for the Other 90% of Transport](\u002Fblog\u002Fbeyond-the-car-routing-for-specialized-fleets\u002F)\n\nStandard \"car-first\" routing APIs often fail to account for the unique legal and physical constraints of specialized fleets. Stadia Maps bridges this gap by leveraging the Valhalla routing engine and OpenStreetMap data to provide granular, modal-specific routing for everything from 10-ton trucks and e-bikes to low-speed vehicles (LSVs).\n\n### [Why Basic OpenStreetMap Routing Needs Real-Time Traffic](\u002Fblog\u002Fwhy-osm-routing-needs-real-time-traffic\u002F)\n\nOpenStreetMap (OSM) provides a world-class geographic foundation, but it remains a static dataset. Without real-time traffic integration, routing engines must rely on algorithmic proxies like road class and legal speed limits, which often lead to unreliable ETAs and logistics bottlenecks.\n\n---\n\n## What's Coming Next\n\nIn our next issue, we'll start a new blog series on Geocoding & Search and introduce a new feature highlighting some of our customers.\n\n*— Luke, Ian, and the entire Stadia Maps team*\n\n---\n\nHave feedback or questions? [We'd love to hear from you.](\u002Fsupport\u002F)\n","Newsletter",{"title":200,"description":201},"Stadia Maps Newsletter №15 | June 2026 Updates","Latest from Stadia Maps: New leadership team, changelog RSS feed, improved water feature rendering, routing privacy, and multi-transport support.","blog\u002Fjune-2026-newsletter","mupkg6F2XcrvPUnn0VAf2mkcsEOns50n1eHTkKpEkek",[205,220,233],{"title":206,"description":207,"path":208,"published":209,"keywords":210,"rawbody":219},"The Open Data Superpower: Why Global Search is Moving Beyond Proprietary Silos","Stadia Maps builds geocoding & search on continuous open data streams — rapid updates, community fix-it loops, multilingual search, and precision reverse geocoding.","\u002Fblog\u002Fopen-data-geocoding-global-search","2026-07-08",[191,211,212,213,214,215,216,217,218],"Geocoding API","Reverse Geocoding","Open Data","OpenStreetMap","Multilingual Search","Localization","On-Premise Geocoding","Location Search","---\ntitle: \"The Open Data Superpower: Why Global Search is Moving Beyond Proprietary Silos\"\ndescription: Stadia Maps builds geocoding & search on continuous open data streams — rapid updates, community fix-it loops, multilingual search, and precision reverse geocoding.\nauthor: ian-wagner\nhead:\n  meta:\n    - property: og:image:width\n      content: \"1200\"\n    - property: og:image:height\n      content: \"630\"\n    - property: og:image:type\n      content: image\u002Fpng\n    - property: article:tag\n      content: Geocoding\n    - property: article:tag\n      content: Open Data\n    - property: article:tag\n      content: Reverse Geocoding\n    - property: article:tag\n      content: Localization\n    - property: article:tag\n      content: Location Search\nimage: \u002Fimages\u002Fog\u002Fglobal-search-proprietary-silo-og.png\nimageAlt: \"The Open Data Superpower: Why Global Search is Moving Beyond Proprietary Silos — Stadia Maps\"\nkeywords:\n  - Geocoding\n  - Geocoding API\n  - Reverse Geocoding\n  - Open Data\n  - OpenStreetMap\n  - Multilingual Search\n  - Localization\n  - On-Premise Geocoding\n  - Location Search\npublished: 2026-07-08\nsection: Geocoding\nseo:\n  title: \"Open Data Geocoding API: Global Search, Rapid Updates\"\n  ogTitle: The Geocoding Engine Built on Open Data, Not Black Boxes\n  description: Stadia Maps geocoding & search APIs ingest continuous open data for rapid updates, multilingual search, and precision reverse geocoding — no proprietary black box.\n---\n\n# The Open Data Superpower: Why Global Search is Moving Beyond Proprietary Silos\n\n> Legacy mapping providers rely on static data captured during periodic drive-bys, creating a \"black box\" where errors can persist for years. Stadia Maps solves this by building living infrastructure that ingests continuous open and proprietary data streams, offering a transparent \"fix-it\" loop and rapid updates that proprietary silos cannot match.\n\n---\n\nLegacy mapping providers rely on data captured during periodic drive-bys, which can remain unverified for years. When the physical world changes, these APIs become a liability, leading to \"destination not found\" errors and broken logistics chains.\n\nAt Stadia Maps, we solve this by building **living infrastructure**. Instead of waiting for a fleet of sensor cars to pass through a neighborhood, we ingest continuous streams of open data for our [geocoding and search APIs](\u002Fproducts\u002Fgeocoding-search\u002F).\n\n## Rapid Turnaround and the \"Fix-it\" Loop\n\nProprietary datasets often feel like a black box. If an address is wrong or a new subdivision is missing, reporting the error can feel like shouting into a void. Stadia Maps changes this dynamic by leaning into the breadth of global contributors and open, official datasets.\n\n- **Data Corrections:** We include \"fix-it\" URLs for many records directly in our API responses. These links point users to datasets that accept contributions, enabling community-driven accuracy that commercial datasets can't match.\n- **Global Localization:** We collaborate on an open-source set of address templates that respect how people actually write addresses in their home countries.\n- **Rapid Geocoding Updates:** We refresh our geocoding data at least monthly to match our maps and routing services.\n\n## Localization Without the Friction\n\nSearch quality often takes a dive when switching between scripts. Handling non-Latin characters or searching for a Korean city using its English name are common pain points for global apps. Stadia Maps supports multilingual searching across all primary data layers, including Administrative Areas and Points of Interest (POIs).\n\nWhile we continue to refine partial matches in specific East Asian scripts, our current engine remains a benchmark for internationalization, helping global apps meet users where they are.\n\n## Precision Reverse Geocoding, Down to the Feature\n\n[Reverse geocoding](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Freverse-search\u002F) is the backbone of delivery and real estate apps. A \"close enough\" result isn't sufficient when an app needs to know exactly what's at a location — not just the nearest street. Because we ingest a massive variety of data sources, we identify extremely granular features. For enterprise teams with strict security or latency requirements, we even offer this entire geocoding engine for [on-premise usage](\u002Fblog\u002Fwhy-is-your-geocoding-bill-higher-than-it-should-be\u002F).\n\n## What's Next?\n\nWe are currently planning and building features that make the switch to Stadia Maps a no-brainer for enterprise teams:\n\n- **Revamped Categorical Search:** Expect more granular detail in specialized searches, such as \"Sushi restaurants,\" ranked by distance and relevance.\n- **Deeper Internationalization:** Our team is expanding English-name search to include road names globally, bridging the gap for international logistics.\n\n---\n\nWant to learn more about what we're working on? [Contact our engineering team](mailto\\:entsales@stadiamaps.com) to discuss your specific enterprise requirements.\n",{"title":221,"description":222,"path":223,"published":224,"keywords":225,"rawbody":232},"Precision Meets Privacy: Elevating the Consumer Search Experience","Stadia Maps geocoding API delivers structured search, reverse geocoding, and autocomplete across 1B+ locations — no user tracking, no ad-network bias.","\u002Fblog\u002Fprecision-meets-privacy-consumer-search-experience","2026-06-17",[191,212,226,227,228,229,230,214,231,218],"Structured Geocoding","Autocomplete","Address Search","Privacy","GDPR","Foursquare","---\ntitle: \"Precision Meets Privacy: Elevating the Consumer Search Experience\"\ndescription: Stadia Maps geocoding API delivers structured search, reverse geocoding, and autocomplete across 1B+ locations — no user tracking, no ad-network bias.\nauthor: ian-wagner\nimage: \u002Fimages\u002Fog\u002Fprecision-meets-privacy-consumer-search-experience.png\nimageAlt: \"Precision Meets Privacy: Geocoding API With Global Coverage and No Tracking — Stadia Maps\"\nkeywords:\n  - Geocoding\n  - Reverse Geocoding\n  - Structured Geocoding\n  - Autocomplete\n  - Address Search\n  - Privacy\n  - GDPR\n  - OpenStreetMap\n  - Foursquare\n  - Location Search\nmodified: 2026-07-02\npublished: 2026-06-17\nsection: Geocoding\nseo:\n  title: \"Geocoding API: Structured Search, No Tracking\"\n  ogTitle: The Geocoding API That Doesn't Track Your Users\n  description: Stadia Maps geocoding API delivers structured search, reverse geocoding, and autocomplete across 1B+ locations — no user tracking, no ad-network bias.\n---\n\n# Precision Meets Privacy: Elevating the Consumer Search Experience\n\n> Developers often hit a ceiling when moving from a search prototype to a production-ready global product. Stadia Maps delivers more reliable [structured geocoding](https:\u002F\u002Fstadiamaps.com\u002Fblog\u002Fopen-data-geocoding-global-search\u002F) by aggregating open datasets from across the globe, applying freshness signals to POI data, and providing structured endpoints that eliminate the black box guesswork of single-string search. All while maintaining a strict no-tracking policy.\n\n---\n\nBuilding a location-aware application often starts with a simple goal: helping users find where they need to go. Let's look at the specific gaps in the current geocoding landscape and how we've built a more reliable path forward.\n\n## Coverage and Data Quality\n\n[Our geocoding API](\u002Fproducts\u002Fgeocoding-search\u002F) surfaces three core capabilities: [fuzzy search and autocomplete](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fautocomplete\u002F) to resolve ambiguous input in under 100ms, [reverse geocoding](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Freverse-search\u002F) to convert coordinates into street-level addresses from a dataset of over 1 billion locations globally, and [structured data](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fstructured-search\u002F) access for clean, parsed results that satisfy strict schema requirements. All three depend on the same thing: data you can trust.\n\nGeocoding quality isn't just about how often data updates. It's about how many sources you draw from and whether those sources tell you something meaningful. A single-provider dataset, no matter how frequently refreshed, will have gaps. [We aggregate open datasets from across the globe](\u002Fblog\u002F75-million-more-addresses-geocoding-precision\u002F), giving you broader coverage than any single source provides. For POI data specifically, we use Foursquare's freshness signals to reduce the likelihood that a result points to a location that closed years ago.\n\n## Move Beyond the Single-String Black Box\n\nFree-form single-string search is popular, but it's often an inefficient way to handle data. Most providers force you into a \"black box\" parser that guesses what your user meant, which works until it doesn't.\n\nStructured search shines when you already know something about your data, such as information from a shipping form or a registration profile. Structured geocoding endpoints let you pass postal codes, specific cities, and other clean facts directly to the engine. Removing ambiguity ensures better results and more reliable handling of local conventions, such as the wildly varying ways different countries format unit numbers.\n\n## Real Results in an Ad-Driven World\n\nIn an era when \"near me\" searches are auctioned off to the highest bidder, location infrastructure has effectively become an ad network. Unlike industry giants that harvest user behavior for profiling or bias results toward paid advertisers, our search APIs are built to be a transparent source of truth.\n\nOur no-tracking policy ensures that end-user searches don't get used to create behavioral profiles. Avoiding data harvesting leads to a more honest discovery experience. Users see what is actually there rather than what a platform was paid to show them.\n\n---\n\nReady to see the difference for yourself? [Get started for free](https:\u002F\u002Fclient.stadiamaps.com\u002Fsignup\u002F) and test our [Search API](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Foverview\u002F) today.\n",{"title":87,"description":234,"path":235,"published":236,"keywords":237,"rawbody":244},"Catch up on everything Stadia Maps shipped since mid-2024 — traffic-influenced routing, Geocoding v2 with hundreds of millions of new POIs, a 37M km² satellite imagery update, and new mobile SDKs. Plus, subscribe via RSS to stay current.","\u002Fblog\u002Fwe-updated-our-changelog","2026-06-02",[238,239,240,241,191,242,243],"Changelog","Product Updates","RSS","Traffic-Influenced Routing","Satellite Imagery","SDKs","---\ntitle: We Updated Our Changelog (Yes, Really)\nauthor: luke-seelenbinder\ndescription: Catch up on everything Stadia Maps shipped since mid-2024 — traffic-influenced routing, Geocoding v2 with hundreds of millions of new POIs, a 37M km² satellite imagery update, and new mobile SDKs. Plus, subscribe via RSS to stay current.\nimage: \u002Fimages\u002Fog\u002Fchangelog-update-og.png\nimageAlt: Stadia Maps changelog update announcement graphic\nsection: \"Company\"\nkeywords:\n  - Changelog\n  - Product Updates\n  - RSS\n  - Traffic-Influenced Routing\n  - Geocoding\n  - Satellite Imagery\n  - SDKs\npublished: 2026-06-02\nseo:\n  title: \"Stadia Maps Product Updates: Maps, Routing, Navigation, Geocoding, and more\"\n  description: Catch up on everything Stadia Maps shipped since mid-2024 — traffic-influenced routing, Geocoding v2 with hundreds of millions of new POIs, a 37M km² satellite imagery update, and new mobile SDKs. Plus, subscribe via RSS to stay current.\n---\n\n# We Updated Our Changelog (Yes, Really)\n\n> Stadia Maps shipped traffic-influenced routing, Geocoding v2, a 2026 satellite imagery update covering 37 million km², and new mobile SDKs between mid-2024 and mid-2026 — all of it is now documented in a fully updated [changelog](\u002Fchangelog\u002F) with an [RSS feed](\u002Fchangelog\u002Frss.xml).\n\nWe've shipped a lot since mid-2024. [Traffic-influenced routing](\u002Fblog\u002Ftraffic-influenced-routing-in-public-preview\u002F). [Geocoding v2](\u002Fblog\u002Fintroducing-stadia-maps-geocoding-search-v2\u002F) and data updates, including hundreds of millions of new POIs and addresses. A [2026 satellite imagery update](\u002Fblog\u002F2026-satellite-imagery-update\u002F) covering 37 million km². New SDKs, [autocomplete UI components for SwiftUI and Jetpack Compose](\u002Fblog\u002Fautocomplete-search-for-swiftui-and-jetpack-compose\u002F), and more.\n\nNone of it made it into our [changelog](\u002Fchangelog\u002F).\n\nThat's on us.\n\nWe got heads-down building and let updating the changelog slide, which defeats the point of having one. We've gone back and filled in everything since June 2024. Go take a look.\n\nMoving forward, we're committing to keeping it current. If you want updates without checking back manually, our changelog now has a long-overdue [RSS feed](\u002Fchangelog\u002Frss.xml), too.\n",1787151429269]