Saad Hashmi would like Microsoft to move to a six monthly release schedule on Windows Phone. He details the arguments over on Windows Phone Daily, pointing out that a faster turnover could result in more devices on sale throughout the year, keep Windows Phone in the front of the network stores and in front of customers, and would mimic the saturation strategy that he believes has driven Android to the dominant role in the smartphone market.

Hasmi writes:

Traditionally, the more significant software revisions for Windows Phone have launched alongside new hardware during Winter, while one incrementally important update is released to existing devices in the Spring. Yet with the exception of a peculiar 2011, new Windows Phone flagships are rarely ever released (or marketed) after the Christmas lights are taken down. In other words, it feels like Microsoft has been putting in about three months of real effort each year while manufacturers like Nokia pick up the slack.

To remedy the Spring lull and keep the influential tech world engaged, I believe that Microsoft needs to move to a biannual release schedule for Windows Phone updates. More importantly, they really need to make that Spring update count by rapidly adding support for new hardware specifications to compete with Android. We all know how quickly manufacturers can churn out Android flagships, and Microsoft needs to enable them to do something similar with Windows Phone.

It would be a significant engineering challenge, and would require buy-in from the manufacturers, the networks, and the developers working on the OS to have something significant ready every six months. There would also need to be a huge amount of compatibility testing to ensure third party apps would continue to be accessible. At the moment it's not clear if the structures are in place to allow a switch to a rapid iterative process for Windows Phone.

You can read the full editorial over on Windows Phone Daily. What do you make of the argument?