post a picture when they have one of something they update
Is this the only way they can inform us of cool things they are working on?
BTW, low level updates (changes at the sub-routine or individual class level) are what you described with your snapshots. We are
not asking for this at all. Again: we are not asking for low level updates.
HTC is a very small company, a couple of artists, and couple of code writers, and a few administrators. All work is done in house. Big name software companys can post updates weekly because in those 7 days they have 100 people working 40 hours each to drive that. HTC may have 5 people doing the same work and to cover that same 4000 hours of work takes 20 weeks.
You seem to know a lot about software engineering. So you are saying the number of programmers has a direct relationship on their ability to perform SCM (Software Configuration Management) to the degree that they cannot spend 5 minutes a month to routinely give us a preview of what they are working on at a high level?
Example:
We have begun working on say on a Ki-100 this month. We do not need to know their test cases and SCM and QC testing practices for the K-i100. Because they can duplicate success (they have created planes before) they know how to do it accurately and thus them not being able to produce the KI-100 in this example would not be in doubt. They still have the flexibility to not do it too for business reasons. An investor gave them $10k to produce an IAR-80 first for example.
To put it another way. Are you saying they do not use standard industry programming practices (Unit Test->Environment Test->Staging->Acceptance Test phase) because of the number of resources they have, so they cannot spend a few minutes providing a high level update?