Episode summary
As AI PCs move into the enterprise, IT teams need a clearer picture of how applications will perform across new architectures—and how today’s hardware will support tomorrow’s AI workloads. Manish Sirdeshmukh, Senior Director of Product Management for Snapdragon at Qualcomm Technologies, joins eSpeaks to discuss the Windows on Snapdragon ecosystem, including native and emulated applications, Prism emulation for legacy software, enterprise application compatibility, NPUs and on-device AI, power efficiency, and the growing developer ecosystem. He also shares what IT leaders should consider as they evaluate future PC refreshes and AI PC deployments.
About eWeek
eWeek delivers the freshest technology news, insightful analysis, buying guides, and product reviews tailored for IT professionals and technology buyers. Our focus is on exploring innovative solutions and providing comprehensive technical content. Stay ahead with eWeek as we cover the forefront of technology news and IT trends, featuring exclusive interviews and expert analysis from top innovators and thought leaders across IT, business, enterprise software, startups, and beyond.
Connect with us on social —
LinkedIn: / eweek-washington-bureau
Facebook: / eweeknews
Twitter: https://x.com/eWEEKNews
Key takeaways
- Windows on Snapdragon supports a mix of native and emulated applications, with Microsoft’s Prism providing a path for many legacy x86 applications.
- Qualcomm is working with enterprise software vendors and developers to expand native Windows on Snapdragon support.
- Snapdragon’s dedicated NPU is designed to run AI inference locally and efficiently without relying exclusively on CPU, GPU, or cloud resources.
- IT teams evaluating AI PCs should assess more than application compatibility, including reliability, battery efficiency, local AI capabilities, developer tooling, and future workload requirements.
- Qualcomm says enterprise adoption is growing across organizations of different sizes and industries, with Snapdragon PCs already deployed internally at Qualcomm and Microsoft.
Episode transcript
Corey Noles: Welcome, everyone, to eSpeaks from eWeek. I’m Corey Noles. For enterprise IT teams, application compatibility is no longer just a question of whether software opens. Organizations also need to understand how applications perform, how they interact with security and management tools, and whether today’s devices can support the AI workloads being built for tomorrow.
Joining us to discuss the evolving Windows application ecosystem is Manish Sirdeshmukh, Senior Director of Product Management for Snapdragon at Qualcomm. We’ll explore native, emulated, and hybrid applications, the growing role of on-device AI, and what IT leaders should consider when evaluating Windows on Snapdragon.
Manish, welcome to eSpeaks.
Manish Sirdeshmukh: Corey, thank you so much for having me. I’m looking forward to an exciting discussion.
Noles: Same here. To start, most people know Qualcomm first through smartphones and mobile technology. Can you walk us through Qualcomm’s journey into the PC market and what made this the right time to bring Snapdragon more deeply into Windows computing?
Sirdeshmukh: Most people know Qualcomm. We’ve been around for more than 40 years as a technology company. Our history started with communications—think 2G, 3G, 4G, and 5G. We’ve been pioneers in some of those technologies.
Over time, we built our Snapdragon application processors. We started with smartphones and Android phones. I remember working on one of the first Android smartphones with Qualcomm, so it goes a long way back.
Since then, we’ve evolved into multiple business units. With Snapdragon PCs, it has been a little over two years since our first device launch, and it’s been very successful. We’ll talk today about how that ecosystem has evolved.
Why Performance and Power Efficiency Matter for Enterprise PCs
Noles: That’s awesome. Across PCs, data centers, and edge devices, we’re seeing much more emphasis on combining performance with power efficiency. What’s driving that shift, and how is it changing what enterprise IT leaders expect from endpoint hardware?
Sirdeshmukh: That’s a great and very deep question. In my opinion, IT decision-makers have traditionally thought about infrastructure in a certain way, but the mindset is changing with AI.
We’re coming out of the COVID health crisis, and now we’re facing new challenges around energy and compute. IT decision-makers have to think about all of those factors and build their device infrastructure for the future.
Let’s break down what I mean by the compute challenge. When people think about AI compute today, they tend to think about data centers and primarily GPUs. But from an IT decision-maker’s standpoint, you also have to think about inferencing. Once you deploy AI into your infrastructure, you need to use it for your specific use cases, and that happens through inference.
You can’t simply buy unlimited GPUs, so you have to look at the compute capabilities already available across devices. Every employee has a smartphone, and organizations have PCs throughout the enterprise. The way Qualcomm looks at it is that any connected device can provide computational capability.
We think about addressing that compute challenge by enabling AI inference points across employees’ devices.
The second challenge is energy. AI workloads in data centers translate into significant power consumption. By distributing workloads across multiple devices, you can make that infrastructure much more efficient.
Snapdragon has a long history of efficient hardware architecture. So an IT decision-maker has to think about AI as part of the future: How do I make the best use of compute, and how do I save energy? Those are important shifts.
Noles: I agree.
Sirdeshmukh: And to extend that point, Snapdragon has efficiency built into its architecture. Unlike x86, which is used in most PCs today and is based on a complex instruction set computing architecture, Qualcomm uses a RISC-based architecture—reduced instruction set computing.
By its nature, that can operate very efficiently. Snapdragon PCs are designed to run efficiently, especially when you think about future AI workloads running locally.
We also have specialized hardware within Snapdragon for AI. Traditionally, PC processors have a CPU, or central processing unit, and a GPU, or graphics processing unit. Today, many AI inference workloads run on the GPU, but the GPU wasn’t specifically designed for AI.
With Snapdragon, we also have an NPU, or neural processing unit, which is designed to run machine-learning workloads and neural-network operations.
When IT decision-makers think about the future and about efficient compute hardware, Snapdragon is already designed with those needs in mind.
What NPUs Bring to AI PCs
Noles: I think it’s really interesting that you bring up NPUs because we’re seeing them more and more. Can you explain the value of the NPU and what it does differently?
Sirdeshmukh: Absolutely. I mentioned compute and energy efficiency together. The NPU is a very AI-centric processor designed specifically to run neural workloads.
If you have a model running on an NPU, it can operate very efficiently and quickly. There are KPIs such as tokens per second, which essentially measures how quickly an AI model can run, and time to first token, which measures how quickly the AI begins responding. Accuracy is another important measure.
We’ve looked across those KPIs, and we believe the NPU is the right approach.
Another way to think about it is that, for an IT decision-maker, AI agents will increasingly run in the background all the time. Security is a good example. We’re seeing more security application providers use the NPU because they want their software running continuously and efficiently in the background without interfering with foreground processes using the CPU or GPU.
Snapdragon’s architecture, with a dedicated NPU for AI workloads, makes it much more future-ready for what IT decision-makers need.
IT decision-makers also face another question: How do I actually use AI? A lot of companies have identified AI use cases today, but those use cases are still evolving. Every six months, I see something new and think, “I didn’t know AI could do that.”
Another issue I consistently hear about is the cost and availability of cloud AI tokens. With Snapdragon and an NPU, more workloads can run locally, which can reduce cloud costs while operating efficiently in the background without negatively affecting the employee experience.
So, in my opinion, Snapdragon is a strong approach.
Where Windows on Snapdragon App Compatibility Stands Today
Noles: That’s great. Application compatibility is often a major concern when an IT organization starts thinking about a new compute platform. Where does the Windows on Snapdragon application ecosystem stand today, particularly for enterprises moving from traditional x86-based environments?
Sirdeshmukh: Bringing a new architecture into the Windows ecosystem wasn’t going to be easy, but we’ve worked very hard over the past several years. I think we’re now at a point where consumer application compatibility is no longer a major issue. You buy a Snapdragon PC—and I know you have one, Corey—
Noles: I do, and it hasn’t been an issue for me.
Sirdeshmukh: Exactly. You can install applications and games, and they generally work out of the box. We’ve changed a lot of the perception around that over the past couple of years. When we initially launched, a lot of people had concerns. That’s much less of an issue today.
When you think about enterprises and IT decision-makers, application compatibility generally falls into three buckets.
The first is popular consumer applications that employees want to use. As I mentioned, we feel very good about that area.
The second is popular IT applications or applications that are specific to a particular company.
The third is legacy applications—perhaps homegrown applications or software an organization has been using for a decade or longer.
For IT applications, we’ve done a lot of work over the past couple of years. We started by interviewing hundreds of IT decision-makers and asking which applications were most important for us to support.
We’ve worked directly with application vendors to make sure their software is functionally compatible. We’ve also helped vendors port their applications natively to Windows on Snapdragon. If an application has dependencies such as kernel-mode drivers, for example, we work with the vendor to resolve those dependencies.
Some companies have gone even further. ESET, for example, is an IT security provider that has integrated AI capabilities with the Snapdragon NPU.
We continuously engage with IT application vendors, and I’m proud to say that today we support the majority of popular IT applications. Security is a great example, and we continue to expand that coverage.
The third category is legacy applications. That’s where it’s important for us to work with enterprises to ensure their workloads run on Snapdragon PCs.
It may sound difficult if you have an application you’ve relied on for many years that wasn’t designed for this architecture, but Microsoft and Qualcomm have worked together on Prism emulation. Essentially, an application built for x86 can run on Windows on Snapdragon through emulation.
I’ve even seen some applications running in emulation on Snapdragon perform faster than they do on certain x86 systems because our CPU is very fast.
So across those three buckets, we feel comfortable. Consumer applications shouldn’t be a major concern. We have strong coverage for IT applications, and we maintain application compatibility information at Works on WOA. For legacy applications, Prism provides a solid path for running them out of the box. And if customers do encounter issues, we have support and field application engineering teams that can help resolve them.
Noles: Excellent. Native, emulated, and hybrid applications can all be part of a modern Windows environment. How should IT teams think about the differences between those approaches when evaluating performance, efficiency, reliability, and the overall user experience?
Sirdeshmukh: A lot of IT decision-makers have dashboards that track these things. At Qualcomm, for example—and also at Microsoft and other companies that have adopted Snapdragon—I’ve reviewed dashboards comparing Snapdragon with equivalent x86 platforms.
The first question is whether the user experience for a given application is acceptable. That becomes pretty obvious through testing.
IT decision-makers also track things like the number of crashes and hangs over a certain number of users and months of usage. Based on what we’ve observed, Snapdragon has performed very well across those measures.
So whether an application is emulated or native isn’t necessarily the most important question. What matters is: Is the application usable? Does it crash? Does it hang? If it provides a good experience and operates reliably, then you’ve achieved what you need.
That’s not to say native applications aren’t important—they’re extremely important, and we’ve been doing a lot of work with developers on native support.
The broader industry is also shifting toward native applications. Other computing platforms introduced emulation several years ago and have increasingly moved applications toward native architectures. Windows on Snapdragon is seeing that same progression.
So ultimately, IT teams should focus on the application KPIs and the actual user experience rather than worrying only about whether an application is emulated or native.
Noles: That seems like a significant undertaking. The success of any platform depends on its software ecosystem, and you’ve talked about working with Microsoft and other developers. What about independent software developers and hardware partners? Are you also working to make it easier for them to build and optimize applications for Windows on Snapdragon?
Sirdeshmukh: Yes. One of the interesting things for us with Snapdragon PCs is that, until now, many of the platforms we worked on—smartphones, XR, automotive—were primarily consumption platforms.
The PC is also a development platform.
That means we not only have to ensure that existing Windows applications run on Snapdragon, but also that the tools developers need to build software run on Snapdragon.
Microsoft has been an amazing partner. We identified the software toolchains that need to run across our platform and support application development, and we’ve worked with Microsoft to enable those.
The majority of those toolchains are from Microsoft, but there are also many open-source projects that we continue to contribute to so they support Snapdragon as well.
It has taken a lot of work, and that work continues. AI readiness is another part of that ongoing challenge.
Native vs. emulated apps on Windows on Snapdragon
Noles: It is, and I think it’s going to be for a while. For an IT leader evaluating Snapdragon today, what does real-world adoption look like? Can you share an example of an enterprise that has deployed a significant number of Snapdragon-based PCs?
Sirdeshmukh: For confidentiality reasons, I can’t disclose many customer names. But I can talk about Qualcomm as our own “customer zero.”
At Qualcomm, we have more than 35,000 devices deployed.
Noles: That’s fair.
Sirdeshmukh: Microsoft has more than 45,000 devices. Across our dashboards, we consistently see fewer hangs and freezes with Snapdragon, along with significantly greater efficiency and longer battery life for employees.
That has been an important success story for us.
In just the last 12 months, we’ve sold to more than 25,000 unique customers in the commercial and enterprise segments. That gives you an idea of the volume and pace of adoption.
Those customers range from small and midsize organizations to large enterprises, and they span industries such as financial services, industrial organizations, education, and retail across global markets.
We continue to highlight some of those customer stories on our portal. One example involves an Australian education organization using Snapdragon PCs across its employee base. According to that case study, the organization saw a significant reduction in device-related issues.
When people hear Windows on Snapdragon, they may initially think, “This is new, so it must not be stable enough.” In our experience, we’ve seen the opposite. It has proven to be stable, efficient, and future-ready because of the AI processing capabilities and the NPU we discussed earlier.
What IT teams should evaluate before an AI PC refresh
Noles: Absolutely. I’m glad you mentioned PCs in the workplace, because as organizations begin planning their next PC refresh or an AI PC deployment, what should they test during the evaluation process? Which signals can help determine whether a platform is ready both for their current application environment and for the workloads coming around the corner?
Sirdeshmukh: That’s another deep question.
Today, IT decision-makers often start with, “These are the applications my employees need. Do they run?” That’s a great place to start, but I would challenge organizations to look beyond that.
You need to think about all the factors we’ve discussed. AI is here, and it’s evolving very rapidly. How do you expect your AI use cases to evolve over time?
No IT decision-maker can perfectly predict the future, but what I can tell you is that the future of AI is hybrid. The cloud alone isn’t going to be enough. Organizations continue to face constraints around tokens and cloud resources, so inference at the edge is going to be very important.
IT decision-makers should ask how they’re preparing for that and whether they’re purchasing hardware with local AI capabilities that won’t disrupt other processes.
As we discussed, an NPU can run AI workloads in the background without interfering with foreground workloads on the CPU and GPU, and it can do so very efficiently. That’s another factor organizations need to consider.
They should also think about the tools and infrastructure employees need beyond the PC itself and whether those run on the platform.
For example, we recently announced a partnership with Hugging Face. Many AI developers today begin with a model hub such as Hugging Face and start experimenting from there.
Noles: That’s where I started.
Sirdeshmukh: Exactly. Partnerships like that, and the broader readiness Snapdragon offers for future development, are important for IT decision-makers.
It’s about thinking not only about today but also about tomorrow, and taking a more holistic view: Am I solving the company’s future challenges? Do I have enough compute? Am I making use of compute everywhere it’s available across my employee base? Am I running those workloads efficiently? And am I able to unlock future use cases?
Noles: Excellent. Manish, thank you so much for joining us today. It’s been really interesting.
Sirdeshmukh: Corey, thank you. Thank you again.
Where to learn more about Windows on Snapdragon
Noles: Before we let you go, where can people learn more about Snapdragon, Windows on Snapdragon, and Qualcomm’s work with the application developer ecosystem?
Sirdeshmukh: There are a couple of websites. One is Works on WOA, which provides a community-driven list of applications.
If you’re still unsure whether a particular application runs on Snapdragon, you can search for it there. The list continues to grow tremendously. And even if an application isn’t listed, that doesn’t necessarily mean it won’t run.
You can also reach out to us through our forums.
And for the latest information about where to buy Snapdragon PCs or the newest Snapdragon SoCs, you can visit Qualcomm’s Snapdragon website. We also have a portal dedicated to commercial wins and customer success stories like the ones we discussed earlier.
Noles: Excellent. Thanks again, Manish. I really appreciate it.
For more conversations with technology leaders, visit eWeek.com. Be sure to like this episode, subscribe to the channel, and follow eWeek so you don’t miss what’s next.
I’m Corey Noles. Thanks for watching. We’ll see you next time on eSpeaks.
Sirdeshmukh: Thank you, Corey.


