


Ex-Microsoft exec gives us another perspective on failure of Windows Phone
Jul 24, 2025 am 12:17 AMFollowing Microsoft CEO’s recent admission that discontinuing Windows Phone was a misstep, a former executive from the company has shed more light on the true factors behind the operating system’s downfall.
Brandon Watson, who previously led the Windows Phone Developer Experience, has taken to Twitter to reveal what he believes was the core reason for the platform's failure. In his view, it wasn’t app shortages or hardware issues—it was the lack of carrier support that ultimately doomed Windows Phone.
In markets like the United States and parts of the EU, telecom carriers play a crucial role by bundling smartphones with compelling plans and promoting them through retail channels. Store staff and carrier websites often serve as primary decision-making touchpoints for consumers shopping for new phones.
“We were fighting an uphill battle trying to get the carriers to feature our phones with their sales people.”
Watson explained that carrier sales representatives simply didn’t prioritize Windows Phones. Any brief excitement around new Lumia devices would quickly fade as the usual promotional focus shifted back to iPhones within a week or two.
While many believe the absence of a robust app ecosystem was the main killer, Watson disagrees—though he acknowledges it played a role. He concedes that some users missed popular apps like Candy Crush or Angry Birds, and essential services like the Chase banking app weren’t available.
“I get it, there were people who had FOMO because they couldn’t play the latest version of Candy Crush or Angry Birds. The Chase banking app wasn’t available. I get it. But, again, combinatorial math makes it so that everybody is going to likely have one app that they can’t get that their friends have that allows the discussion to pivot on “there weren’t enough apps.”
Once sales staff saw customers hesitating due to missing apps, they stopped recommending Lumias altogether—steering buyers toward iPhones or Samsung Galaxy devices instead.
Another critical issue Watson highlights is less commonly discussed: Microsoft restricted external developers from using the same internal tools that its own teams used to build apps.
“I actually think the biggest problem with our developer story was that we did not allow the tools that we used internally to be used by developers externally. Therefore the app experiences diverged.”
This created a gap between first-party and third-party app quality. Third-party apps looked and felt different, lacked polish, and underperformed—making the overall user experience inconsistent. As a result, fewer people bought Lumias, which in turn discouraged developers from investing in the platform.
While this perspective offers a fresh angle on the collapse of Windows Phone, it raises questions about Microsoft’s commitment to the platform. The challenges Watson describes, while significant, seem surmountable for a company with Microsoft’s resources and expertise.
Was it really carrier apathy and internal tool restrictions—or was it a lack of long-term vision? What’s your take?
The above is the detailed content of Ex-Microsoft exec gives us another perspective on failure of Windows Phone. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

When the Windows Security Center is blank or the function is missing, you can follow the following steps to check: 1. Confirm whether the system version supports full functions, some functions of the Home Edition are limited, and the Professional Edition and above are more complete; 2. Restart the SecurityHealthService service to ensure that its startup type is set to automatic; 3. Check and uninstall third-party security software that may conflict; 4. Run the sfc/scannow and DISM commands to repair system files; 5. Try to reset or reinstall the Windows Security Center application, and contact Microsoft support if necessary.

The computer is stuck in the "Undo Changes made to the computer" interface, which is a common problem after the Windows update fails. It is usually caused by the stuck rollback process and cannot enter the system normally. 1. First of all, you should wait patiently for a long enough time, especially after restarting, it may take more than 30 minutes to complete the rollback, and observe the hard disk light to determine whether it is still running. 2. If there is no progress for a long time, you can force shut down and enter the recovery environment (WinRE) multiple times, and try to start repair or system restore. 3. After entering safe mode, you can uninstall the most recent update records through the control panel. 4. Use the command prompt to execute the bootrec command in the recovery environment to repair the boot file, or run sfc/scannow to check the system file. 5. The last method is to use the "Reset this computer" function

Encountering something went wrong 657rx can be frustrating when you log in to Microsoft Teams or Outlook. In this article on MiniTool, we will explore how to fix the Outlook/Microsoft Teams error 657rx so you can get your workflow back on track.Quick

When encountering the "RPCserverisunavailable" problem, first confirm whether it is a local service exception or a network configuration problem. 1. Check and start the RPC service to ensure that its startup type is automatic. If it cannot be started, check the event log; 2. Check the network connection and firewall settings, test the firewall to turn off the firewall, check DNS resolution and network connectivity; 3. Run the sfc/scannow and DISM commands to repair the system files; 4. Check the group policy and domain controller status in the domain environment, and contact the IT department to assist in the processing. Gradually check it in sequence to locate and solve the problem.

When you encounter the "DefaultGatewayisNotAvailable" prompt, it means that the computer cannot connect to the router or does not obtain the network address correctly. 1. First, restart the router and computer, wait for the router to fully start before trying to connect; 2. Check whether the IP address is set to automatically obtain, enter the network attribute to ensure that "Automatically obtain IP address" and "Automatically obtain DNS server address" are selected; 3. Run ipconfig/release and ipconfig/renew through the command prompt to release and re-acquire the IP address, and execute the netsh command to reset the network components if necessary; 4. Check the wireless network card driver, update or reinstall the driver to ensure that it works normally.

When encountering the "SYSTEM_SERVICE_EXCEPTION" blue screen error, you do not need to reinstall the system or replace the hardware immediately. You can follow the following steps to check: 1. Update or roll back hardware drivers such as graphics cards, especially recently updated drivers; 2. Uninstall third-party antivirus software or system tools, and use WindowsDefender or well-known brand products to replace them; 3. Run sfc/scannow and DISM commands as administrator to repair system files; 4. Check memory problems, restore the default frequency and re-plug and unplug the memory stick, and use Windows memory diagnostic tools to detect. In most cases, the driver and software problems can be solved first.

Windows 11 KB5062660 is now rolling out as an optional update for Windows 11 24H2 with a few new features, including Recall AI in Europe. This patch is available via Windows Update, but Microsoft has also posted direct download l

How to use command prompt to repair Windows 11? 1. Enter the command prompt through the recovery environment: enter the recovery environment through USB boot or three consecutive interrupts, and then select Troubleshooting > Advanced Options > Command Prompt; 2. Use DISM to repair the system image: Run DISM/Online/Cleanup-Image/CheckHealth to check for corruption, DISM/Online/Cleanup-Image/ScanHealth scanning problem, DISM/Online/Cleanup-Image/RestoreHealth to repair the problem, and specify an external source if necessary; 3. Run SF
