Are we Migrating to MetaWear-Swift-Combine-SDK?
Hello,
Currently, we are using MetaWare Motion R accelerometer to get the accelerometer data and using Below SDK to connect and download data from Sensor to Mobile.
https://github.com/mbientlab/MetaWear-SDK-iOS-macOS-tvOS/tree/master/StarterProject
As part of recent changes, I could see more updates on the below framework are we migrating from the above SDK to the below SDK in the future and if so can we accept similar sample apps and other example apps available in the above repo .?
https://github.com/mbientlab/MetaWear-Swift-Combine-SDK
And also we is there any special repo for each model base or its common for all type of sensors ?
Comments
We are strongly considering the move based on user reviews / feedback.
Thanks, @laura for the quick reply and found the Streamy https://github.com/mbientlab/Streamy
also has some minimal features so are is there any timelines to move completely or does the current code base also works?
The reason for asking this question is if you provided some SDK update/New Features and that is not done on the below source and only implemented on the swift combined framework we might need to plan to write the communication layer accordingly. Hopefully will get updated both until the swift combined framework has some good shape.
https://github.com/mbientlab/MetaWear-SDK-iOS-macOS-tvOS/tree/master/StarterProject
also Appreciated your response to MMRL support thread
https://mbientlab.com/community/discussion/4076/observed-the-change-in-download-recorded-data-from-sensor-to-phone#latest
@Srinivasa
We are still updating our swift examples, SDK and Apps but I think we are going to make the executive decision to move to this new SDK permanently.
@Laura
Hello, this may be late to the discussion. What is the future plan for the Bolts-Swift version of the iOS SDK then? Would it no longer communicate with newer firmware in the future or that it simply won't receive any updates? Since most of the old iOS SDK is still mainly MetaWearCpp codes, I would assume that Cpp SDK will still receive updates so we just need to handle the iOS-side code ourselves if iOS SDK won't be updated anymore?