# Google Maps Published articles for Google Maps. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Bringing Google Maps to Friendly Meals with Firebase AI Logic DevFeed: [Bringing Google Maps to Friendly Meals with Firebase AI Logic]() Original publisher: [Read original article]() Author: Marina Coelho Published: 2026-07-28T00:00:00Z Content type: tutorial Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [Artificial Intelligence](), [Google Maps](), [Android](), [Kotlin](), [Google](), [SDKs](), [Mobile](), [personalization](), [real-time](), [configuration]() Tags: [ai](), [ai-logic](), [android](), [build](), [configuration](), [features](), [firebase](), [firebase-ai-logic](), [gemini](), [google](), [google-maps](), [grounding](), [kotlin](), [mobile](), [personalization](), [prompt](), [real-time](), [sdks](), [time]() ### AI overview A Firebase team tutorial explains how to add a Store Finder feature to the Friendly Meals Android app using Grounding with Google Maps through Firebase AI Logic. The Kotlin implementation uses location-aware Gemini responses to provide nearby businesses, operational details, and geographic personalization. ### Source excerpt News, tutorials, and updates from the Firebase team. ## Codename One Adds a Pure-Vector MapView and Pluggable Native Map Providers DevFeed: [Codename One Adds a Pure-Vector MapView and Pluggable Native Map Providers]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-06-27T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Framework](), [Google Maps](), [Code]() Tags: [api](), [code](), [framework](), [google-maps](), [maps](), [native](), [vector]() ### AI overview The article describes a Codename One mapping update that adds a pure-vector MapView and a NativeMap using platform map providers behind a shared API. The vector engine uses Mapbox Vector Tiles, existing drawing pipelines, pluggable tile sources, and MapLibre-subset JSON styling. ### Source excerpt A pure-vector MapView rendered through Graphics plus a NativeMap whose provider is wired by a build hint, not code. ## Bringing the real world to your AI application using Firebase AI Logic DevFeed: [Bringing the real world to your AI application using Firebase AI Logic]() Original publisher: [Read original article]() Author: Ankita Saxena; Ken Nevarez Published: 2026-05-19T00:00:00Z Content type: tutorial Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [Artificial Intelligence](), [Google Maps](), [Generative AI](), [Large Language Model](), [JavaScript](), [Web Components](), [API](), [Mobile]() Tags: [ai](), [ai-logic](), [api](), [firebase](), [firebase-ai-logic](), [gemini](), [generative-ai](), [google-maps](), [hallucinations](), [javascript](), [tutorials](), [web]() ### AI overview Firebase introduces Grounding with Google Maps in the Firebase AI Logic SDK to help mobile and web applications produce location-aware responses based on real-world geospatial data. The article explains configuring the model, plotting places with Google Maps Web Components, and using grounding metadata for citations and coordinates. ### Source excerpt News, tutorials, and updates from the Firebase team. ## Google Maps UI Test Automation with Maestro - Full Tutorial DevFeed: [Google Maps UI Test Automation with Maestro - Full Tutorial]() Original publisher: [Read original article]() Author: Leland Takamine Published: 2025-07-01T16:23:00Z Content type: tutorial Language: en Sources: [mobile.dev - Medium]() Topics: [Testing](), [Test automation](), [Google Maps](), [Automation](), [YAML](), [Tutorial](), [Mobile]() Tags: [automation](), [cli](), [google-maps](), [maestro](), [maps](), [open-source](), [test-automation](), [tutorial](), [ui-testing](), [yaml]() ### AI overview A step-by-step tutorial for automating a Google Maps UI test with the open-source Maestro framework. It covers installing the Maestro CLI, launching the app with clearState, tapping, typing, swiping, scrolling until an element is visible, validating with regex, and running a complete YAML flow. ### Source excerpt Discover step-by-step automated Google Maps UI testing with Maestro: complete YAML guide to tap, input, swipe, scroll commands and fast assertions. ## Building an Uber Clone with Flutter and Supabase DevFeed: [Building an Uber Clone with Flutter and Supabase]() Original publisher: [Read original article]() Author: Tyler Shukert Published: 2024-09-05T07:00:00Z Content type: tutorial Language: en Sources: [Supabase Blog]() Topics: [Flutter](), [Supabase](), [real-time](), [data](), [Database]() Tags: [dart](), [data](), [database](), [flutter](), [google-maps](), [gps](), [guide](), [real-time](), [security-policies](), [tutorial]() ### AI overview This tutorial explains how to build the consumer-facing portion of an Uber-like ride application with Flutter and Supabase. It demonstrates real-time driver location tracking using geographical data, PostGIS, Supabase Realtime, database tables, row-level security policies, and database functions and triggers. Payments and the driver-facing application are outside the article's scope. ### Source excerpt Learn how to handle real-time geospatial data using Supabase Realtime and Flutter. ## Analyzing Swiss Car Accident Data to Inform Commute Timing with a Power BI Dashboard DevFeed: [Analyzing Swiss Car Accident Data to Inform Commute Timing with a Power BI Dashboard]() Original publisher: [Read original article]() Published: 2023-10-20T00:00:00Z Content type: tutorial Language: en Sources: [Mutt0-ds Notes]() Topics: [data](), [dashboards](), [Google Maps]() Tags: [car](), [dashboard](), [data](), [google-maps]() ### AI overview This article analyzes a decade of Swiss car accident data to understand when accidents are more likely and how that information may inform commute planning. It describes obtaining the data from a Swiss government dashboard, preparing multilingual fields, and working with Swiss coordinate data. The author emphasizes that the analysis is a general framework and cannot predict or prevent accidents or account for everyday disruptions. ### Source excerpt I want to express my gratitude for the positive feedbacks I received a few months ago when I used Google Maps data to determine the best... ## The future of design systems is semantic DevFeed: [The future of design systems is semantic]() Original publisher: [Read original article]() Author: Carly Ayres Published: 2023-07-27T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [Tooling](), [Code](), [Google](), [App]() Tags: [code](), [design](), [design-systems](), [figma](), [google](), [google-maps](), [tokens](), [tooling]() ### AI overview The article examines how Figma variables and design tokens support reusable design values, theming, dynamic prototyping, and closer connections between design and code. It presents these capabilities as evidence of a broader shift toward semantic design systems and discusses how teams can maintain consistent palettes at scale, including the Google Maps team's reduction of its color palette from more than 700 colors to 25 hues. ### Source excerpt Variables, one of Figma's newest features, help you streamline designs and connect more closely to code, but what do they tell us about larger shifts in the industry? We dig into what they might signal for the future of design systems. ## Analyzing My Commute Data to Find the Best Time to Go to Work DevFeed: [Analyzing My Commute Data to Find the Best Time to Go to Work]() Original publisher: [Read original article]() Published: 2023-07-07T00:00:00Z Content type: article Language: en Sources: [Mutt0-ds Notes]() Topics: [Google Maps](), [API](), [Google Cloud Platform (GCP)](), [Simulation](), [data]() Tags: [api](), [data](), [google-cloud-platform](), [google-maps](), [simulation]() ### AI overview This article analyzes personal commute data using Google Maps traffic predictions and the Google Distance Matrix API. It simulates departure times in five-minute intervals across morning and evening travel windows, finding that the results generally align with the author's prior experience while noting seasonal traffic limitations. ### Source excerpt When my commute buddy and I find ourselves stuck in traffic during our car journeys, we often daydream about finding the ideal route and... ## Integrating Google Maps, Places API, and Reverse Geocoding with Jetpack Compose DevFeed: [Integrating Google Maps, Places API, and Reverse Geocoding with Jetpack Compose]() Original publisher: [Read original article]() Author: Sanskar Agrawal Published: 2023-01-08T16:51:10Z Content type: tutorial Language: en Sources: [Sanskar's Stuff]() Topics: [Google Maps](), [Jetpack Compose](), [Android](), [API]() Tags: [android](), [api](), [geocoding](), [google-maps](), [jetpack-compose](), [places-api]() ### AI overview A tutorial for building an Android address-selection screen with Jetpack Compose, Google Maps, the Places API, and the Geocoding API. It covers Google Cloud project setup, billing, API enablement, API-key configuration, place autocomplete, and converting coordinates to addresses. ### Source excerpt Integrating Google maps into Android apps has been somewhat of a tough nut to crack for developers. With the advent of Jetpack Compose for building native UI on Android, the Google Maps team announced a Map SDK for Compose, available here. However, i... ## Personal Heatmaps DevFeed: [Personal Heatmaps]() Original publisher: [Read original article]() Author: J Evans Published: 2022-10-28T21:15:46Z Content type: tutorial Language: en Sources: [Strava Engineering]() Topics: [data](), [Algorithm](), [navigation](), [pixel](), [real-time](), [Google Maps](), [Website]() Tags: [algorithm](), [cycling](), [data](), [engineering](), [gis](), [google-maps](), [gps](), [heat](), [map](), [mapping](), [navigation](), [pixel](), [real-time](), [recursion](), [running](), [strava](), [zoom]() ### AI overview This article explains the algorithm behind Strava's Personal Heatmap, which renders an athlete's GPS activity as a frequency-based heatmap on an interactive world map. It focuses on Mercator projection and recursive map tiling, where 256x256 pixel tiles are served at different zoom levels for real-time navigation. ### Source excerpt This post discusses the algorithm behind Personal Heatmap, one of Strava's most acclaimed subscriber features. Product Overview The Personal Heatmap feature has been around in some form since 2015, but we gave it a major overhaul in 2020. For those unfamiliar, the heatmap is an aggregated view of an athlete's GPS-enabled activities on Strava. Activity data is rendered onto a map according to path traversal frequency; the more an athlete runs on a road, the brighter -- i.e. "hotter" -- that road shows up on the map. The result is a beautiful color gradient displaying the intricate web of past activities, unique to each athlete. The Personal Heatmap is displayed on an interactive world map, also known as a slippy map. Athletes can seamlessly zoom in and out or pan around to arbitrary views of the map, and their activity heat stays displayed the entire time. To enable this, we must provide a scheme for rendering and serving subsections of the world map on the fly. Enter map tiling. Mercator Projection & Map Tiling Map tiling is the practice of subdividing a map into many discrete images that can be stitched together and rendered as a single image in real-time during map navigation. The first step in choosing a tiling scheme is picking what world map to use. Enter, the Mercator Projection, the most commonly used projection of Earth as a flat, rectangular surface. We use this projection in all of our mapping products, including heatmaps. https://medium.com/media/d9e120d13950dd0f1bb4ee14108aa9a9/href Now, imagine a grid overlaying the Mercator projection. Each grid section is known as a tile, a pixel image with resolution 256x256. Every tile has an associated zoom level, and tiles are defined recursively according to this zoom level. A tile at a given zoom level can be subdivided into four equal sized tiles at a next zoom level. For example, Zoom level 0 displays the entire planet in a single 256x256 pixel image. Zoom level 1 displays the world in four 256x256 pixel images. ## Build-Hints Editor DevFeed: [Build-Hints Editor]() Original publisher: [Read original article]() Author: Codename One Published: 2022-03-01T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [configuration](), [Tool](), [Google Maps](), [API keys]() Tags: [api](), [configuration](), [google-maps](), [guide](), [tools]() ### AI overview The article introduces a Build-Hints Editor in the Codename One simulator. It explains how to launch the editor, configure build hints, use help text and API-key actions, apply or save changes, and add support for custom cn1lib build hints. ### Source excerpt In the latest plugin update, we've added a Build-Hints Editor that accessible from a menu item inside the Codename One simulator. This is intended to make it easier to edit your app's build hints, and also inform you of build hints that you may need to configure. ## Questions of the Week 47 DevFeed: [Questions of the Week 47]() Original publisher: [Read original article]() Author: Shai Almog Published: 2017-03-16T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Development](), [Google Maps](), [Bluetooth](), [Support]() Tags: [bluetooth](), [development](), [google-maps](), [support]() ### AI overview A weekly Codename One development update covering bootcamp registration, recent ComponentSelector API and Google Maps support posts, upcoming maintenance changes, Stack Overflow participation, and a Bluetooth callback-threading issue that can cause deadlocks. ### Source excerpt Thank you all for the great response to the bootcamp and especially those of you who signed up. Registration is closing in about 2 hours and we have one last spot left! I'm sure we'll put out some incredible showcase apps around May/June. Despite all my efforts going into the bootcamp things have been moving fast in Codename One development. Steve added a new blog post the other day detailing the new ComponentSelector API. It was actually committed last week but we didn't have room in the blog schedule until this week. He also posted about the big changes he made to the Google Maps support and how those can be used with z-ordered peers to make Uber style applications a reality in Codename One. ## Codename One Updates Google Maps Integration with Improved Widget Layering and Simulator Behavior DevFeed: [Codename One Updates Google Maps Integration with Improved Widget Layering and Simulator Behavior]() Original publisher: [Read original article]() Author: Steve Hannah Published: 2017-03-13T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [Google Maps](), [Mobile](), [ui](), [API](), [JavaScript](), [Library]() Tags: [announce](), [apis](), [code](), [google-maps](), [improvements](), [javascript](), [library](), [maps](), [native](), [ui](), [update]() ### AI overview Codename One released an update to its Google Maps library that allows Codename One widgets to appear over native maps and makes the simulator behave more like actual devices. The simulator now uses an internal BrowserComponent with the Google Maps Javascript API, while configuration requires separate keys for Android, iOS, and JavaScript. ### Source excerpt One of the primary use-cases that benefits from our recent improvements for native peer integration, is "map apps". That is, apps that use native maps in some shape or form. This is an extremely common use case for mobile apps these days. Codename One has supported native maps for quite some time, but (up until recently), they were limited by a couple of factors: Native Widgets Were Always In Front - Since Google Maps were "native" widgets Codename One couldn't paint over top of the map. Native widgets were always placed in front of the Codename One UI. We could place markers on the map, and draw paths using MapContainer APIs (which were backed by native code on each platform), but we couldn't, for example, place a Button over top of the map. The Simulator Still Used the Old MapComponent - The simulator didn't have support for native maps. It would just use the light-weight Codename One MapComponent, which uses tiles (rather than vector graphics like the native maps), and didn't behave the same as native maps in some cases. E.g. you could draw over top of the MapComponent, which would cause a bit of a surprise if you were counting on that, only to find out after building for iOS that your beautiful buttons were rendered behind the map. I am happy to announce that on Friday we released an update for the Google maps library that resolves both of these issues. ## Questions of the Week 46 DevFeed: [Questions of the Week 46]() Original publisher: [Read original article]() Author: Shai Almog Published: 2017-03-09T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Web](), [Google Maps](), [bug](), [debug](), [App](), [Stack Overflow](), [GitHub]() Tags: [backup](), [bug-fixes](), [debug](), [github](), [google-maps](), [maps](), [storage](), [web]() ### AI overview A weekly Codename One update covering a Google Maps library web fallback, bug fixes, new functionality, developer discussions, debugging issues, storage behavior, and Google's backup policy change. ### Source excerpt This has been one of the more exhausting weeks for me in recent years. I don't remember this level of exhaustion since those first few months of launching Codename One. Getting everything ready is the hard part, doing the actual bootcamp is the relatively easy part... Despite all of that we still got some things done this week. Steve reworked the google maps cn1lib to have a web fallback option. He wrote a pretty big post on it but I didn't want it to get lost in the whole "bootcamp launch" posts so we'll post it next week. Our update of the week includes some bug fixes and a bit of new functionality that we will cover in posts next week. ## Can Execute Hint DevFeed: [Can Execute Hint]() Original publisher: [Read original article]() Author: Shai Almog Published: 2017-01-24T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [iOS](), [Google Maps](), [API](), [App]() Tags: [api](), [apple](), [availability](), [google](), [google-maps](), [ios](), [plist](), [privacy](), [xcode]() ### AI overview This tutorial explains how Display.canExecute(url) can test whether a feature or URL is available before executing a command, such as opening Google Maps instead of Apple Maps on iOS. It also describes the iOS URL-scheme privacy change, the required plist configuration, and build-hint automation for standard URL prefixes. ### Source excerpt Display.canExecute(url) provides us with a generic tool to test the availability of a feature before executing a command. This is very useful for inter-app communications and allows us to achieve various things such as launching Google Map instead of Apple Maps on iOS. Let's say I want to navigate using Google Maps if it's installed in iOS but if not I'll settle for Apple Maps I can do something like this: ## Automatic Build Hints Configuration DevFeed: [Automatic Build Hints Configuration]() Original publisher: [Read original article]() Author: Shai Almog Published: 2017-01-17T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [configuration](), [Mobile](), [iOS](), [Android](), [Google Maps]() Tags: [android](), [api](), [apple](), [configuration](), [google-maps](), [ios](), [libraries](), [mobile]() ### AI overview Codename One introduces APIs that can detect whether build hints are set and assign values when they are missing or incorrect. The feature helps handle platform requirements such as iOS location usage descriptions and lets third-party libraries detect misconfiguration or provide setup interfaces. ### Source excerpt We try to make Codename One "seamless", this expresses itself in many small details such as the automatic detection of permissions on Android etc. The build servers go a long way in setting up the environment as intuitive. But it's not enough, build hints are often confusing and obscure. It's just hard to abstract the mess that is native mobile OS's and the odd policies from Apple/Google... E.g. a common problem developers face is location code that doesn't work in iOS. This is due to the ios.locationUsageDescription build hint that's required. The reason we added that build hint was a requirement by Apple to provide a description for every app that uses the location service. ## Questions of the Week 32 DevFeed: [Questions of the Week 32]() Original publisher: [Read original article]() Author: Shai Almog Published: 2016-11-17T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Stack Overflow](), [JavaScript](), [JavaFX](), [Google Maps](), [iOS](), [pdf](), [passwords]() Tags: [bridge](), [browser](), [google-maps](), [ios](), [java](), [javascript](), [pdf](), [posts](), [weekly]() ### AI overview A weekly Codename One update covering the standard release, plans for the 3.6 release, and answers to developer questions about permissions, running projects, UI components, galleries, dialogs, JavaScript integration, Android behavior, browser features, audio capture, iOS location authorization, and large PDF downloads. ### Source excerpt I practically had a vacation from blogging these past two weeks with all the great posts from Steve. I've put some work into something interesting but it's not yet ready for prime time. If you follow the git commits you might have noticed we'll discuss it when we think it's ready. This week we (thankfully) aren't releasing a plugin update and just releasing the standard weekly release as usual. Hopefully, things will cool down a bit and we'll be able to sprint to the 3.6 release easily. ## A better way to handle links in TextView DevFeed: [A better way to handle links in TextView]() Original publisher: [Read original article]() Author: Saket Narayan Published: 2016-09-11T17:48:21Z Content type: tutorial Language: en Sources: [Saket Narayan]() Topics: [Android](), [App]() Tags: [android](), [browser](), [google-maps](), [library](), [textview]() ### AI overview The article explains problems with Android's default LinkMovementMethod for clickable URLs in TextView, including incorrect touch areas, unreliable highlighting, and limited customization. It introduces BetterLinkMovementMethod as a drop-in replacement with custom URL-handling support. ### Source excerpt There are two ways of "linkifying" URLs in a TextView. First, as an XML attribute: and second, programmatically: TextView textView = (TextView) findViewById(R.id.text1); Linkify.addLinks(textView, Linkify.PHONE_NUMBERS | LINKIFY.WEB_URLS); In both the cases, the framework internally registers a LinkMovementMethod on the TextView that handles dispatching a ACTION_VIEW Intent when any link is clicked. This is why phone-numbers open in a dialer when clicked, [...] The post A better way to handle links in TextView appeared first on Saket Narayan. ## Highly Unconventional Suggested First Aid DevFeed: [Highly Unconventional Suggested First Aid]() Original publisher: [Read original article]() Published: 2013-03-26T00:00:00Z Content type: article Language: en Sources: [Signal Blog]() Topics: [Development](), [android-development](), [SQLite](), [Database](), [Google Maps](), [API](), [Mobile]() Tags: [android](), [android-development](), [api](), [database](), [development](), [google-maps](), [sqlite]() ### AI overview A personal account of a Spring Break of Code project in Maui describes developing an Android geofencing application. The project uses spatial databases, SQLite, SpatiaLite, and the Google Maps Android V2 API to classify environments as trusted or hostile and trigger actions on client phones. ### Source excerpt Spring Break Of Code, Day Two "I am torn on how best to introduce myself out of context like this, the idea of rattling off facts from my resume is my first instinct, but that seems terribly conventional. With the goal of introducing myself and the entirety of my character, my second (highly unconventional) instinct is to link you to my online dating profile with the prayer that such an action would be taken in the desired context. Through my indecision I hope to explain who I am and why I would like to travel across the country to be involved with the Institute for Disruptive Studies. So here goes..." Read more... ## BorderPatrol: KML border checking in Ruby DevFeed: [BorderPatrol: KML border checking in Ruby]() Original publisher: [Read original article]() Author: Square Engineering Published: 2011-07-05T16:00:00Z Content type: release Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [Ruby](), [Algorithm](), [data](), [benchmarking](), [rubygems](), [Google]() Tags: [algorithm](), [benchmarking](), [data](), [engineering](), [github](), [google-maps](), [performance](), [ruby](), [rubygems]() ### AI overview The article introduces BorderPatrol, a Ruby gem that imports KML files and determines whether points lie within regions defined by polygons. It describes support for complex regions, a point-in-polygon ray-casting algorithm, performance optimizations, and use in production for real-time and offline geospatial evaluation. ### Source excerpt Presenting a gem to import KML files and detect whether or not points are contained within defined regions.