Porting to Thunkable

Hello Community,
at the beginning of my first Topic, I introduce myself briefly: I deal with It for educational and artistic projects in the non-profit sector.

We are evaluating some software products including Thunkable: our need is to evaluate the best practices with which the source codes can be provided from the external files to the different software products: for us, evaluating means both finding the technical solution and listening carefully to the opinion of the Community of each individual product.

Our specific case is afflicted by the need to recover impressive libraries in which the definitions of user interfaces of our applications are stored.

Our goal would be to automatically convert them to the Thunkable source code, thus limiting ourselves to rewriting the code associated with the events of the user interface components.

Our ideal would be:

  1. receive from the Community of Thunkable the everlasting “Hello World” in external format and instructions on how to automate (if possible) the upload to Thunkable;
    alternatively, there would be sufficient instructions on how to manually load “Hello World” on Thunkable always starting from an external file and on how to automate (if possible) the upload to Thunkable;
  2. receive from the Thunkable Community an example of source code on how to define the components of user interfaces: a typical example could be a Form with a Label, a Textbox and a CommandButton.

We thank you in advance and congratulate you for choosing to receive from the Thunkable Community! :slight_smile:

Hi @miaudit, you’re very welcome to the Thunkable community! :smiley:

I’m not 100% sure what your asking, but Thunkable doesn’t have any facility to upload external code to the platform. Are your existing apps developed for Android or iOS? Can you tell us a bit more about the software stack that your organisation currently uses?

In terms of streamlining your development process, you could create a template project, with the colours and images for your organization, and then share this as a starter template for each new app you build.

To learn how to get started with different component in your app, please take a look at some of the many great tutorials on YouTube:

If you have any follow up questions, please let us know here.

Thank you, Domhnall! :slight_smile:
Our prototype was developed to create source code for mobile app with B4X, B4I and desktop app with B4J

The goal is to allow artists and educators to assemble, with a desktop app, a set of multimedia materials and make it navigable on smartphones and tablets.
There is therefore no concept of a reusable template but rather a concept of pattern with which the user experience is described.

Our current software selection is underway to evaluate other software products to which to export source code written in the languages ​​used by these software products. We need to identify the best performing and complete software product to guarantee artists and educators the possibility to create complex sets of multimedia materials to navigate. The goal is to achieve a fluid and at the same time flexible user experience.

The choice to generate the source code of the app - rather than read and interpret at run-time the libraries containing the sets of multimedia materials - is caused by considerations regarding the performance and limits placed on the Store.

We thank you again and wish you a great success!