Theme (optional): Rain

Rules:

• The jam is going to be for 1½ week + 12 hours, so you can enjoy the full 1½ week in your timezone.
• During this time, you would have to make a practical tool, using your favorite engine/framework/library/language/etc.
  • This is not a "game" jam, and you are not required to make a game-related tool. Tools which solve real-life problems are encouraged.
  • Reusing existing assets or libraries is fine, but keep it reasonable.
• You are not required to follow the theme; it is there to give you some initial ideas.
• After the jam, there would be a week for voting; we encourage you to check other people's tools and rate them.
  • The "usability" criteria is for how useful having that tool is for solving its problem. A painting app which cannot save images or a video converter not supporting common formats are both probably not usable.
  • The "intuitiveness" criteria is for how easy is it to get started using the tool with little or no past experience. Having to read a thick guidebook just to get started or having to pixel-snipe certain features is not really intuitive.
  • The "neatness" criteria is about how well-organized and accessible the features of the tool are. A tilemap editor with buttons spread everywhere on the screen is not neat.
  • To give an example with screwdrivers: you want a screwdriver which has a normal head (not an alien hexagonal one), and thus usable, one which looks like and is used like a screwdriver (and not like a hammer), and thus intuitive, as well as one that isn't covered in grime and soil, and thus neat.
• You are allowed to publish updates to your tool, as long as you are bugfixing and not adding new features.
• Open-sourcing the final result is optional, but encouraged, especially if you don't have the time to continue developing it.