Part III:
Showing 9 or "more" free seats is basically not a relevant consideration, what difference does it make 9 or 10 bookable seats?
Now of course 9 and 30 available seats on a 50 seater is a difference, but then we would need market analysis to show those 30 seats, which is not a good idea. But we could display 10, 11, 12... or not. Where do we cut the line?
My suggestion in (2) was meant to quickly show fully booked flights - a visual differentiation, something that can be quickly spotted. In old RM there was "fully booked" entry in red, which was immediately noticeable and obvious. In the new market analysis, even an entry that would say ***0*** (with the asterisks included) in bold red would suffice as well :) as that would be a visual differentiation from other numbered entries.
The rest is copied from my reply in the other thread:
With the market analysis, we can start by grouping by flight number :)
After all, regardless if in the future there are more booking classes, they can still be grouped by flight number.
It will be in the future to decide whether to show them as the service class grouped together, or individual booking classes, but this has little to no connection/relevance to the current page layout.
I consider "grouping by flight number" a visual aspect, not a game feature.
In other words, grouping by flight numbers makes the page less cluttered and easier to understand, rather than behave in a different way game-wise.
That is the main point, even if booking classes are used, they can still be grouped by flight number. If they are not use don market analysis, service classes can still be grouped by flight numbers.
The consideration is to make the page easier to read, understand, and make quick sense of. Grouping by flight number can be a quick fix for now.
Part II:
In order to really come up with long-term solution for what the market analysis should display, it is necessary to actually understand what the fare buckets are supposed to achieve, what will be their function and how will they affect demand and bookings. Only after we specify the purpose and desired outcome, can we move into visual display of it. Questions like "will premium economy be a separate demand category" or "what advantage will using more booking classes within one service class bring to me as a player", etc. We must understand that many fare buckets / booking classes in real life deal with advance purchase, minimum stay requirements, miles redemption, some booking classes are specifically targeted for connection passengers etc. We do not have most of these considerations in AS to think of. Only after we define the purpose, execution, and outcome, will we be ready to translate it into visual display. This is not something that can be decided in one or two days. It may take some time, but by then, players need some decluttering of the market analysis page as an interim measure, the fix mentioned above could be implemented in the meantime.