@meshjay, @geeksville it would be great if I can get this is the position where it can be submitted to the App Store, but at the moment I have only been working with Meshtastic devices for the last few days, so its impossible to put any timescales on what can and cannot be achieved.
It is also worth bearing in mind that this is very much a part time project fitted around family and work commitments and the approach to this will be different to Mesh Developers Toolkit (https://apps.apple.com/us/app/mesh-developers-toolkit/id1342708841) which I started to extend Mesh functionality from pure messaging to linking up with other devices (e.g. a lightening detector), before a python API was available.
Meshtastic already offers a great Python API - so it makes no reason for me to replicate this, but the Idea of building a client for iOS does appeal, as does the open nature of the platform.
I also need to understand better how the stack works (although I think I have the basics) and adopt an approach which will allow me to work alongside the core Meshtastic project.
Although I could pick up the c++ code and refactor it to work with Objective-C, I need to come up with a method that allows me to keep in sync with the main code base - if that makes sense.
Which is very different to the work on Mesh Toolkit where I was working with a SDK which offered a level of abstraction from the low level message formatting.
I would hate for Meshtastic to be getting flak over something stupid I had done code wise.
Although on a positive note, the next steps that I will be looking at to address is the use of protocol buffers and binary encoding…