Migration to 10 #691
Comments
|
@tobrun @m0nac0 Can we please have some input here? I have several projects in Flutter relying on Mapbox and would love to see v10 support. I also don't believe that such an initiative can come to success made by community-only without any official support by Mapbox team/company. |
|
To clarify: I do not work for Mapbox (and I never have), I just contribute to this plugin because I find it very useful and I love Mapbox's maps and map services. Therefore, I obviously can't comment on whether Mapbox plans to provide official flutter support. But I think it has been suggested before that it's a good idea to reach out to them directly and tell them that you would be interested in official Mapbox flutter support. They may consider providing it, if they see that there's enough interest. Personally, I do hope to be able to continue contributing to this plugin, but it's greatly dependent on how much spare time I'll have for this, and I can't exactly anticipate that, yet. |
|
Tobrun is a Technical Lead of Mapbox Maps SDK for Android, so I assume he can answer these kinds of questions. |
|
Very interested in a v10 upgrade as well. |
|
Thank you all for reaching out and requesting this!
As a Mapbox employee, I can't make any public statement that Mapbox SDKs will officially support Flutter. I would love to see this project adopt the v10 codebase (lot of cool new features!) and current API surface of this repo is too limited (not able to change style properties for example) but I would also love to see a better approach as the current platform plugins setup (see #140). This would make maintenance almost a breeze when compared to current approach. To get that to work however, it would require a Mapbox commitment to invest into the Flutter ecosystem and Dart language. |
|
@tobrun thanks a lot for the answer, although it doesn't give us much understanding on what to do. My project depends heavily on flutter mapbox support and I need to understand how to drive it forward. Current implementation has some very important features missing. |
|
I am in the same boat as you, my project heavily depends on the ability to have a performant mapping solution. I am set on using mapbox. What can we do to get this process started? I have no problem with committing my time to helping to bring v10 access to flutter apps. Even if we have to start from the ground up, I am onboard. When do we start? |
|
@JMNewsome v10 just got production ready yesterday. Maybe now @tobrun can push a bit internally in Mapbox and give us some kind of clarity on next steps for Mapbox on Flutter? |
|
This is actually one other problem I have with future v10. While it looks great it doesn't have offline side-loading support, at least it's not mentioned anywhere. My project requires offline side-loading. |
|
I understand the situation you have. I don’t mind personally committing a portion of my time with making it, because I strongly need mapbox in general for my app concept. The main issue is I don’t exactly know what I need to do to start it, I’m need to making extensions for flutter, but if there is a general guidelines or resource on how incorporating mapbox v10 into flutter. I don’t mind atleast gnawing at it |
|
@AAverin should we not just add V10 here? The API should not be that different right? |
|
@felix-ht We could try to have a separate branch or tag and keep it in this repo. |
|
I agree with @AAverin, looking at the SDK a lot of things have changed and, TBH, maybe part of the wrapper should be rewritten to match the underlying SDK. |
It is :) v10 compared with v9 (android) and v6 (iOS) is a completely new SDK, build from the ground up with new internal technology stack. The main difference from consumer point of view is the adoption of Kotlin/Swift instead of Java/Obj-C in previous version. When it comes to public API, we have tried to bring the APIs across platforms closer together (which should help a lot for this project going forward!).
No definitive answer yet atm but will be able to speak about this in upcoming weeks. |
Can't wait for some news! We're about to start a cool project using this really cool flutter mapbox plugin, and we'd like to know if it's worth investing porting some APIs on this version or wait for a mapbox-supported plugin a do a minimal POC with this plugin version :-) Thank you all for your awesome job!! 👏 |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
Any updates, any hints? @tobrun |
|
Hi @AAverin , did you resolve the problem? |
|
@edofritz I have tried reaching Mapbox through every channel I could find but they just don't respond on any emails or request for meetings and sales requests. |
|
@AAverin Well you still could run a local tile server that streams the tiles to mapbox as if it where hosted somewhere. A Raster tile server would be trivial to do for the xyz format. For Vector data this might be a good starting point: https://github.com/saigontek/dart-vector-tile |
|
Thanks @felix-ht, I will try to investigate a bit more. I don't mind paying for the feature, as long as I can still pre-generate offline packs and let users download, but I can't reach to Mapbox to talk about details, they just don't respond. |
|
Do we have to wait for mapbox to do anything ? It's implementable today without any change on their side, isn't it ? It's a bit unclear when reading the comments here what it is that you want from map box. I see there is a branch already using v10 https://github.com/flutter-mapbox-gl/maps/commits/kl-v10 Also I think it makes sens to keep this repository if the dart public api stays the same (or close to). |
|
I haven't run that branch yet but looking at the diff it's rather small and seems to cover android only. Maybe author @Chaoba can tell us more? |
|
Thanks @oosafff , web would be very much appreciated as many of us currently rely upon it in through this plugin. From what we have heard the version of mapbox used by this plugin would stop working in the new year some time, so at a minimum it would be nice to know that it would not be disabled until your new flutter plugin is ready with web+mobile. |
|
@oosafff Covering other platforms (desktop, web) besides mobile + having a way to do navigation would allow us to expand our product to many more customers. Flutter is unique in this regard, allowing to do so much more than just a mobile app. We would also love to get 3D maps that were advertised for original mapbox mobile SDKs. I have about a 100 questions, but will wait for a proper SDK announcement first =) |
@oosafff You're very welcome! Please note that current plugin, started from Mapbox and adopted by @tobrun and then by the community (@felix-ht and @AAverin in particular) does partly support web. Personally I think it's very important to have this unification, especially since a lot of ground work is already done by this plugin. |
|
@oosafff i have to say that not having web is a hard blocker for my usecase. One thing to note is that with the plugin system of flutter it would be possible to just create a flutter web plugin that satiesfies whatever interface is required by the new However having first party support for web would be much much better. |
Note that this plugin it will not be disabled - the only thing that changes is that mapbox won't support the old ios and android code after that point in time. So no more bug fixes from their side for the native code. |
|
My understanding was that there are no bugfixes to the native code since 2019, no? At least no matter the complaints and attempts to reach out, everything was scoped out in favour of v10 implementation. |
|
@AAverin indeed - thats why flutter 3.X was such a pain already |
|
@oosafff Hi, just wanted to ask if there any new forecast on timing? Another clarification is that we want to use Navigation SDK in our app alongside with another web service that changes itinerary of stop points and to update a current route(without finishing and starting a new route). As for now we are sticked to another unofficial plugin with only functionality to start and finish route. Thanks in advance! |
|
Any news regarding the public beta? It is the last week of November - Will the beta be published as planned? |
|
We might have to wait for the BUILD with Mapbox event on Thursday 🤔 "Mapbox is unveiling our latest features and upgrades on Dec 1 at BUILD with Mapbox, and you’re invited! Learn about our virtual event and register today" |
|
The agenda is not mentioning a possible flutter sdk at all. |
|
Looks like a delay. Flutter SDK is only listed as "coming soon" at the bottom of the release page. |
|
And it looks like Web is ignored completely. |
|
Flutter SDK seems Mobile only |
|
Well, let's hope Android and iOS are bug-free and fully features, so that the only way to go would be to add more platforms, like Web and Desktop =) |
|
I asked in the AMA as well - the answer was that they will wait to see how the adoption goes and depending on that add web and desktop support. Launch will be iOS and Android tho. |
|
They created a Discord to interact with the community, on it, Chris Wrong from Mapbox said that they plan to publish the public beta on pub.dev next week. Edit: |
|
@Bazni can you share the link? |
|
Well, it should be a big improvement in any case. And there is only one trajectory it can take – become better and support more platforms. |
|
It is out: https://pub.dev/packages/mapbox_maps_flutter |
|
That's a good news! |
|
Works for me on iOS after I changed the min OS version in However, with Android I get the following issue: I added the token to Do you have any suggestion? I cannot access the Discord mentioned above. |
|
Hi @demux79, here is the discord link : https://discord.gg/PEjJHgwm |
|
@demux79 I had the same problem, to fix it you need to install ktlint. I'm not sure of the necessity to lint the code in this context, I will ask the team if it's normal :) |
|
I took a good look at the new Mapbox plugin. Works as advertised, all in all, kudos @oosafff! It is derived from the original opensourced project and shares some similarities with the current pre10 community supported plugin. However there's no web support. And the new plugin is implemented with a lot of private classes that are semi exposed to the outside, making it nearly impossible or at least very hard to extend, implement classes or make a sustainable wrapper, should the community decide to make the effort and try to implement the web version as well. That's a blocker. @oosafff In that scope I think it makes sense for ur to keep supporting the current plugin and keep reviewing merging PRs and/or find people who can and are willing to help. Also (and this is a pure mapbox feature request) 3d polygons and polylines would be greatly appreciated: mapbox/mapbox-gl-js#6987, mapbox/mapbox-gl-js#3993, mapbox/mapbox-gl-js#12227 @oosafff |
|
I saw in Discord that repo for the new SDK should be up soon and everyone will be able to create issues and feature requests there. |
Sadly its not open source yet , i would've loved to be able to make my own fork and add support to 3d model from 10.6.2. good job anyway. |
|
Not an official open-source version, but for the time being, here is the link to explore this specific project version. https://github.com/motrieux-thomas/mapbox_maps_flutter-0.3.0 |
|
official repo here https://github.com/mapbox/mapbox-maps-flutter |
and others
Any plans on supporting v10?
https://docs.mapbox.com/android/beta/maps/guides/migrate-to-v10/
Looking at the migration guide it seems that there is not much sense in migrating but rather creating a new repo to back the v10 API, since the entire codebase had changed significantly.
Or is there anybody else who's doing the migration somewhere else?
The text was updated successfully, but these errors were encountered: