There is another way to force an app to run as Runtime. That is changed the extension to accdr. But, such a file can be renamed back to accdb. This is NOT true of accde. When you convert to accde, it compiles the app and removes all the design stuff. That's why I didn't mention accdr in my first response.
If you want to distribute an app to people who don't already have an Access license, there is NOTHING you have to do to the app. You just need to include the Runtime file or a link so they can download it. Once they install the Runtime, they can then run the Access app.
However, you should test your apps to determine how they will work. You can force Access to run an app as if it was the runtime by renaming it as accdr. That's really what the accdr is for, to allow developers to test. But you can do the same with accde. You can install the runtime in a Virtual machine for test purposes as well. I have a few VMs for that purpose. An app that will be run under runtime and/or accde, needs to have a lot of error trapping since Access will only give a generic message when it encounters an error.