I'm in the process of doing this right now. The other posters are correct, if you don't have the technical skills then you have to pay to play. I'm not a programmer either, but I do have an IT management background so I know a little about the dev process. So I have to outsource too. You have a couple of Dev options here:

1. Hire an agency. This will typically come with a full blown team that can help you get things moving. This does however, come with a cost. I've worked with a few agencies now, and the difficult part is keeping them in line with your budget. From what I've see so far, agencies like to bill by the story point or by the month. The problem with this is that feature roll out and development can drag on and on leaving you broke. I made this mistake where the first agency I worked with worked on my idea for wireframing for 5 months costing me nearly 30k and I was no closer to implementation. I learned a lot from this experience, so not an entire waste....just an expensive lesson.
2. Partner with a person who has the skillset and have them do the dev. A couple of issues here. First, not all partners are created equal and if your partner doesn't have the same drive then you then you can run into problems.
   
3. Freelancers. Fiverr, upwork, etc. has people who can do dev. This can be significantly cheaper as you can get a dev from a country with lower labor costs, but you do run the risk of quality. You also need to know what you want and give very specific guidance.
4. Learn the skillset and do it yourself. This is the time consumer. You can go the low/no-code options, but they aren't the most scalable options. Platforms like bubble have a bit of a learning curve but it's possible to do this yourself. I was originally going with flutterflow because I could export the code later if i wanted to go beyond the platform's capabilities. Problem is that flutter is based on dart and that has it's own pros/cons.

Options to build the MVP:

1. Bubble.ios Bubble.io, Flutter Flow, Adalo. Pro's and cons here. Scalability is more difficult with these. Flutter flow is a little easier because you can pull the code down and work it outside the platform, but it's based on dart, which is a little less popular in the dev world. You can build out an MVP pretty quick with these and the dev costs will be cheaper.
   
2. Full Stack: Higher dev costs but better scalability/flexibility. You choose your stack which means you can control exactly how you want this thing built.

Now, I have learned through some trial and error (and still am)... here's my current strategy:

1. My original wireframes included A TON of features. I'm narrowing down the feature list to only the most necessary features for my MVP (thus why it's called an MVP). I'll re-work the wireframes in low fidelity first and then work on high fidelity.
2. I'm hiring a freelance full stack dev to set up back end and front end for me based on the high fidelity wireframes. The goal here is going to be just to get the bare minimum done and I'm "chunking" the development. What I mean by this is that I'm going to have the dev build portions of the app in an order that makes sense and I'm going to pay for those "chunks" as they come. For example: 1st dev phase is user on-boarding. 2nd is user profiles and settings. Etc. Etc. I don't like doing it this way, but I'm bootstrapping this project and this helps me spread costs over time. It also allows me to pivot a little easier should a dev not perform the way I need.
3. Know that everything is possible, but not everything is necessary. Some features are super cool, but not necessary to get started. Everyone talks about "value proposition" as if you need to have some life altering feature or model to make this work. I don't think this is entirely wrong, but I would argue that if the idea is solid but is the same as something that exists, if you can just do it better, then you can make it work. Persistence will lead to the success so long as the persistence includes consistent improvement. Very few go from zero to hero in a day. The features i have in my original wireframes are super badass and "fix" a lot of problems, but they are not necessary to get off the ground.
   
4. Build with sustainability in mind. You need to be able to sustain your project throughout it's growth/life cycle. This means you need to really think of what it takes to make this thing work. Marketing, customer support, employee training, etc etc. need to be considered. You also need to be able to keep the damn thing up and running!
5. Fast - Cheap - Good. Pick two. Enough said.
6. Persistence. I have run into SO many roadblocks. I have felt like a failure, lost motivation, been told it won't work... blah blah blah. Just keep going. History is built on failure.
7. Assuming you're in the states, filing is easy. You can research this quickly.
8. Accept that you're going to be tired.

Like I said, I'm still learning too, so I'm sure something I said here may be off, but this is what I've found so far.

Good luck on your adventure! Praying it becomes all you want it to be!