Something often overlooked is how your app integrates to the user's mobile experience. When listening to music and interacting with other apps, it can be a bad user experience for the user's audio experience to be cut off when your app has no use for a focused audio experience.
Here's a short code snippet to allow your user to play background music in your IOS App...
So we all know Game Center isn't ideal - if user's don't login at install time it can be hard to get them to login whilst within your app. Game Center is designed to stop presenting the Game Center login view after the user has dismissed it a few times. Short of giving the user clear instructions to login once this has occurred there isn't really any ideal solution to get your user to login once they have decided to do so.
Since Apple introduced iBeacon as the WWDC conference as part of IOS7 it'd be fair to say that it may be slowly passing under the radar, but for me as a developer I feel this will be one of the most exciting products of recent years. Already there are a few front runners producing the hardware to utilise this technology and the case studies they have developed are very clear and focused in how they will help the end user.
So, with the release of Air 3.2 this week I decided to run a quick demo in the iPad using the source code of the Whack Game Demo by Byxb Interactive. This is pretty easily to do - overlay the Air 3.2 SDK then just create a new mobile project and copy over the source from the project.
I received my free PlayBook a couple of days ago and wanted to share my own personal views on the device and development process. Now we all know this hasn't been the smoothest of journeys for these guys - with a lot of flack from developers...
First opinions of the device are good, looks nice, feels good in the hand etc. It's only after a little bit of use where the small things become apparent. Now those that know me will know I'm a bit of an Apple fan - I've had my issues with various Apple devices but for the inconvenience the rest of the package keeps me a happy user. Initial factors to note are the lack of email client (something that will be rectified soon) and I have noticed not all sites work on the device (e.g. The FWA). Being a Flash compatible device I was expecting the PlayBook to replicate web browsing on my main machine with a few usability limitations due to the the device's size.
With the release of the new Air 2.6 SDK yesterday I wanted to see what performance improvements had been made. After a couple of hours playing with Ant scripts I managed to get this example up and running on my iPhone4.