-
YOu know I am a very enthusiastic and optimistic person.
that's right. I like your enthusiasm.
I recently went from Windows for imac and really do love it and it was this that made me ditch the BB for a iphone but after 8 weeks I knew something was missing and one morning woke up and just said BB here i come, come to daddy, daddy loves you............Bought a 9780 and give it a huge hug and voila.
Only slight issue was the initial sync with the mac as it gave a sync alert and want to change nearly all of my 3000 calendar entries but not the main body of the notes JUST the actual header that it was initally composed to eg: it wante it to change the header from General to PROFILE (I think from memory) It seemed that the imac sais Hey I am the master sync service and truth database and I want you to slightly change that pesky thing to conform with me.06-07-11 04:53 PM - If you're a developer, you should know about background task completion (<= 10 minutes) and other background services (no time limit). One of our apps uses both core location and audio in the background for as long as needed. Those are just two examples.
You have to be smart about this, and deploy your resources wisely. I will say that we make back all our investment in iOS and then some, no matter how much work is required to support various devices As an example, my current project has separate Mac, iPhone, and iPad apps built from the same core source but with different interface code. We're doing this because it's a huge revenue opportunity, so it's not a hassle. This is entirely different than gambling resources on Android where payback is not guaranteed.As mentioned above, the isolation of hardware on the devices. Trying to build an app that will work on an iPad, but take advantage of new hardware on iPad2, but also look correctly when outputted via HDMI to a 16:9 screen, and look correct on the odd-sized iPhone4 screen, but also be able to run on the limited hardware of an iPhone 3GS... well, it's not very easy to do. And if we don't dumb down our apps to work on older devices, we are then isolating a lot of potential customers and app sales.
Most of our more advanced apps can easily support both the iPhone 3GS and 4, and iPad 1 and 2. These apps aren't even practical on older devices like the 3G, so no loss there.
My very first OpenGL iOS game in October 2008 used OpenAL for panning stereo sound (jet flyby and other aviation/battle sounds). Stereo has been possible (and easy) from the beginning. You do need headphones to take advantage of it, obviously.2) It's a brilliant Phone OS that is now trying to be too many things at once. There are limitations here of course. As a simple example, the iPhone was built with a speakerphone with a single speaker (makes sense for a phone of course). When the iPad & iPad2 were scaled up using the same iOS and hardware layout, the devices were still built with Mono sound. If you open up an iPad2 you'll find two speakers in there; but there's no circuitry for stereo sound. Even with headphones most games/apps are in Mono.
Having developed for BB, WP7, Android, and iOS, I will take the iOS SDK hands down. And this from someone who didn't know a lick of Obj-C until midway through my career in 2002 or so. There's room for all languages and perspectives of course (hey, I started on Fortran) but I think the quality of iOS apps speaks volumes about the SDK. It's just really good for cranking out solid apps. The animations and graphics acceleration alone are something that really sets iOS apart.3) A major issue with iOS is its until-recently closed development platform of Objective C. It's nice that they now support pretty much any programming language you want to throw at it, but it still relies on embedding the interpreter in the code, and still can't support any JIT code unless you precompile and send it to Apple for review. It's frustrating having to jump through hoops. I suspect QNX and possibly Honeycomb supporting POSIX standards will allow incredibly easy platform development from a low level, and easy porting or apps over to the platform. There's a good demo on youtube of a POSIX Linux version of Quake 3 ported over the Playbook with minimal effort. To do this on iOS is not possible unless it is Jailbroken---but if you want it on the App Store you'll have to redevelop the app.
This is a stark contrast to what QNX will offer the following platforms to develop on at a low level (i.e. running on top of the kernel). This makes it an extremely powerful platform... just wait for that SDK and see.
- Adobe AIR
- Adobe Flash
- Android Java (Dalvik 2.2)
- OpenGL/ES
- OpenVG
- IEEE
- POSIX (Linux/Unix)
- Open SSL
- Zlib
- SQ Lite
- Open AL
- Curl
- Airplay (mp)
- Unity (mp)
- Native C/C++06-07-11 05:48 PM
