If it's very small scale, your app may not be approved for the store anyway - one of the common reasons for rejection Apple cits is "If your app doesn’t offer much functionality or content, or only applies to a small niche market, it may not be approved." They don't, of course, say how small is small. I guess I'll find out when I've done all the hours of coding.
Anyway, you can install over the air on a small number of phones provided:
1. You have an Apple Developer account
2. You know the UDID of all the phones on which you want to install the app (get it via iTunes or have the owner visit get.udid.io on the phone's browser)
3. You add the UDID of each device to your developer account
4. You create a Provisioning Profile which includes each of those UDIDs
5. You use that Provisioning Profile when you build the app in release mode
6. After building, if using the Hosted Mac Builder, you download the latest build, which will pop a .ipa file in the Objects sub-folder
7. You can use the B4J OTA Deployer tool to upload that to Erel's servers; it will give you a link that can be emailed to the people who want to install the app.
8. Users will be asked if they want to install the app from the IP address of the server.
There are issues with this. Notably, Apple's limit on the number of test devices you can have on your account. With ten, you should be fine. However, be aware that you cannot delete a device, so if for example half the people lost their phones, or upgraded, and got a new phone, you'd have to add the new UDIDs, and the old ones would still be taking up space in the list, counting towards the quota of 100. If you had a larger user base, and people upgrading or breaking phones, you could quite easily reach the limit, which applies to your developer account as a whole, not per app.
The only time you can remove devices from the list is when you renew your account once a year, at which point Apple allows you to remove the ones you don't want to use - but do it before you start adding any more, because then the list is apparently locked again.
The description of using the OTA deployer is here:
https://www.b4x.com/android/forum/t...ly-distribute-your-app-to-beta-testers.61672/
You can also distribute from your own server, which is what I'm doing for a test app at the moment, mostly so that when people click the link, they're asked if they want to install from 'BLUF.com' rather than from an IP address. That was actually reasonably easy to set up, as long as your site is served over HTTPS. If anyone wants, I can post the details of that.