That is an important issue because platforms have pros & cons. Some are very good at web applications, while others may specialize in mobile applications or just backends.
That's why it's crucial to choose the platform that will allow you to do the core features of your application.
Also, keep this in mind. Usually, the steepness of the learning curve is directly proportional to the capabilities of the platform/tool. But don't be intimidated by the number of platforms. There is one that you can quickly meet your needs.
And do you need all these features? Really?
That is also an important issue. Do you really need what you consider core features??
One of the most common mistakes is turning the app into a feature freak.
After determining the core features when planning your application, take a walk, have a coffee or tea, and think again.
Adding features unnecessarily extends your time to launch the application and provides a more complex application for newly acquired users.
Try to finish your app with the minor feature set as soon as possible. Then, based on the feedback you get from users, you can identify new feature sets, remove unnecessary ones, and continue improving your application.
And it would be best if you didn't forget this either. The flexibility of the platform you use and its features are essential, but do you have to start with the hardest to bring what you have in mind to live?
No way!
If it will work for you, start with the tools that come with zero learning curve, play around, and try to gain programming logic. Then your transition to instruments with a steeper learning curve and more capable will be easier.
If you will be a developer and started no-code to grow your customers or your own business rather than bringing your ideas to life, you can skip step 2.
