Without the possibility of importing AIA projects on ThunkableX it becomes impossible to reconstruct complex projects, you risk losing important projects.
Hey @Labirinto_Ambientale - good news, Thunkable ✕ now supports importing keystore files from Classic. This means that you can rebuild your project, upload it as an update to Google Play and you get iOS compatibility thrown in for free too!
this means that the previous android project built with ionicframework can be continued using thunkable x by importing my keystore and changing the package name. Right? @domhnallohanlon
I’ve never tried this with an Ionic project actually, but I would imagine that as long as you the original keystore file and accompanying password then you should be ok?
Is there any way you can test this on a simple app or demo project first - just to verify?
As long as you Thunkable X project hasn’t been published there won’t be any hassle with uploading the keystore anyway.
This is really saddening. Being with Thunkable Classic, right from it’s Inception, has taught me so many things, and transformed my view on App development. When Thunkable X came along, I really wasn’t able to get myself to like it cause it had so many shortcomings and wasn’t simply as friendly as the original. I remember being genuinely worried when the devs started branding Thunkable X and advertising it with premium plans. There was a small talk back then about whether Thunkable classic was retiring, but the devs assured that they were only simply stopping support. I knew things were going to go downhill for Thunkable Classic and since then stopped using Thunkable entirely, for the fear of my projects being obselete one day. Now that that day has come, it’s really saddening.
All the best for the future! That’s probably all I can say.
This is great to hear - hopefully you have a set of transferrable skills that you can use now to create any apps you want to.
x.thunkable.com was initially launched as ios.thunkable.com back in 2017. There have been a lot of improvements and enhancements since then.
When was the last time you used Thunkable X?
Can you be a bit more specific about what you want to do in your app and why you can’t do this in Thunkable X?
As I’ve mentioned already in my other posts, I’d be happy to walk you thought the conversion process from Classic to X. Let me know if you want to hop on a call and we can discuss in person!
Hi, Will Thunkable X be adding Extensions soon ? Im busy working on an App that needs TCPIP comms and Im busy building a Graphing Extension on App Inventor but I need the app to generate both Android and iOS so I was planning on switching to Thinkable X but if Extensions are the thing of the past then I will have to stick with APP Inventor and wait till their iOS stack is ready.
I am sure extensions are “possible” but realistically Thunkable X should provide just about everything we need for making cool apps as there are many features in the works that will catch up or even surpass builders with the likes of Thunkable Classics. I don’t see the real urgency for extensions, but I wouldn’t rule it out! I’m not sure if Thunkable X uses a cross platform language but if they did then extensions would be less difficult.
If you are having issues with Thunkable X please do ask the community, check out Thunkable Docs or browse YouTube for fantastic videos. Videos from the likes of Thunkable X Tutorials and the Thunkable X Team.
Again if you are stuck, don’t be afraid to ask any questions in the community. The people here are extremely helpful and you are bound to get an answer
The AI you have mentioned is not compatible right now.
So the only choice is Kodular?
Are there any plans to move to MIT App Inventor?
Please, I need an official answer because there is a lot of work to convert my apps to be compatible with Kodular or MIT App Inventor and time is passing.
MIT App Inventor has the limitation of a rather primitive canvas support (resolution is poor) and does not support AdMob.
It looks like you should not really expect an official answer; it has been weeks since I asked the status of the API 28 compiler bug to be fixed, and I am still waiting.
