Greetings from Playlyfe. It's been a year of change for Playlyfe, with the shedding of old designs and old approaches to gamification, and introduction of newer, faster, and immensely better ways to gamify your apps and websites.

Here are some of the things we made simpler for you over this past year:

  1. Active Notifications: Our main aim is to simplify the process of designing and deploying a gamified system as much as possible for you, and one of the oft-requested and sorely missed features was a way for you to tell that there were errors in your design. You could, say for example, create actions which didn't give you any points, or badge metrics which didn't have any badges, and Playlyfe would have been a mute spectator until you launched your game... That was a lot of suck for a lot of designers.

    We've changed that by popping up push notifications as soon as you save components which have errors. So, say you create a process with no tasks, pop comes the notification bubble, saying Fix this NOW!, albeit in a more subtler fashion :) This cut down designers' time, which was earlier spent figuring out what's wrong in the design, and they're now able to invest much more into actually making their designs better, faster, and with a greater confidence.

  2. SDKs, SDKs and SDKs: Furthering that aim of simplifying gamification for you, we introduced a collection of Software Development Kits, a.k.a., SDKs for all of your favourite languages — C#, Java, Ruby, Python, PHP, NodeJS and Client-side Javascript. Checkout the complete collection on our Github repo. Here, we'd also like to mention our small but delightful community for contributing to the projects, in the way of reporting issues, bugs, and making some tangible contribution to our OSS effort.

  3. Open Discussions: We believe that the best way to take gamification forward and build a better community is by fostering constructive discussions on the subject. Therefore, we've opened up our platform and support for more scrutiny by launching a brand new discussion forum, and our try-as-you-read API Documentation. This is great news if you're new to our platform, as you will get a clearer idea by trying out stuff at the developer center and via discussions at the forums of how Playlyfe works and how easily you can integrate it into your awesome application.

  4. New API: Another welcome change is the new v2 API, which simplifies some of the application design and exposes many more functionalities which you've been requesting for some time now, like creating new designs directly from the application, or better leaderboards. This also means that we've split up our API into three different levels:

    • Runtime: the end-user Play part of gamification.
    • Admin: the boring part (or fun, depends on your inclinations) involving administrative stuff.
    • Design: the God mode - your app can change the rules as players play them!

This last part is the most powerful thing you can get: Imagine! Now you can change the design of the game in a more fluid manner from your own apps. No more coming to our platform and clicking buttons. It can all be automated, or tied-in with your logic. So, now create new actions on-the-fly or make rules which mutate as the game goes on! We'd be remiss if we didn't give one scenario where this can prove to be a boon!
Imagine you have a Learning Management System, and there are a bunch of courses, all with different set of students, different rules and different metric. It'll be nigh impossible to think of all these intricacies when you're starting off with gamifying the LMS. So, what do you do instead? Well, you can integrate Playlyfe into the LMS in a way which can let you add metrics or award badges right from the LMS's admin panel!

  1. New Horizons: Lastly, we have an exciting announcement, which we'll keep for next week.

Well, that wraps up this post. We'll be bringing more gamification goodies in our next article.

We wish you a happy new year.

Happy Gamifying.