You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Publish benchmarks comparing performance between native iOS/Android code and Flutter, continuously updated with releases #47561
Corporate customers of Flutter want a dashboard that shows the performance comparison between Native iOS/Android code and Flutter code.
With this information, they will be able to articulate clearly the benefits of Flutter and promote Flutter within the company. Customers are happy to provide use-cases and scenarios, but wish to have an official performance benchmark dashboard coming from the Flutter team.
I think the final artifact could be a documentation with a table that compares native code with Flutter code. But the customer is more hoping for a live dashboard that gets updated frequently whenever there is a new version of Flutter in different channels on different types of devices.
This issue is assigned to @gaaclarke but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!
This issue was assigned to @gaaclarke but has had no status updates in a long time. To remove any ambiguity about whether the issue is being worked on, the assignee was removed.
From primary triage: imitation_game was in master_archive/packages but it is not maintained at the current packages repository. So I'm unsure which team will take this.
While this is probably still actionable by someone, imitation_game isn't being worked on, I'm not aware of any other plans to make this kind of comparative benchmarking happen, and I'm not sure who would own that work.
If something specific around native benchmarking comes up from customers and it could have a clear owner, we could look into it. I'm going to close this for now.
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.
Activity
jmagman commentedon Jan 17, 2020
@zoeyfan Is this a request for documentation on the website?
zoeyfan commentedon Jan 17, 2020
I think the final artifact could be a documentation with a table that compares native code with Flutter code. But the customer is more hoping for a live dashboard that gets updated frequently whenever there is a new version of Flutter in different channels on different types of devices.
39 remaining items
flutter-triage-bot commentedon Jan 20, 2024
This issue is assigned to @gaaclarke but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!
flutter-triage-bot commentedon Mar 23, 2024
This issue was assigned to @gaaclarke but has had no status updates in a long time. To remove any ambiguity about whether the issue is being worked on, the assignee was removed.
huycozy commentedon Mar 25, 2024
From primary triage: imitation_game was in
master_archive/packagesbut it is not maintained at the current packages repository. So I'm unsure which team will take this.jmagman commentedon Mar 26, 2024
While this is probably still actionable by someone, imitation_game isn't being worked on, I'm not aware of any other plans to make this kind of comparative benchmarking happen, and I'm not sure who would own that work.
If something specific around native benchmarking comes up from customers and it could have a clear owner, we could look into it. I'm going to close this for now.
github-actions commentedon Apr 10, 2024
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 -vand a minimal reproduction of the issue.