Skip to main content

Note to Microsoft: Focus on Software, not tablets

iPad 2 was announced yesterday and the business and technology world (and mainstream media who bends over backwards for Steve Jobs) stopped and gazed at the double rainbow that is Apple.


I responded there but I thought I would take the opportunity to drill down a bit further.

First, Microsoft should stop trying to be a hardware maker. Their expertise is in software - so they should attempt to provide the BEST applications available in the App Store, even out-doing Apple. Microsoft's forays into hardware with the exception of the xBox have been fairly laughable - not many people recommend their webcams or mice without offering just as good alternatives.

Imagine what would happen if Microsoft actually GAVE businesses a reason to buy iPads or other tablets? Because Microsoft felt that their focus should be on the software - the BUSINESS software.

Where is the MS CRM iPAD client ? That could be Microsoft's killer intro into this marketplace. If they did it right, they could crush Salesforce. Oh, I know, CRM is a web-based product - but it has a terrible mobile interface. Why? Because it thinks it is still in the Windows desktop world.

Apple rebuilt iWorks for the iPad to try and show it as a great "office" tool - Microsoft should take Office and show why Office is the king of Office tools. Excel defined the office spreadsheet - should Apple's Numbers define the mobile spreadsheet?

Microsoft has to realize that the days of their owning the desktop hardware due to licensing is over. Projects like WinPhone 7, Kin and possibly moving to tablets should be treated for what they are - hobbies, much like the AppleTV was. Build the best software for the devices and people will use them (provided you don't kill them with licensing).

Microsoft's greatest strength (and profits) are in tools like Office, SharePoint and others. Their developers rock at this.

Jobs had it right in that Apple's strength is that they have always tried to be the cross-roads between Technology and the Liberal Arts. Microsoft has never been that - they make business software. Period.

So Microsoft should get their own developers making the best damn business software for the platforms they want to support. If they don't want to support the devices that are becoming more popular, then it's a losing business and they should realize they are eroding their customer base.

Consider the Server Tools market, That's a battle with Linux and Unix - and while it's a tough one, it's one that Microsoft currently does arguably well. The majority of small to mid-sized businesses run on a Microsoft back end.

The desktop? I think even the biggest Linux proponents would just as soon say "take it" - the new battle is on the mobile devices. But the one thing we've seen is that what matters on these devices are the "apps".

Want an instant way in here? Find a way to build "Lightswitch" apps for these next generation mobile devices ON the devices themselves. (focus on getting that trademark from someone where you can bully them). Corporate developers would fall over themselves if they could build it - and think of how cool it would be to be able to "build" the application on the device itself. (as long as Apple or other device makers allow you to do this, of course - but there's the in).

If Microsoft wants to keep relevant, they should focus on their strengths, not their weaknesses. This being my last year as a Microsoft MVP, I really wish I had gone to the MVP summit to promote this attitude.

They have started a little bit - the latest contest is to build great HTML5 applications. Great - we already know that Silverlight is not the end game for web-based applications.

And another thing, Microsoft - really?!? "App Store" is a generic term - much like "Windows"? Grow up. They beat you to it - you should have trademarked "Tablet" when you had the chance.

Comments

foo said…
Don't kid yourself, Andrew. Going to the summit would not have enabled you to share a message with anyone at Microsoft. After two summits, I have to admit that MS invites MVPs to Redmond to tell, not to listen.
Andrew MacNeill said…
Good point.

I agree that those attending the summit are there to be spoken to. However, I do believe (or like to believe in my little rose-colored world) that the teams at Microsoft would like to do a little more in these areas. I can't see an MS tablet cutting it.

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...