App Developer Focused On Music? Use Xbox Music API and Make Money!

Xbox Music API is now open to all third party developers. The affiliate program is interesting too, but will developers come?

App Developer Focused On Music? Use Xbox Music API and Make Money!

//build 2014: One Windows Vision Coming Together For Microsoft

I have resumed writing at Techie-Buzz. This past week, Microsoft’s //build/ conference gave me an opportunity to write something about the company and its moves.

At //build/, Microsoft made key announcements to get closer to realizing their vision of “One Windows”, hoping to increase developer interest in Windows.

//build 2014: One Windows Vision Coming Together For Microsoft

Windows Phone app problem

Over the weekend, I had a twitter conversation with the Wordboxer developers, trying to get them to port their game to Windows Phone. It brought to light an important point about the Windows Phone (and for that matter, Blackberry) app problem: most cool games and apps are being built by small shops or single developers who just don’t have the time to build and maintain more than one or maybe two versions of their app/game. I really hope the Windows Phone (and Windows 8) teams realize this and create ways and means to reach these folks and help them out with the education needed to have them port their apps.

I know with the addition to C++ and support for cross-platform game engines on both Windows Phone and Windows 8, things are easier in terms of porting, but the point is most devs look at market share numbers and shy away from the platform. Of course, the market share going up and reaching some level of respectability (10% in the US?) may automatically help, but until then, Microsoft has a tough problem on their hands. They have to increase sales of devices, they have to attract the big brands and they have to make sure the indie devs also consider Windows Phone, if not at launch, at least soon after.

Fingers are crossed.

Windows Phone app problem

Small devs really don’t have time to develop and maintain code for more than one or two platforms. Even though Windows Phone dev tools are arguably better than anything else out there, and porting is easier with Windows Phone 8, it comes down to resources. Here is a great example of that.

  1. @wordboxer My friends want me to play your game with them, but you don’t have your app on Windows Phone. Please help 😦
  2. I got an invite to play this game from someone on iOS. As usual, after not finding the game in the Windows Phone Store, I ping the developer twitter account.
  3. @TheRomit Unfortunately we have no plans to develop WordBoxer for Windows Phone…
  4. As is usually the case, developer says “no plans”. 😦
  5. @WordBoxer 😦 That’s terrible news. Can I make a desperate plea?
  6. Again as usual, I start begging. 🙂
  7. @WordBoxer porting to Windows Phone 8 is relatively easy. Looks like you already have Android, may as well attempt WP? 😦
  8. And then prodding.
  9. @TheRomit We’re not a big game company but just three friends who build WB in their spare time, and it takes lots of spare time already 😉
  10. Then …. reality. Devs don’t have the time.
  11. @WordBoxer Haha, ok. We need your help, that’s all. I am sure the folks at @wpdev won’t mind giving you a hand �� Cheers!
  12. More shameless begging.
  13. @TheRomit if you find us an investor down there in CA we might reconsider 😉
  14. More reality.
  15. @WordBoxer Investor, maybe. Dev/porting help? More than likely ��
  16. My side of the story: practicality.
  17. @TheRomit Help would of course be appreciated, but a way to make a living even more 😉
  18. Another dose of reality.
  19. @WordBoxer Windows Phone users definitely tend to pay more than Android. Hence, surprised that you ported to Android but not to WP.
  20. Hey, no harm in throwing some well-known facts to counter the harsh reality.
  21. @TheRomit 6 months ago when we started to port to Android the W8 marketshare was even less than the 5% now.
  22. At least they are aware of the 5% share. I see a slight opening 🙂
  23. @WordBoxer But Android users, despite the market share, tend to appreciate “free” whereas WP users tend to spend more.
  24. “It is not all about market share”, as the word on the street goes 🙂
  25. @lancewmccarthy Hey, I don’t know where these guys are located, but hope you can find help for them? See thread here twitter.com/WordBoxer/stat…
  26. Seeing the opening, I ping a good twitter friend and a prolific developer and now a Nokia Developer Ambassador. They can help and in fact, they encourage developers to port their apps.
  27. @TheRomit I guess the only chance to have make a living from an app like ours lies in high numbers of downloads.
  28. Meanwhile, back to reality.
  29. @WordBoxer of course. I am not trying to say you are missing a large market. You would have built the app already if that were the case.
  30. Countered with more practicality/realism. It’s not a bad idea to go Android after iOS, to get the volume.
  31. @WordBoxer My point is that you will see more stickiness and willingness to pay with an average WP user than an Android user.
  32. ….but, Windows Phone users are more loyal to the platform and the early adopters tend to support developers who bring their stuff over from other platforms.
  33. @WordBoxer Also, it helps that number of devices and resolutions and OS versions are way more limited than Android.
  34. My turn to throw some reality into the mix. It is easier to develop/port to Windows Phone because testing involves a finite number of resolutions and device types. Especially if they focus only on Windows Phone 8.
  35. @WordBoxer (Hence, potentially an incremental effort may give you some valuable customers. Just a thought.)
  36. Yup, continuing the reality trend – if they can re-use much of their code then the incremental effort to bring the app to Windows Phone may not be too much, but the upside is huge.
  37. @TheRomit I see your point, same goes for iOS users compared to Android users I think.
  38. Full agreement here.
  39. @WordBoxer Oh, of course. WP users definitely more like iOS in that sense. Of course iOS user count >>>>>> WP ��
  40. More agreement.
  41. @TheRomit but to create a viral effect, which obviously did not occur yet ;-), we needed the masses to play WordBoxer. Hence Android 😉
  42. No arguments here.
  43. @WordBoxer Anyway, I have pinged @lancewmccarthy who may have some resources to help you. It would be *great* if it comes to WP
    #hope ��
  44. And now, bringing Lance into the convo.
  45. @WordBoxer Agreed. That is def a proper method, no questions. With WP, you will get so much more coverage too, since we yearn cool iOS apps.
  46. Agreement all around.
  47. @TheRomit @lancewmccarthy thanks for sharing your thoughts! We’ll look into it! Cheers
  48. Looks like these guys are open-minded developers.
  49. @WordBoxer @lancewmccarthy Thanks for listening and being open to my humble thoughts. Cheers, and all the best!
  50. Appreciation for hearing me out.
  51. @WordBoxer I can help knock down the financial barrier, the only thing you’d need to do is build it. When you’re ready, ping me. @TheRomit
  52. Here we go 🙂
  53. @lancewmccarthy @theromit Hi Lance, that sounds interesting 🙂 Could you please drop us a mail at info@wordboxer.com to elaborate? Cheers
  54. Oh hey … could this twitter convo lead to something? Let’s hope so!

