Don't commit to one no-code platform. Instead, match the tool to the job, the tool's current state, and your own skills. Since platforms change fast and your expertise grows, what worked six months ago might not be best anymore. Pick based on the problem, not habit.
Don't pick a no-code stack. The right tool for a job, the right no-code tool for a job is going to be based on one of three, maybe three factors, some combination. The first is going to be what is the job? What is the thing that needs to be accomplished out in the world? The second is going to be what is the state of the tool? One of the things about these no-code tools, and that's true of all dev tools, is they keep on changing and change pretty quickly so that the right tool, say, 6 months ago, may not be the right tool now based on change in features and vice versa. The third is going to be the change in you, your understanding, your skills. The matching of the tool to the carpenter is going to be, I think, really critical to getting the maximum value and being able to gain speed and clarity and effectiveness for whatever it is you're trying to put into the world. So I would say, don't pick a no-code stack, pick a no-code you. Evolve you, evolve your understanding of the market, evolve your market and technical knowledge, and you'll be able to bring the right tool to the job and you will be bigger than the game.
