@Christopher Tyson I'd add to this from my experience. The build for yourself is as Alex said a good place to start. However, in saying this, if you then want the app to either give or sell to your customers, this is where it can become a bit on the tricky side. Because what will work for you on your computer, may not have all the components to work on other computers. Hence, there is a time factor involved. Not to mention, sending apps without the full notorisation/signatures will also provide a few friction points - especially for Mac computers who may block the app. This also includes a cost factor decision that you may not necessarily have to make right way. Apple Developer is $99 for the year and you can include as many apps as you like for this. Microsoft can be Anything from $120 - $200+ to have the same thing. Hence, my suggestion is start with the end in mind even if the for customers is down the track. If you're using ai to build the app, simply tell it that whilst you are building for yourself at present, it needs all relevant code for customers down the track. I.e. I'm building for myself and I have a Windows 11 computer, however, it needs to also be available on Mac and Linx computers. Make sense? The build for yourself means you can test and tweak as the build progresses and have a complete working version for yourself.