Read next page

Did you find this story interesting? Be the first to
or comment.

Liked!

Plex for Windows Phone is out

Plex, the “media center” software application built for a multitude of devices, has a Windows Phone app now. They wrote up a blog post about it and while I am excited that there is a WP7 app now, it was heartening to see the praise they had for WP7 both from a user’s perspective as well as from a developer’s perspective.

There are so many gems in that post, I felt compelled to not only write this blog post, but highlight a bunch of the gems from the post:

Android phones never managed to capture my interest. They just looked and felt like bad photocopies of the iPhone, and didn’t offer anything new I was interested in, like the ability to install a custom theme that looked even uglier than the default, or download torrents on my phone, or play a Matrix animation in the background, or remove my battery, or spend time killing random processes, or over-clock my CPU, or any other beardy sort of thing.

Fast-forward to this January, I ordered a second hand Samsung device to help with development, and promptly fell in love with it.

As much as Android felt like (poorly) recycled ideas and bad new ones, Windows Phone felt original, well designed, and fun to use.

The performance was great, really smooth in a way iOS is and Android isn’t even in ICS.

[Ice Cream Sandwich, or Android 4.0, from a Windows Phone User’s Perspective (my Techie Buzz post from earlier)]

The “pivot” and “panorama” UI concepts were fresh and a great way of making good use of a small screen in portrait mode. The typography was clean and brazen.

The integration of Facebook and Twitter made them feel like first class citizens, not an afterthought.

The live tiles on the home screen were a great way to make the phone feel alive.

But the iPhone felt staid, for lack of a better word. I wanted to be able to pin a few email folders to my home screen and watch them update live. I wanted to see all my social updates in a more integrated way. I missed being able to go to a contact (which I could also pin to my home screen), and easily see the conversations (Facebook, or SMS) I was having with them, and recent photos they’d uploaded.

The iOS development environment is quite good, with the weakest link being Objective-C, which has a steep learning curve and feels like it stepped out of the 80s with a cocaine hangover.

Android, oh, Android, I don’t mean to pick on you once again, but your edit-build-deploy cycle is long enough to make a grown man cry, and then stab himself in the eyeballs, and then cry some more. Java is fine, but the surrounding environment and piss-poor emulator makes it much harder to develop for than it should be.

So how is the Windows Phone development environment? It’s scary good. C# is a great language, .NET is a solid framework, XAML is a really nice way to design user interfaces, and the edit-build-deploy cycle is fast.

We were able to write the [WP7] app from start to finish in two months, between two engineers working part time, which is almost an order of magnitude faster than it took for the iOS and Android app.

Related (linked to from the blog post):

My last thought on Windows Phone is that it’s got all the ingredients it needs to be successful: It’s a fun, useful, well-designed platform, with sexy (Nokia) hardware, and it’s as good for developers as it is for users. It deserves much more marketshare than it has, and Microsoft seems to be making most of the right moves (about time).

Since I use WP7 all day and follow a bunch of WP7 developers on twitter, I am very well aware of all these benefits. I am glad the folks at Plex thought of putting all these thoughts on their blog.

Hope to see many others release their WP7 apps. Are you listening, Instagram?

Calm Down, Windows Phone Developers. Tango is Good for You!

Does Tango restrict developer capability so apps can target lower-end (256MB) devices? Per Justin Angel, Principal Engr at Nokia, not really.

Calm Down, Windows Phone Developers. Tango is Good for You!

Developer Interview: gReadie app developer Chris Sainty

An interview with Chris Sainty, the developer of gReadie, a Google Reader client for Windows Phone 7.

Developer Interview: gReadie app developer Chris Sainty