[ChrisMarshallNY]

As an iOS developer, that could definitely use this, I completely support you, in keeping it Android native.

I’m a believer in native software (I write native software). I think it results in much higher Quality user experience, than hybrid development.

There’s a reason that it’s not super-popular, though. It’s a fair bit more expensive than hybrid approaches, and generally requires a higher skill level, as well. Most companies find that hybrid approaches are “good enough,” and they make much better margins.

That said, you could probably test it, using the Xcode Simulator. It’s gotten pretty good with I/O, lately. Bluetooth still requires a physical device, but most of the stuff could probably be tested fine, if you used a modular approach (my preferred methodology).

[niedev]

Yes I agree with you, moreover for now I am much better as a Java or C developer than as a web developer, so for me the native approach is also simpler. However, yes, I practically never use the emulator even for Android precisely because I have to test Bluetooth, which at least in my experience on Android, is the most difficult part.

[ChrisMarshallNY]

I wrote up this series, a few years ago[0]. It was actually #1 on HN for a day, but is probably a bit "dated," now.

I did do an actual video tutorial on it for try!Swift[1].

[0] https://littlegreenviper.com/series/bluetooth/

[1] https://github.com/ChrisMarshallNY/ITCB-master

[niedev]

Really cool tutorial! When/if I start developing for iOS this will be really useful, thanks!