Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move minimum Android version up to v19? #9310

Closed
eseidelGoogle opened this issue Apr 10, 2017 · 10 comments
Closed

Move minimum Android version up to v19? #9310

eseidelGoogle opened this issue Apr 10, 2017 · 10 comments
Assignees
Labels
platform-android Android applications specifically

Comments

@eseidelGoogle
Copy link
Contributor

@chinmaygarde mentioned he was working on a proposal for such?

We currently support v16+, which provides compatibility with 98% of devices.

v19+ would only give us 90%:
https://developer.android.com/about/dashboards/index.html

However my understanding is it would remove a bunch of devices with bad GPU drivers which have caused us trouble in the past.

I'd like to better understand the tradeoffs.

@dbacinski
Copy link
Contributor

It is very rare to start a new project with min API 16 even for native Android development.
I am not sure what is a target audience for Flutter, but most probably only green field projects.
As Android dev I would like to finally "kill" 16-18 APIs :)

@eseidelGoogle eseidelGoogle added this to the 3: Make conferences happy milestone Apr 12, 2017
@eseidelGoogle eseidelGoogle added the platform-android Android applications specifically label Apr 12, 2017
@eseidelGoogle
Copy link
Contributor Author

We met with a customer today who is considering Flutter and currently supports all the way back to Android v14. They seemed to be willing to consider being only v16+, but v19+ would be a longer discussion. Please reach out to me if we get serious about changing this.

@chinmaygarde
Copy link
Member

Being tied to v16+ has caused some pain when developing the engine in the past. However, as the engine is stabilizing, the issues aren't coming up as often. In an ideal world, I would like to move to 19+ just so we are able narrow our focus and make better guarantees about performance and behavior. For example, we also have issues with older Android emulators (16-18) that are hard to isolate and fix. But I feel like I cannot come up with a single reason that makes it impossible for us to support 16+. Just a bunch of tiny issues that slow us down.

@vaidyanathanas
Copy link

Flutter camera plugin is supported above minisdk version 20. So how can we use camera for below 21 in flutter

@zoechi
Copy link
Contributor

zoechi commented Mar 16, 2018

@vaidyanathanas you could fork the plugin and adapt it to older SDK versions yourself or provide a PR
or hope for someone else to do it.

@vaidyanathanas
Copy link

Is it possible create or customize flutter plugin without publishing.

@zoechi
Copy link
Contributor

zoechi commented Mar 17, 2018

@vaidyanathanas sure, you can clone it to your disk and modify and add it to pubspec.yaml with a path
https://www.dartlang.org/tools/pub/dependencies#path-packages

@tofutim
Copy link

tofutim commented Mar 31, 2018

@vaidyanathanas just remember, sharing is caring!

@eseidelGoogle
Copy link
Contributor Author

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 25, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
platform-android Android applications specifically
Projects
None yet
Development

No branches or pull requests

6 participants