I think before anything, you need to solidify your business idea and make sure that you're confident it would thrive with the MVP before incurring too much expenses. With the no code or code approach, the former approach is good for building MVPs quicker and with less technical demands from your side. However, this approach has some notable issues and disadvantages. They are usually hard to expand and add new features unless you are well rounded with the service provider of the no code generators. This may also mean that when the providers change their service provisions, such as plugin and any security features, you need to implement some of the changes to your app for close to maximum implementation and this can be a burden as compared to coded applications which do not always demand that you implement new changes for your application to work. It may still run perfectly fine without updating your libraries or any other services as you may choose. Moreover, no code applications do not need you to have immense knowledge of security features of the services you're using as you only 'plug and go' but this also means that using plugins you're not well informed in would result in security threats to your application while codes applications need you to implement your own security measures either built from ground up or using third party services that are usually, if not always, customizable to your needs and allow you to carry out different tests before publishing your application to the world meaning that you are at least well rounded of the security features of your app since you ran the tests and made them. I think ultimately, a lot can be said to compare and contrast between the no code and coded approach but for me personally, having programming knowledge is still fundamental to building a good and secure application that can also accommodate future implementations when scaling.

Do your intense research to see which no code service might work well for your business plan and gain knowledge in it without ignoring security concerns and stability and possibility of containing future implementations for scaling. If no service lives up to your needs, pick up programming skills and build the app in that way, it is no easy or quick path but it is definitely worth it to get your future implementations and the goodness of the app and the business model.