Welcome to ArseyBee Productions’ website.
We released our first app, Conkers, in December 2009. Since then we’ve totally re-written the game to improve it’s realism. We did this by incorporating a proper physics engine (like the one used by Angry Birds) as well as adding damage effects and a grand finale. There are more features planned for the future. In particular, a 2-player mode which we believe would transform the playability. So keep watching…
Our second app, Mega Booth, was released in December 2010. Everyone knows the popularity of Booth apps, but they generally only do one thing each. We wanted to give better value than that – just because we can! So we put several preset morphs into one slick app. But we didn’t stop there – we also added the ability to make your own tweaks to the picture, or just start from scratch and do something totally new and different. We call this our ‘Freestyle’ mode and it’s pretty cool. When you are all done it’s really quick and simple to simply save the image to your photo album or, if you want to give your friends a laugh, upload the image to Facebook or Twitter. We also released Mega Booth Lite, the free version which has all of the same functionality of the paid for version except the ability to save and share your creations.
And there’s more to come. Not just updates to our existing apps, but new and exciting ideas we hope to make a reality. So please feel free to try out our apps, get in touch and follow us here or on Twitter…
In order to make your iOS 4.x apps work with iOS 3.x versions it’s important to remember to check what frameworks your app is using and if necessary weak link them.
The issue arises if you are using a framework specific to iOS 4.x and therefore isn’t included in iOS 3.x. A lot of people are still on 3.x because they have the original iPhone / iPod Touch, the 3G or even the 3GS (which runs slower on 4.x – but really not noticeably enough to put-off the benefits of 4.x).
If you aren’t sure about the frameworks you are using you can check the API differences documentation on Apple’s site (link here). Once you’ve identified the frameworks that don’t exist in 3.x Xcode makes it pretty simple for you to weak link them – basically flagging them as not required to run. If you don’t do this the app will simply crash on startup and return your disgruntled user to their home screen. Inevitably they’ll delete the app, unhappy that it doesn’t work and, due to the way Apple’s rating system works (let’s not go there – not now anyway…), there’s a good chance you’ll get a 1 star rating for something that should take just a few minutes to fix. Ouch!
To weak link the frameworks: just right-click on you app under ‘Targets’ in Xcode and choose ‘Get Info’. You’ll get a window that looks like this:
Weak linking in Xcode
Simply set the Type to ‘Weak’ instead of ‘Required’ for the relevant frameworks.
However, there’s also the reason you’re including the framework in the first place to consider. It’s being used somewhere in your code (if not remove it altogether!). Where you make a call to a method provided by the framework you need to check that the framework is loaded, or rather that the method will execute correctly. and if not tell the user that this feature doesn’t work on their iOS version.
If you’d like more help with this a good starting point is here on Apple’s site.
