Skip to content

Inline Google Maps support #73

Closed
Closed

Description

@FlutterIssues

Issue by Hixie
Thursday Jul 16, 2015 at 22:26 GMT
Originally opened as https://github.com/flutter/engine/issues/30


From @collinjackson on July 8, 2015 20:23

We are going to want to have support for maps in Sky.

There are a few ways we might go about doing this:

  1. Use native maps widget for each platform to render the map
  2. Use maps widget for each platform to render to a texture and draw the map ourselves
  3. Develop a custom maps SDK for Sky

The second option would be ideal but may not be possible. We should investigate which approach is best and build a demo app.

Copied from original issue: domokit/mojo#310

Activity

  1. FlutterIssues commented on Nov 9, 2015

    @FlutterIssues
    Author

    Comment by eseidelGoogle
    Wednesday Aug 05, 2015 at 19:35 GMT


    We might need this for the Fitness app, depending.

  2. added this to the milestone on Nov 9, 2015
  3. added
    frameworkflutter/packages/flutter repository. See also f: labels.
    c: new featureNothing broken; request for a new capability
    on Nov 9, 2015
  4. Hixie commented on Dec 16, 2015

    @Hixie
    Contributor

    This is presumably going to be a "third-party" component, right?

  5. collinjackson commented on Dec 16, 2015

    @collinjackson
    Contributor

    We'll almost certainly want to use some non-Dart SDK to provide Maps support, so yes.

  6. eseidelGoogle commented on May 13, 2016

    @eseidelGoogle
    Contributor

    We expect developers will use Maps by using a "native" iOS or Android maps view, per:
    https://docs.google.com/document/d/1DOfwpL6VojCAG_zjjcA_z5ekF7rTIohV8dWn2o7_IME/edit

  7. a14n commented on May 13, 2016

    @a14n
    Contributor

    I don't see in this doc descriptions of how to integrate native widget (like Maps) into your flutter apps. Have I missed something ?

  8. eseidelGoogle commented on May 13, 2016

    @eseidelGoogle
    Contributor

    Sorry, I may have been a bit overzealous in my linking. Said doc is pre-work for Flutter to participate as a normal View inside Obj-C/Java applications. The path to add other Obj-C/Java code to them is not yet documented, no.

  9. tjerkw commented on Sep 7, 2016

    @tjerkw

    As a developer i really want to use the native Google Maps component to render inside my flutter app. I just created a flutter app and this is kind of a blocker. The only solution is to build it in Java/Android and open it when clicking a flutter button.

    Ideally I would like a 'NativeView' in flutter, which renders a native widget inside flutter.
    This is probably quite difficult because you have merge rendering / events into the flutter rendering engine.

    It also goes against the flutter 'one widget for both platforms'. However, sometimes complex widgets (like a map) are really something you want to reuse.

  10. Goutte commented on Dec 2, 2016

    @Goutte

    Hello ! I would love to know the roadmap of this feature, or even if one even exists. I have two mobile apps in the works and both rely heavily on a map. I love Dart, and I'm looking for an excuse to try Flutter.

    The solution with FlutterView looks overly complicated, from the point of view of a rookie who has never written a single line of Flutter. The other solutions do not suit my need, I need a fully interactive map.

    I don't know how hairy that is to implement in Flutter, nor if you even plan to implement it someday. Any info would be appreciated. I guess the resolution of this issue will be my signal to start development with Flutter.

  11. debunge commented on Jan 8, 2017

    @debunge

    Is there any chance maps will be implemented in 2017? I love Dart and would like very much to use Flutter, but I really need non-static maps, like showing points of interest nearby and showing the description upon the click on the point.

  12. modified the milestones: , on Jan 11, 2017
  13. owenthereal commented on Jan 17, 2017

    @owenthereal

    Any updates on this?

  14. 186 remaining items

  15. amirh commented on Nov 10, 2018

    @amirh
    Contributor

    Note that if you want to try it out on iOS you will need to enable the preview flag, see more details on:
    #19030 (comment)

  16. feinstein commented on Nov 10, 2018

    @feinstein
    Contributor

    I thinks this information should be included in the Readme.md for the library.

    Are there any plans to move this to not be an in-line solution, so I can place buttons top of the map, a bottom sheet, a drawer layout?

  17. amirh commented on Nov 10, 2018

    @amirh
    Contributor

    I'm planning to improve the documentation soon.

    Not sure what you mean regarding not being an in-line solution? Flutter widgets can be placed on top of the map now.

  18. feinstein commented on Nov 10, 2018

    @feinstein
    Contributor

    Ohh, that's great! I remember reading there couldn't be any widgets on top of the map, as if it was a different rendering layer. Is this valid for ios and android?

  19. nosmirck commented on Jan 28, 2019

    @nosmirck

    After trying the maps plugin and messing around with platform views widgets, I came to this post, the very original post, and I can say that option 3 would have been a much better option.

    I'd like to know, is there a reason why no one chose to create an actual widget for maps from scratch? I mean, the whole power for it is there! Skia is powerful enough to create it's own renderer for buildings and roads using simple graphics, or is it not possible to do so from Dart? I checked the code from rendering a simple box from Dart to the engine and I see it's possible.

    I understand there's a technical reason we need platform views, but, maps needs "native" flutter SDK, or what's the plan for Fuchsia? Keep leveraging Android's SDK to render maps? It's nonsense!

    We already have a platform view that seems to be working fine, might need optimizations, but the teams can now just drop this maps implementation (basically two, one per platform) and start working on an actual maps for Flutter that would technically work on any future platform that flutter gives support, including hummingbird, PC, Mac and Linux (and many more).

    It's the best way, and you now it. The maps plugin for Unity3D doesn't use the native view, it's entirely custom for the engine and with amazing customizability! We need that for Flutter too, it's much more rich and useful than what a platform view of a map can do.

    Also, it will bring an idea for us, developers, on how actually use the graphics engine on a low level to build other stuff.

    I hope you guys don't take this wrong, but, I truly believe that the maps plugin through platform views already fulfilled his goal: to make possible native views to be rendered as widgets.

    Oh, before I end this: I thought that maybe this could extend to WebViews (having an actual browser engine that renders using skia) is something useful, maybe not, maybe it's just too much (for now) but would solve the issue of having different renderers for WebViews per platform (like the intention of the flutter maps), however, an integration with chrome engine somehow would be amazing, I mean, if the platform is able of running chromium it could technically serve as a web renderer and provide a channel to render WebViews inside Flutter.

    That's it! I'm going to bed now :)

  20. hundeva commented on Jan 28, 2019

    @hundeva

    I assume that the very long time plan is to develop something independent from the underlying platform (option 3). However, in the meanwhile, this was a "low hanging fruit", to support the current two main platforms. I have no doubt that before long, third party solutions will pop up, for example nothing stops noone from creating an OSM package.

  21. github-actions commented on Aug 31, 2021

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  22. locked as resolved and limited conversation to collaborators on Aug 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

c: new featureNothing broken; request for a new capabilitycustomer: mulligan (g3)engineflutter/engine related. See also e: labels.frameworkflutter/packages/flutter repository. See also f: labels.p: mapsGoogle Maps pluginpackageflutter/packages repository. See also p: labels.

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions