I’ve written this in emails before and on quite a few occasions but this bares repeating. Gaining visibility in this
industry is tough especially when the industry is driven by Google & Apple…
Despite years of effort most Java developers or mobile developers haven’t heard about us and it’s still an uphill
battle for awareness.
If you like our product and think we are doing something important it would be VERY helpful for us if you
can help us with these small things. Doing everything below would take 5 minutes and every bit counts!
If you are active on reddit, hackernews or any other community such as these and you think something we
wrote is worthwhile for that site we’d really appreciate a share on those sites.
If you have accounts in any of those networks we’d appreciate the help here
Facebook – like the page & share stuff you like
StackOverflow – follow our tag by hovering over codenameone and staring it
Github project – star & fork using the buttons on the top right
LinkedIn Company – Follow the company on linked in
LinkedIn group – Join the group
Codename One Academy – You can help us spread the online courses we have for Codename One using the social bar in the side of the courses/academy
Community engagement for Codename One is good but it can still be better. Ask us questions on stackoverflow.
fork our projects on github, contribute your work and submit
If you ask a proper question on stackoverflow you will get points (which are useful when you have a really hard
question), so even if it isn’t the biggest problem in the world ask…
If you see something broken report it or submit a pull request. You can just edit the Codename One sources/docs directly
on the github site. If JavaDoc isn’t clear or the developer guide was confusing just edit them directly and help the
next person coming along. The
developer guide is literally a wiki you can edit!
Let us know if you have ideas how to improve the site and engage with us. Try to use the public forums e.g.
comments, stackoverflow and discussion groups when engaging so other developers gain the benefits of
the collective knowledge.
Don’t be Timid
We got a lot of feedback over the years with ideas on how to improve engagement and we’re always open
for more even if it is critical of how we do things.
Don’t be afraid to criticize us in a public forum, if you use polite language and explain the criticism properly
it’s always helpful. Avoiding criticism doesn’t help us as we try to move forward and build a better product.
We can’t address every criticism as the community is large and we just don’t have the budget to cover
“everything” but we need to know and it might be your specific critique that pushes us to fix a specific problem.