Migration to 10

[srmncnk]

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?

[AAverin]

@tobrun @m0nac0 Can we please have some input here?
It looks like both iOS and Android SDKs for Mapbox were considerably re-written for v10.
What is the planned strategy for Flutter support, will you still drive this or it is now full on community to start the new package?

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.

[m0nac0]

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.

[AAverin]

Tobrun is a Technical Lead of Mapbox Maps SDK for Android, so I assume he can answer these kinds of questions.

[rossbroom99]

Very interested in a v10 upgrade as well.

[tobrun]

Thank you all for reaching out and requesting this!
Regarding this project, you could say I wear two different hats:

• one as Mapbox employee and technical lead for Mapbox Maps SDKs
• one as Flutter enthusiast and maintainer of this community driven plugin

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.

[AAverin]

@tobrun thanks a lot for the answer, although it doesn't give us much understanding on what to do.
Should we start the community project for v10 and hope that Mapbox will commit into supporting it? Or should we rather wait until Mapbox officially commits into supporting flutter?

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.

[JMNewsome]

@AAverin

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?

[AAverin]

@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?
In terms of time commitment, for me it will heavily depend on how well my project will perform after release and how much time I will have on my hands to spend on it. Problem is I can't release due to the bug in current implementation on iOS: #703

[AAverin]

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.
So now I am on the crossroads – adopt fleaflet and forget about vectors and 3D or invest into v10 and find a workaround for offline side-loading of map packages.

[JMNewsome]

@AAverin

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

[felix-ht]

@AAverin should we not just add V10 here? The API should not be that different right?

[AAverin]

@felix-ht We could try to have a separate branch or tag and keep it in this repo.
Still, as far as I understood, SDK were completely re-written and many things most likely changed. So our separate tag or branch would be a parallel implementation of same features differently and using another SDK in native layer.

[srmncnk]

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.

[tobrun]

The API should not be that different right?

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!).

in Mapbox and give us some kind of clarity on next steps for Mapbox on Flutter?

No definitive answer yet atm but will be able to speak about this in upcoming weeks.