This may not be a bug, but it is a little annoying.
1. When I select multiple objects, I am unable to hold in Shift and click+drag the selection tool to deselect the objects I don't need. I have to click on the individual objects. This technique is time consuming and very inaccurate. It would be a huge timesaver and userfriendly to just select multiple objects with the click+drag, and using the Shift key to deslect multiple objects at once.
2. Expanding strokes. Apologies for comparing this to another design software. Expanding strokes in Adobe Illustrator is way easier. I can simply select all objects on the paste board, and expand the strokes, and only the objects that had strokes will have their strokes expanded. However, in Affinity Designer, even the objects that didn't have strokes somehow gets invisible expanded strokes, which creates unnecessary nodes, uses extra computer resources and causes more unnecessary time consuming effort. I have to go to each "unstroked" object and first delete all those invisible expanded strokes. This leaves me with less room for creativity and makes me less motivated to use Designer, because I know that is the struggle I'll have to go through.
3. Aligning objects. I'm pretty sure this is a bug. In the beginning, I was able to select my objects and then select the option of how I want to align them, such as "first selected," etc. When I select my object, those options are grayed out. Currently, I have to first apply my alignment, then the options become available. It's not working properly. Can you also perhaps create a shortcut for "key object" so that the child objects will align to the parent object?
4. For some reason Designer starts to lag when a single object has a lot of nodes. I'm used to using as little nodes as possible, but sometimes a complex object involves plenty nodes. In this case, the program gets laggy. I'm running a SSD drive, with 12Gb RAM, GeforceGT 640m 2GB, and i5 processor. Illustrator runs very smoothely on my computer, so not sure why Designer stuggles.
5. This can be a future request: "Offset path." So useful!
I look forward to your feedback and hopefully resolving these bugs in the near future.