What is new in .NET 11, and should you move from .NET 10?
A fair tour of .NET 11 and C# 15 as released on 10 November 2026, the breaking changes to read first, and a decision guide for production teams on .NET 10.
· 7 min readAs we’ve discussed before, mobile phone apps can be created for Android, iOS (iPhones etc), or both, as well as for other (less used) devices. When building...

From the archive: originally published on the Eastpoint blog on 29 December 2014. Some details reflect that time.
As we’ve discussed before, mobile phone apps can be created for Android, iOS (iPhones etc), or both, as well as for other (less used) devices.
When building an app this is a fundamental question, and a decision you will likely make early on in the project. Should I build my app for iPhone or Android?
As we’ve discussed before, mobile phone apps can be created for Android, iPhone, or both, as well as for other (less used) devices.
In the UK, both Android and iOS are popular, but slightly more people are on Android. It is understood to have overtaken iOS devices in 2012.
Maybe, although there are other factors to consider. Android is used over a huge variety of devices and brands. So in theory, that’s a huge amount of devices to test. In reality, just like with iPhone, you can chose which devices you want to make your app available to.
It doesn’t mean it can’t be used on other devices, it just means you are not marketing your app as supported/tested on all phone, just specific ones.
Obviously, if you already know your target market closely, or perhaps have a customer that has already explained that the app will be used on iPads, your decision is made for you.
Let assume you’re picking between either a purely iPhone or Android app (ie, you’re doing one or the other only). Is one cheaper to develop than the other?
You would probably expect the app development to be roughly the same. However, resources needing for testing can be different. There are a finite iPhones and iPads to test on within the Apple brand.
Android is used over a huge variety of devices and brands. So in theory, that’s a huge amount of devices to test. In reality, just like with iPhone, you chose which devices you want to make your app available to. It doesn’t mean it can’t be used on other devices, it just means you are not marketing your app as supported/tested on all phone, just specific ones.
Yes, there is. The benefits are clear – reach more people for less money. The downside is that, since the app needs to work across two platforms, there will most likely be some compromise involved.
There more about this in our previous article about hybrid apps, plus some more on Android and iOS.
While iOS and Android are the most popular systems that apps are built for, others include Blackberry and Microsoft.

A fair tour of .NET 11 and C# 15 as released on 10 November 2026, the breaking changes to read first, and a decision guide for production teams on .NET 10.
· 7 min read
As of 10 November 2026, .NET 8 and .NET 9 no longer get security fixes. What has changed, what has not, and a calm 30-day plan for software on them.
· 4 min read
How a non-technical owner can decide what comes first on a product roadmap: plain criteria, simple scoring, outcome-based thinking, and saying no with reasons.
· 6 min read