Niotron App Builder v4.9.6: Introducing Cross-Platform Project Import for All App Inventor Distributions

We are excited to announce the release of Niotron App Builder v4.9.6, bringing an industry-first feature to the App Inventor ecosystem: Cross-Platform Project Import. This groundbreaking update allows you to import project files (AIA) from any App Inventor distribution without any external website or tools, just import the AIA and you’re good to go, making Niotron the first platform to fully support seamless migration across various App Inventor-based environments.

Migrate Projects with Ease

Whether you’re using MIT App Inventor, Kodular, or any other App Inventor-based platform, Niotron v4.9.6 enables you to import your projects directly. With this new feature, developers can save significant time when migrating their apps to Niotron, without having to manually rebuild from scratch.

Here’s how it works:

  • Unsupported components: When a project contains components not supported by Niotron, they are automatically replaced with placeholder components, ensuring that the app’s layout structure remains intact.
  • Incompatible blocks: Blocks that are incompatible with Niotron are marked as “bad blocks,” giving developers a clear indicator of where to make adjustments in the logic.

This approach allows developers to retain much of their project’s framework while resolving compatibility issues in a targeted and efficient manner. Whether you’re working on a simple utility or a more complex app, the import process ensures you won’t lose critical work when switching platforms.

Why This Matters

For developers who want to explore Niotron’s rich feature set, this new import functionality offers a streamlined path to migrate projects from other App Inventor-based platforms. The ability to preserve layout structure and highlight problematic blocks reduces the risk of errors and minimizes the time needed for adjustments post-import.

This update also helps users avoid being stuck with one platform, giving them the freedom to explore more options. Whether you’re looking to take advantage of Niotron’s unique components, experiment with new tools, or simply move your project for better optimization, faster updates, this feature makes it easier than ever to switch platforms without losing your work.

The flexibility provided by this feature empowers developers to choose the best platform for their needs at any stage of app development, without the hassle of manual migration or starting from scratch.

We Need Your Feedback!

As with any major update, we are eager to hear from you. We encourage you to test your existing projects by importing AIA files from other App Inventor platforms and exploring how they function in Niotron.

Your feedback will be invaluable in refining this feature further and ensuring that future updates address any issues you may encounter. If you spot bugs, notice performance improvements, or have any suggestions, let us know through our feedback channels.

How to Get Started

  1. Export your project (AIA file) from your existing App Inventor platform (MIT App Inventor, Kodular, etc.).
  2. Open Niotron App Builder v4.9.6.
  3. Import your project file just as you would’ve earlier.
  4. Review any placeholder components or bad blocks and adjust your project as needed.
  5. Compile and test your app directly within Niotron.

Niotron v4.9.6 is just the beginning of our ongoing effort to make app development more accessible, streamlined, and feature-rich. We can’t wait to see how you use this new capability to build amazing apps!

Try it now, and let us know how it goes!
fixale

18 Likes

I’m telling you that I just imported an aia from kodular, it has many blocks and several designs, in short a complex app. I was surprised that now I can migrate the project to Niotron without problem, but as you mention the components that are not compatible are marked as defective in order to adjust the logic in specific parts of an app. Thanks for this great change. The only thing is that the beta companion fails when it reaches 20% the companion closes.

3 Likes

@Christian_QF Appreciate the feedback!

1 Like

Best update ever, I trust you guys… Guys of determination and perseverance…

Kudos! Kudos!! Kudos!!!

4 Likes

image

Showing this again and again and after import when change screen it does not change giving this

image

@DevXlabs This update is only available on beta now, will be released in the main version soon.

https://beta.niotron.com

3 Likes

When will it be available on the main builder?

The best of the changes, it is a great advance for Niotron.
Without a doubt, it is becoming the best platform.
We are going to test, debug and report so that the main version is released soon.
Congratulations!!

1 Like

Once it’s tested and there are no bugs. This is a huge update and we want to make sure it does not affect existing projects.

2 Likes

Please fix as soon as possible the main companion crashes when using extensions, and in beta companion closes unexpectedly when reaching 20%

The existing extensions in imported project are showing as placeholder component however, the associated blocks of those extensions are not shown as bad blocks. Do I have to import extensions and write blocks again?

It is a bug, We’ll release an update, currently do not work on the project and reimport once the update is released

1 Like

WOW… the ability to do this is incredible… Establishing the Niotron brand above any other platform, being the first to offer their users the option to migrate their projects to Niotron environments… They have truly positioned themselves above the competition. Niotron team, don’t forget that you are the best of the best.

2 Likes

Still having problem with extensions. sent you the complete aia.

1 Like

What’s wrong in the screenshot?

Card view and space and lottie component give error how to fix

What’s the error?

I suppose it refers to importing the AIA from another platform, there are the 2 components that are imported with problems. It has happened to me and in large designs it takes a long time to correct and replace each CardView and Space.

https://beta.niotron.com

Both components are imported as if they were layouts with errors.

Something I want to suggest since it also involves time, is that when selecting a component in the design it is not visually marked in the list of them, it is only identified in the component properties title, so it is not possible to know in which part of the structure it is located.

thank you very much for your work

2 Likes

Has this update been deployed to prod yet?