I do plan on recognising and supporting drawers in a future release. I'll take a look at how Orgzly presents these to the user as part of planning how I intend this to work. Support the PROPERTIES drawer will enable a number of additional features so I am keen to do this relatively soon.
I was only targeting folding/unfolding i.e. visibility cycling. If you support PROPERTIES you have to deal with visibility cycling; and it should not be difficult to include all drawers, and not only PROPERTIES.
My main concern was with compatibility with emacs and orgzly. You can have big drawers in file that are folded in emacs and orgzly, and appear as garbage in beorg.
I hope you can consider it while implementing PROPERTIES.
As someone that has a PROPERTIES drawer added to every item, I can't wait to see this implemented!
Thanks for the clarification on this request. I guess there are a number of things to implement:
1. Getting beorg to parse drawers and then update/read the property drawer programatically
2. In the outliner there should be a way of expanding/collapsing drawers
3. When HTML is rendered (for use when showing notes in the item editor and for document export) drawers should be hidden as it doesn't make sense to show them here