the launch of thunkable X was recent months ago. Since then I got a feeling for the use of the two platforms X and classic.
First learning is, that for high fidelity programming, which is absolutely possible in thunkable , it needs the use of both platforms. The design concepts of Google and Apple are so different and you even cannot say which is better.
How can this be congruent with the cross platform strategy?
The solution could be introducing components into thunkable X, which are iOS only.
From the beginners point of view, there is thunkable X and it can do cross platform - fine .
From the power thunkers view, she or he can use thunkable X plus these iOS-only-components for iOS devices and thunkable classic with community aix-file extensions for android - super awesome .
I assume, that the development of iOS components is much easier and therefor faster, when the @thunkable team wont have to make this component functional for android as well.
The Headline for potential users of thunkable would be:
“Start crossplatform and if you need more special functionality for iOS, you can use our iOS-only-components in your thunkable X project, or you start a parallel thunkable classic project and can use rich extensions from the community.”
Do you get my arguments? Am I wrong in this argumentation?
Let me know! cheers User81