If you are experimenting with Compose UI, you are likely to run into some problems. When you do:
- Check to see if there is a bug report for it
- If there is none, file a bug report with a sample app that reproduces the problem
Far too many issues filed on Google’s issue tracker lack that sort of sample app. While the Compose team does an exemplary job with such issues, it still slows their response time.
There is a good chance that Google is going to consider the May 5 beta06 to be the last beta release, with the final 1.0.0 version shipping during Google I|O. Any bugs that we find and report now would then get addressed in 1.0.x patch releases or perhaps a 1.1 alpha. However, the more details that we can provide about the bug, the more likely it is that Google can fix the bug faster.
Conversely, not providing a project that reproduces the error – or at the very least the source of a composable – means that the Compose team will need to create their own project, and they may have difficulty reproducing your problem.
In other words, the easiest way for Google to help you (by fixing bugs) is for you to help Google (by providing clear ways to reproduce the bugs).