A visual programming language
and set of creativity tools
for smartphones, tablets,
and mobile browsers


First steps into Catrobat

the following lines should help you with your first steps into the Catrobat project.

10 January 2015

Assuming you already know your next steps should be:

  1. Write some programs using Pocket Code and Pocket Paint, upload your Catrobat programs, and check out our inspiration source, the Scratch project.
  2. Visit us on GitHub
    As you can see Catrobat is a very large project with a lot of sub-teams. So go ahead and look into them. Each project should have a readme file so check that out too. There should be viable information for you in it.
  3. If you want more information, visit us our Google+ Community named Catrobat. If you would like to work with us, please read on.
  4. If you want to contribute to our project, please choose one of the sub-projects, you would like to work on. Once you have chosen a project, we recommend that you checkout the project and play around with it a little.
  5. Maybe you find a bug while trying out Catrobat? Awesome. Report it via GitHub. If you can’t find a bug, doesn’t matter; seems that we have done too much the right way ;)
  6. Now is the right time to check out the Issues on GitHub. First fork the project then choose an Issue you can fix --> first write a regression test for it, and then only fix it.

    We strictly use Test-Driven Development and Clean Code (by Robert C. Martin), so first read everything you can about these development methods. Code developed in a different style will not be accepted.

  7. You have fixed an Issue and written at least one test for it? Awesome. Ask for a review via a Pull-Request in Github.
  8. It could take time some time until you hear from us.... In the meanwhile why not choose another Issue or engage in the community on Google+. Try to answer questions of visitors or pose questions yourself, if you have still have some.
  9. Your Pull-Request has been accepted? Go back to 6.
  10. There are no more Issues? Can't be! Go back to 5.