Good point. I often end up dragging things in the stacking order. On the other hand, some people prefer to operate in terms of building from background to foreground.
Frankly, there are so many high-priority items in my Hype wish list that I am not all that concerned about the stacking or object naming. For me the biggest priority is loading time - where the rubber meets the road. In my situation I want the highest impact for the fastest loading time – making it into a seamless and enjoyable experience for the potential customer in order to promote sales of a premium product – so to persuade the prospect to spend 20% more for something that looks the same as a lower quality competing product. The more sophisticated, slick and seamless the presentation, the more effective it is in addressing the goal.
Admittedly, this represents the needs of only a certain segment of the userbase.
Having been a software reviewer for many years, I can say that in many cases a reviewer may be totally new to an app and will not have the time to totally explore an app. As a result, they can miss certain key issues. In such a situation, they will notice simple stuff such as object naming, while missing something really important under the hood, and their focus on such things could have an impact on sales.
This requires strategic thinking – how many seats are required to pay for the time it takes to develop one feature versus another, plus overhead. Certain features (such as a shared resource folder for multiple projects) might be important for deployment but be irrelevant to project development, and most reviewers think in terms of an individual project, which makes project development a higher priority for the vendor.