Some contribution opportunities, in order of diffi...

# compose-desktop

[jim]

Some contribution opportunities, in order of difficulty:
• Documentation & Tutorials - to through the docs and tutorials, following the steps in each one. Identify mistakes where things are out of date or don't align with the code or are confusing and submit fixes.
• Community Contributions - building cool stuff and posting it on twitter and reddit can help inspire other people to join the community and build cool stuff. For instance, one app that really inspired me is https://www.reddit.com/r/androiddev/comments/lgruit/my_first_compose_desktop_app/ which was built by a member of the community. You can also use this as an opportunity to learn Compose, find bugs, and occasionally fix bugs too, all at the same time. And if you build cool things and share them in open source such that people can share/reuse your code, that can help them get started. Getting people excited and building a great community is important for the success of Compose for Desktop.
• Samples - often the samples will be slightly out of date (using an older release of Compose for Desktop) or will have subtle bugs. An example that comes to mind off the top of my head is https://github.com/JetBrains/compose-jb/issues/499 but I'm sure there are many others. IIRC, in the CodeViewer example, when you click an item in the tree view on the left, only the text of the item is selected, whereas usually you want the entire line to be selected up to the edge of the pane, similar to the way channels are selected in slack. Cleaning up such bugs helps make the samples look good.
• Widgets - Widgets are usually relatively well-scoped and require less domain knowledge than core contributions. For example, CEF (https://github.com/JetBrains/compose-jb/tree/master/cef) doesn't currently work on mac osx. If you have a mac and are willing to dive into the technicals, that would be very helpful thing to solve
• Small bugs in the Compose for Desktop core. You'll need to use your judgement to find ones that look interesting and are also small enough to tackle. This requires a bit more knowledge of Compose and would be especially hard for someone who doesn't have lots of experience contributing to open source, so I'd work your way up to this point, aiming for some of the earlier bullet points first.
The most important things are to (1) actually get started contributing instead of just thinking about it and (2) remain engaged by choosing tasks that you will find personally interesting and rewarding.