A small, but effective, guide on how to quickly setup the Android Emulator using the x86 images (not the painfully slow ARM emulation) and GPU.
Check it out at http://detectmobilebrowsers.com/
This step-by-step guide is designed to help app developers and entrepreneurs: understand the variety of ways to monetize apps and develop a pricing strategy that is flexible.
The guide, by Jen Gordon of Smashing Magazine, is freely available at http://www.designboost.net/app-monetization-guide/
Small step-by-step guide on how to install and run Windows 8 Developer Preview under VirtualBox.
Chris Chabot announced the new Google+ APIs:
I’m super excited about how the Google+ project brings the richness and nuance of real life sharing to software, and today we’re announcing our first step towards bringing this to your apps as well by launching the Google+ public data APIs.
Appcelerator’s approach to the Android platform has made another victim, a significant one: 6Wunderkinder’s popular Wunderlist ditched Titanium Mobile (TM) for Android, and is now a native app.
“(…) Wunderlist is now native – smaller, faster and more stable.”
Matthew Bostock, 6Wunderkinder’s blog
Translated, Wunderlist got rid of TM’s biggest problems:
- Size: even the smallest “Hello World” app weights at least 1.5MB (this is still huge in the mobile world – do the same thing using native Java and the app will only weight a few KB);
Appcelerator reacted two days after 6Wunderkinder’s announcement, stating that Titanium Mobile for Android will use, somewhere in the future, google’s V8 engine. This comes, however, with a still significant drawback: only devices running Android 2.2 or newer support android’s NDK, and therefore the natively compiled V8 Engine. According to Appcelerator’s own benchmarks, this will at least double the performance. Remains to be seen if the “Size” problem will be solved: V8′s binaries will still be inside the app’s package…
An Apple employee lost a working prototype of the upcoming iPhone 5 in a bar, and someone took it home. Here is the TV Ad Apple made* on this subject.
Jonathan Stark, blogger and writer of various books (Building Android Apps with HTML(…), Building iPhone Apps (…) without Objective-C among others), compares various approaches to Mobile Enterprise development: Native Apps, Web Apps and Hybrid Apps (PhoneGap, Titanium et al.):
(…) As the mobile enterprise continues to boom and hardware complexity grows with a wide range of platforms, devices and audiences, there is no doubt that HTML5 will skyrocket in adoption. HTML5 Web-based apps offer the developer a “write one, run many” solution, addressing the many demands of today’s immediacy for remote communication, along with enhanced modern media capabilities that have become of increasing importance to both business and consumer.
Complete article on WirelessWeek.com.
Yes, the excellent WebOS is defunct, and it will never be the mainstream player as, at least technically, it deserved. For all of us developing for the mobile world that don’t have the time or budget to develop natively in all the mainstream platforms, its one less player to target. Myself, personally, am deciding/evaluating available options for true cross-platform development targeting iOS, Android, Blackberry and Windows Phone 7.
My requirements are:
- Native UI components must be used – maintaining the native look and feel for each platform is important (PhoneGap is out of the picture because of this);
- The same code base (or at least most of it) must be used in all platforms;
- The UI must scale well between Phone and Tablet formats and screen densities (DPI);
- The application must perform smoothly, speedwise, even in lower end devices;
- Some access to the device’s hardware: GPS, sensors, camera.
I have found some platforms so far:
- RhoMobile: haven’t tested or reviewed this one yet, opinions anyone?
So, i need your opinion about these or other development tools: are they any good? Have you used them in a project? Comment below.
I am currently evaluating development frameworks and mobile platforms for my company, so we can choose our path in our next multi-platform mobile applications (to develop specific apps for each platform is just too expensive). This took me to WebOS, clearly a small player, but with HP at the wheel, maybe it will get somewhere. So, lets look at it: install the SDK, start the emulator and…
… something went wrong: was trying to start Palm WebOS Emulator, version 2.1, and this error always popped up:
The object functionality is limited
code E_ACCESSDENIED (0×80070005), component Machine, interface IMachine, callee IUnknown
and I’ve found the solution!