I'm already doing this with libmsftband Python by Intensive_Coffee, but this requires technical skills which some community members may not necessarily have. My personal opinion is that, since we've missed the deadline for end-of-support, the initial priority should be to build an app that just lets users pull their data off and save it somewhere, for later use once we get a fully functioning client. Maybe we should pool resources and come up with a clear set of priorities. Maybe I'll do a big sprint on this over the weekend.įrom this thread, it's clear there is community interest to keep the Band alive with a new app. I do not want to rely on the official SDK, hence why msftbandlib is being written from scratch, using direct communication over RFCOMM (and all credit to Intensive_Coffee for figuring out so much of this). If anyone else is interested in this, I am open to accepting contributions I feel this is a viable approach but I'm not sure when I'll be able to devote much time to this.
#Microsoft band app for android android#
Android has an app shell but Band connection doesn't work (because I haven't got an Android implementation of msftbandlib yet). The UWP build currently lets you connect to a paired Band, nothing else. Intend to support UWP and Android initially.
![microsoft band app for android microsoft band app for android](https://cdn.pocket-lint.com/r/s/970x/assets/images/115808-apps-news-microsoft-s-onx-app-for-android-can-do-absolutely-anything-so-long-as-you-have-the-api-code-image1-dBoqIhtKWJ.jpg)
At present, it only contains core classes for creating a connection to a Band.
#Microsoft band app for android Bluetooth#
NET Standard, with platform-specific implementations for different mobile OS Bluetooth stacks (currently just UWP). – This is intended as a new SDK implementation. Hoping to resume it soon but right now, there really isn't much at all. TLDR as a direct response to this comment and for others to read: I've barely done anything since I last spoke to you directly sadly, other more urgent (to me) commitments have meant I've dropped it over the past month. Hey, sorry, just completely missed this discussion! In the meantime, I'm going to use Intensive_Coffee's libmsftband Python library to keep pulling my data off my device in the hope we'll get to a point where import into a new client is feasible. I hope to pick it up again soon since Band is EOL from today. There's also a functioning Android app shell, but no msftbandlib Android implementation yet so it will crash when trying to connect. Msftbandapp uses those to, at present, successfully connect to a paired Band with the UWP app. Msftbandlib has some core connection classes to represent Band connections in. even when I was working on it, progress was slow but I was having a great time learning new things.
![microsoft band app for android microsoft band app for android](https://i.pinimg.com/originals/56/b0/39/56b0390fbe0edcf356e040a5a99ec2ee.jpg)
At present, all I have is the foundations of this project structure. Unfortunately, as I said, scheduling time to work on this has proven problematic. NET Standard, and then incorporation of that into the new client app. Hence the reimplementation of a new backend from scratch, using. Myself and I believe Intensive_Coffee feel that continuing to rely on the official SDK for any new client app is an inherently risky move and continues to, on some levels, tie the Band to the Microsoft Health backend. My approach is to create a new cross-platform app using Xamarin (msftbandapp), backed by a new from-scratch SDK (msftbandlib). I'm not experienced with working with Bluetooth, or UWP really, but was using libmsftband by /u/Intensive_Coffee as a reference point. but due to other commitments, haven't been able to work on my project in over a month. Missed this discussion but to jump in here, have also looked at this.