Metro Nuggets

Bitesized tidbits for building Modern (Metro) apps.

Tag Archives: pcl

Introducing Bex, A PCL Library for the MS Health APIs

Yesterday Microsoft [finally] released the MS Health APIs they’d talked about at this year’s Build conference. These APIs are a way of accessing the data that’s been accrued from your Microsoft Band, so any bike rides, runs, sleep tracking, etc. These APIs are a set of REST endpoints that, once authenticated, you can call to access this data. So, naturally, I’ve decided to make this easier.

Read more of this post


Introducing the RottenTomatoesPortable PCL

Over the weekend I was looking at some Rotten Tomatoes stuff for Media Browser 3, and I noticed they had an API for getting the movie information (including reviews and fresh ratings). It’s been a while since I last did a PCL and to avoid any withdrawal symptoms, I created a new project.

For those that don’t know, Rotten Tomatoes is a review aggregator for movies that gives a “freshness” rating based on the reviews that have been done about a given movie.

Read more of this post

Introducing the ScoreoidPortable PCL

For a game I’ve been writing the last few weeks, I’ve been using an online scoring system in order to keep a track of people’s best scores whilst playing the game. What I’ve been using is Scoreoid, which is a cross platform scoring platform. It’s actually pretty easy to get yourself set up with Scoreoid, but that’s not the purpose of this post.

Their API is a REST based one and has a pretty expansive list of calls, from player creation, to score creation to leaderboards, etc. Initially, I looked to see whether anyone had already created any kind of helper library for Scoreoid and found Scoreoid for Windows 8 which I had to tweak in order to use it in my Windows Phone game. Unfortunately, the number of methods it had implemented was somewhat limited, I guess Rudy only implemented the ones he needed, so I found I was going to be adding a lot to his existing code base. In the end, I decided I’d write my own version and have the library how I wanted it (naming conventions etc).

So that’s what I did.

Read more of this post