Don't focus on making it bug-free. That will never happen. Structure things so that bugs don't have big impacts. Auto-save, local backups are a good band-aid, better if you can rearrange things so all the data isn't in one "basket". Think about failures outside of your control -- power outages, network outages, etc. Will people lose work? Don't make it hard to do destructive features, but instead make it easy to undo them. Often it's useful to store data in a redundant way -- sort of caching things to make things faster or easier, and these can be used to restore data when it's needed. Think very carefully about which data can be recreated and which is primary, and treat them differently.
People are going to complain about everything. If they don't complain, that means they are not actually using it. That's ok. Listen to them, listen for patterns, take them seriously but don't take it personally.
It sounds like you're doing the right thing -- when you find a bug, fix it and don't just put in a quick workaround, and learn from it and try to avoid that from happening again.
People are going to complain about everything. If they don't complain, that means they are not actually using it. That's ok. Listen to them, listen for patterns, take them seriously but don't take it personally.
It sounds like you're doing the right thing -- when you find a bug, fix it and don't just put in a quick workaround, and learn from it and try to avoid that from happening again.