Stage-based implementation:

Although the above solutions were presented in twos it is suggested that the console messenger function should be implemented onto mobile first.  This is since it is expected to be the primary feature that appeals to the community the most and is most able to meet the objective of enhancing the community experience and socialisation within it.  However further to this, a staged based approach will ensure that greater focus is paid to developing this function.  This will reduce the cost and time it takes to develop and ensure that it can be quickly delivered to the market as soon as a critical mass of mobile Internet users has been reached. 

However this is also strategic in revenue generation terms since the CCTV function would also undergo development, but under a longer time frame as required.  Since a one off cost represents the most favourable business model the console messenger system could be released first and attract this charge.  Yet when the CCTV function is released this can also be charged for, as could each additional function that is subsequently developed and launched.  This means that in the future each additional mobile feature can be cost on a project-by-project basis and ensure that each are covered financially.  Indeed some services will cost more than others to produce and this method facilitates the development of higher costing products, while maintaining a standardised price considered acceptable to the end user.  This is sensible to ensure profitability in developing these functions, while being consistent in how they are charged for.  Many users said they would pay £5 for a function that they valued and it is believed this would be the case if one or all functions were added.  If all 3 were present users are unlikely to consider this still represents good value if it costs £10.  This also gives Habbo long-term scope to develop add-on products or entirely separate propositions that can ‘plug in’ to the existing console system.  Indeed it would enable to development of a “mobile catalogue” where numerous features could be added and billed for individually and gives the end user the freedom to choose the functionalities that are specifically relevant to them.  In a large community choosing the most popular product is difficult and this makes the situation flexible to the needs of the community and Sulake.

Indeed Chat function should be looked at after the first two functions have been produced and effectively launched on mobile, since the market environment is likely to favour more complex chat at this point.