Back up regularly!
Neither the hardware nor software in your computer is perfect. Computers fail and software can crash.
Back up your projects daily to protect yourself from losing work. Saving projects to single files (.capx files) is a convenient way to back up projects.
You should also maintain
off-site backups. If all your backups are in the same computer or saved to disks all in the same building, catastrophic events like fire, floods, theft or simultaneous hardware failure can cause you to lose
all your work and backups together. A simple way to have off-site backups is to use
Dropbox, which is free up to 2 GB of storage. Copying your project to a Dropbox folder uploads it to the Dropbox server, where you can then access it from any computer with your Dropbox username and password. This is very easy and straightforward and is extremely important to ensure your work is safe.
This advice is
not specific to Construct 2. It is vital to adopt this practice for any work on a computer which is important to you.
Do not wait until you've lost work before starting to do this. People lose work regularly from having poor backup practices. Don't be one of them!
Managing projects
If you are working in a team, you will probably find source-control software like SVN very useful for managing a folder-based project. It can merge changes and highlight the changes each person has made. There is also a history of all changes available and rollbacks can be made at any time. Construct 2 saves project data in XML format so it is well suited to this type of management.
Working as an individual
If you are working on a project by yourself, it is probably easiest to use single-file projects (.capx files). If the project gets large over time, you may notice Construct 2 spends more time saving and loading projects with
Decompressing CAPX... or
Compressing CAPX... in the status bar. At this point it is probably useful to convert to a folder project which skips these steps and will make saving and loading faster.
Test on multiple browsers and devices
It is highly recommended to test your game works as intended in a range of different browsers. While HTML5 is a standard which in theory is implemented the same by all browsers, in practice there are variations between browsers (e.g. in performance, features, text rendering, etc). You should install a range of browsers and test with them all (using the
Preview browser property) to ensure your game will work well for everyone.
You should also regularly test on the target devices if you intend for your game to be played on mobiles or tablets. These devices often have more limited browsers and weaker hardware.
You must not assume a game that runs well on your desktop PC will also run well on a mobile device. To avoid surprises always test on the target device from the start. For more information on conveniently testing on other devices, see the tutorial
How to preview on a local network.
Support touchscreen devices
Many users now browse the web with touchscreen devices with no mouse or keyboard. If at all possible, you should design your game to also support touchscreen devices with on-screen touch controls. For more information, see the tutorial on
touch controls.