Tiangang-AWS wrote on April 27, 2018:
Hi,
Thanks for sharing your use case. As a general rule, we typically don’t share our roadmap on forum.
So it looks like you’re trying to put cloud communication logic on your mobile app, and the app will talk to the device via BLE right? In this case, we do have AWS SDK for iOS, which could help you with device shadow management. You might also want to take a look at this sample, [https://github.com/awslabs/aws-sdk-ios-samples/tree/master/IoTTemperatureControl-Sample/Swift/IoTTemperatureControlSample].
On the device side, I would suggest only using a json library and plain FreeRTOS since device shadow is just a json document. You can check how to construct a valid shadow document here, [https://docs.aws.amazon.com/iot/latest/developerguide/device-shadow-document.html]. You can even delegate this to your mobile app if you want, then you don’t need any json library at all, the device would send the required parameters via BLE to your mobile app as you described. What the shadow library in Amazon FreeRTOS does is to help you with MQTT connection part, it takes the thing name (which is needed for MQTT topic) and the json document as input parameters, then talks to AWS IoT via MQTT.
The idea of Amazon FreeRTOS is to make it easy for developers to develop cloud based applications on microcontrollers. This way, the device can operate by itself and talks to the cloud directly, and you can build most part of your application logic inside the mcu. In your specific use case, I don’t see you would benefit a lot from using our libraries, I do wish we already have BLE support for you though. 
Thanks,
Tiangang