Android Question App must target Android 16 (API level 36) or higher

[Alex_197]

I just received an email from Google Play Console.

App must target Android 16 (API level 36) or higher



To provide users with a safe and secure experience, Google Play requires all apps to meet target API level requirements.
From Aug 30, 2026, if your target API level is not within 1 year of the latest Android release, you won't be able to update your app.


Is it safe to do it now?

When I tried to update my API in manifest I've got a message

The recommended value for android:targetSdkVersion is 35 (manifest editor). (warning #31)

 

[Duque]

With Google enforcing increasingly aggressive and time‑critical requirements (e.g., target API 36 with very short deadlines), we fully depend on B4A/B4X being updated in order to keep our apps publishable and compliant.

My question is technical and serious:

Is there any continuity plan for B4X in case Erel becomes unable to maintain the IDEs due to unforeseen circumstances?

Android is pushing deep and frequent changes, and our applications rely directly on ongoing framework support.

Are there any documented mechanisms, community strategies, or long‑term sustainability plans for the ecosystem?

Thank you for any insight.

 

[Erel]

As B4X is being developed for 16 years now (or 21 years if counting from the beginning of the beloved Basic4ppc), this question was raised a few times
At some point I had a list of the programming languages or tools that Microsoft killed since B4A 1.0 was released. There were many.

1. The framework itself is open source: https://github.com/AnywhereSoftware/B4A. This should give you some confidence. Especially with the ever-improving AIs that can help with the Java framework.
2. I hope to continue and develop B4X for many years to come.
3. I do have some plans in case something bad happens.

 

[Erel]

I've asked ChatGPT to prepare such list:

• IronRuby
• IronPython
• Axum
• TouchDevelop
• M
• Spec#
• C++ AMP
• VBScript
• Microsoft Expression Studio
• Visual Studio LightSwitch
• WebMatrix
• Visual Studio for Mac
• Azure Data Studio
• CodePlex
• Microsoft Connect
• Microsoft Script Debugger
• FxCop
• StyleCop
• Sandcastle
• XNA Game Studio
• Silverlight
• Xamarin
• Kinect for Windows SDK
• Azure Kinect SDK
• Microsoft Robotics Developer Studio
• .NET Micro Framework
• Windows Phone SDK
• Windows 10 Mobile
• HockeyApp
• Visual Studio App Center
• Azure Dev Spaces
• Azure Machine Learning Studio (classic)
• Azure Spatial Anchors
• EdgeHTML
• ChakraCore
• ASP.NET Web Pages
• ASP.NET Web Forms for modern .NET
• WCF Server for modern .NET
• Windows Workflow Foundation for modern .NET
• .NET Remoting

And it forgot .Net CF (and WPF / WinForms are also no getting too much love)

What I'm trying to say is that company size doesn't always matter.

 

[RichardN]

@Erel Your point about deceased development platforms is very true especially where Microsoft has continually failed in driving development in their chosen direction. I do however have to echo the concerns of @Duque.

There are no doubt many hobbyists here. By the same token there are also many professionals who have invested much time in their businesses and B4X. I find these days companies are very reserved when it comes to trusting a solo developer for a job, even moreso if the task is mission-critical to them. Solo developers are viewed as a possible single point of failure that could bring their business to a halt.

The world is an unpredictable place as you are only too aware in your neighbourhood. Life and world events do throw us the occasional fast ball for which we are never prepared. I am at the point where yet another Google/IOS compliance requirement will signal an end to my programming. There are however younger guys who are looking for certainty in the years ahead. I am pleased that you do not see yourself as a 'single point of failure'.