How can Microsoft cannibalize tablet market


Recommended Posts

Note: This is strategy/idea is for lower-end tablets only.

Microsoft should make a ~7 inch version of Windows Phone 8 (Windows Desktop access on small screens wouldn't make for good experience), and give it out for free to it's OEMs. They should make it at a tiny, or even at no profit whatsoever.

All the tablets would have a fixed memory space of ~32 Gb. This would increase the demand/production/consumption for 32 Gb SD card, and hence reduce its cost significantly.

Rather than producing three separate card sizes, we can produce one at a lower price. The reasoning behind the large size memory card, would be talked about later.

The screen dimension would also be very rigid. Giving developers and consumers a better experience. The same mass-production idea applies to this one too. Mass-producing one particular size (more cheaply), rather than producing several different types.

It would have it's own special app store. Microsoft would charge ~50% from the earnings of developers, and share half of it with the device manufacturers. Microsoft's software ecosystem is worth several hundred billion dollars, so we are talking about a lot of money here. Plus, Microsoft would have it's own services integrated on the device, such as Bing, Maps, Mail, SkyDrive; and would make money through that too.

OEMs would be required to give large SD cards on their devices, because their earnings would come through the usage of device. That is, the more apps the people use, more profit they will make!

Having a large number of OEMs would ensure that this form-factor is always up-to-date in terms of hardware (new devices every month!).

Their would be no price wars between OEMs, because it would have a fixed price.

This is the only way I see Microsoft and it's partners, not only competing, but destroying competitors like Kindle and Nexus. Those devices actually sell at a loss, and make money through apps.

Note: And where this: ~ has been used, it means that that particular value is not final, and has been used to just give you the basic idea.

And also, I think that WP8 interface with it's resizeable tiles is more suited to small tablets, than W8. For this form-factor we could have hybrid version, with best features from both (But no Desktop).

Microsoft's primary revenue stream, aside from Office, is operating system licenses. The only way you can sell something at a loss is if you have something else still propping up your overall profits. If they did this, they'd cut out their primary revenue stream. Marketshare regardless of how they go about it doesn't benefit them the same way it does Google.

This is the only way I see Microsoft and it's partners, not only competing, but destroying competitors like Kindle and Nexus. Those devices actually sell at a loss, and make money through apps.

I'm not really sure, but I read somewhere that Asus is making about $20 for the 8GB Nexus7 and $50 for the 16GB.

That sounds silly...the sort of strategy iOS and Android are already using, in some ways...

So are you suggesting MS should just be doing what everyone else is, or what?

Windows RT will go great on 7" tablets once they can reasonably have 32GB storage in them.

Windows Store also already makes sure MS makes money through apps. And those services will already be integrated.

I'm kind of at a loss as to what you should read first.

Note: This is strategy/idea is for lower-end tablets only.

Microsoft should make a ~7 inch version of Windows Phone 8 (Windows Desktop access on small screens wouldn't make for good experience), and give it out for free to it's OEMs. They should make it at a tiny, or even at no profit whatsoever.

All the tablets would have a fixed memory space of ~32 Gb. This would increase the demand/production/consumption for 32 Gb SD card, and hence reduce its cost significantly.

Rather than producing three separate card sizes, we can produce one at a lower price. The reasoning behind the large size memory card, would be talked about later.

The screen dimension would also be very rigid. Giving developers and consumers a better experience. The same mass-production idea applies to this one too. Mass-producing one particular size (more cheaply), rather than producing several different types.

It would have it's own special app store. Microsoft would charge ~50% from the earnings of developers, and share half of it with the device manufacturers. Microsoft's software ecosystem is worth several hundred billion dollars, so we are talking about a lot of money here. Plus, Microsoft would have it's own services integrated on the device, such as Bing, Maps, Mail, SkyDrive; and would make money through that too.

OEMs would be required to give large SD cards on their devices, because their earnings would come through the usage of device. That is, the more apps the people use, more profit they will make!

Having a large number of OEMs would ensure that this form-factor is always up-to-date in terms of hardware (new devices every month!).

Their would be no price wars between OEMs, because it would have a fixed price.

This is the only way I see Microsoft and it's partners, not only competing, but destroying competitors like Kindle and Nexus. Those devices actually sell at a loss, and make money through apps.

Note: And where this: ~ has been used, it means that that particular value is not final, and has been used to just give you the basic idea.

And also, I think that WP8 interface with it's resizeable tiles is more suited to small tablets, than W8. For this form-factor we could have hybrid version, with best features from both (But no Desktop).

Couple things.

1. No.

2. Sorry about number 1. That was rude of me. But seriously, no.

3. You've outlined a product model that requires a lot of OEMs and simultaneously gives them no reason to participate. All of their products must be exactly the same and sell at exactly the same price. What factor do they compete on, then? How do Samsung and HTC differentiate? If you're the idealistic type, you might answer with something like "quality", but that's naive and childish and doesn't actually happen.

4. You've ruled out Windows 8 because of tile customizability, despite Windows 8 having resizeable tiles already, and the fact that it wouldn't have a bunch of wasted, unused functionality (text messaging app, phone dialer, etc). Even beyond tile sizes, Windows RT is significantly more customizable than Windows Phone.

5. Your pricing scheme is also called collusion, and when done with the primary goal of eliminating competitors, is very much illegal. God help them in the EU, where two CEOs can be executed for nodding politely at each other from across the street.

This topic is now closed to further replies.
  • Posts

    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      186
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!