One More Tap » Apple

Thanks, Steve.

xcool — Thu, 06 Oct 2011 05:04:51 +0000

It is a sad day indeed.

I bought myself an iBook back in 2004, wanting to get myself out of PCs. I didn’t know that I’ve just entered myself into the world of Steve Jobs. Three more Macintosh computers, a few iPods and iPhones later, and I am still thrilled to be in this world that was changed by Steve.

Thanks for leaving a dent in our Universe, Steve. Rest in peace.

Screencasting Using Display Recorder for iPhone, iPad or iPod touch [Jailbreak Only]

xcool — Sun, 21 Aug 2011 02:49:31 +0000

True story: I finally did it and jailbroken one of my iOS devices. The victim happens to be my faithful first-generation iPad. I did it simply because I wanted to be able to do screencasting on my device.

You see, I have always been a fan of Street Fighter. I downloaded both Street Fighter IV and Street Fighter IV Volt the moment it was released. If you want a fighting game for your iOS device, the Street Fighter series is the one to get.

With the debut of Street Fighter IV Volt, online multiplayer became possible. I’ve spent countless hours before bed playing with people from all over the world. One thing I loved about the game is the ability to save replays of your favorite matches. Some of these replays were epic moments during game play. I hit the maximum amount of 20 replays quickly enough that I find it difficult to let go most of these replays.

At first, I thought of using a digital camera to record the screen while the replay plays. Not a very good idea. Truth be told, I’d even tried using my iPhone 4 to record the game from my iPhone 3GS. I’m a person who looks for perfection and has an eye for detail, and both options created videos that were lousy in quality or simply mediocre.

I did some research and found Display Recorder by famed jailbreak developer Ryan Petrich fitting my needs. There are other solutions out there, but Display Recorder gets the most attention. However, nothing’s perfect in this world, and so is Display Recorder. It does screencasting perfectly, but it doesn’t record any audio.

No worries there. We can always improvise. And I’ll tell you how in a while.

So, I set my sights on jailbreaking my iPad since its not my day-to-day device. I’m not going to detail the process of jailbreaking here, simply because jailbreaking is not the focus of this site and you can easily find hundreds if not thousands of articles on the internet regarding jailbreaking with a simple search on Google.

Once the iPad has been successfully jailbroken, I downloaded Display Recorder after paying the small fee of just $4.99.

Before you start screencasting using your iPhone, iPad or iPod touch, it’s a great idea to check out Display Recorder’s settings. The default settings are okay, but I’d change it anyways. Display Recorder’s settings are available under the Settings app. Refer to the attached screenshot if you’d like to copy my settings. Here’s the tricky part. The framerate is set using a slider, but there’s no indication of what value is being set. It defaults to 20 frames per second (fps) but I thought I’d set mine to 24 fps. This value is stored in a file located at /var/mobile/Library/Preferences/com.booleanmagic.displayrecorder.plist. Look for DRFramesPerSecond and change the value to 24.

By default, Display Recorder can be activated by pressing and holding the Sleep button. A prompt will appear to confirm if you want to start recording. Feel free to try recording some screencasts.

Earlier, I mentioned about improvising on Display Recorder’s inability to record audio. My Unibody MacBook Pro came with an audio jack that functions as both audio in and out. What I did was to connect one end of an auxiliary cable into my iPad’s audio jack, and the other into my MacBook Pro’s audio in jack. Here’s a selection of auxiliary cables on Amazon if you need one to get one for yourself. Next, I launch QuickTime Player and voila! Just be sure that the volume from your iPad is not set to too soft, otherwise you’ll have a hard time later.

Now that I have everything setup accordingly, I am ready to record screencasts on my iPad. For Street Fighter IV Volt’s replays, I recorded the replays from start til end. At the same time, audio from the iPad is routed to my MacBook Pro and recorded as well. I end up having two streams of recording on my computer. One for audio and the other being the video.

It’s a matter of dubbing them and synchronizing the audio using any video editing software that you have. Mac users like myself may want to use iMovie that came pre-installed. I’m not a Windows user, but I heard that Windows Movie Maker fits the bill.

Display Recorder isn’t all perfect, as I’ve mentioned above. During my recording sessions, I observed lags and some flickering. But the resulting video came out okay with a little bit of lag, but minus those flickering. I’m perfectly fine with this, since it’s tonnes better than recording by holding another camera or iPhone.

What do you do with the video that you recorded? Well, I uploaded mine onto YouTube, of course!

iOS 4 Multitasking and Your Battery Life

xcool — Wed, 25 May 2011 06:59:57 +0000

I read David Pogue‘s latest article in the NYTimes regarding extending your battery life with a lot of interest. There are some mistakes in the article, particularly on how one can actually prevent apps from staying in the background by killing them – Pogue has requested the NYTimes people to amend his article.

What got me more interested was the fact that quite a lot of people don’t really understand how multitasking on iOS 4 works. One of the main reasons was the way Apple (and most likely Steve Jobs) dictated how multitasking should work on their mobile operating system.

Thinking differently, Apple thought that their multitasking implementation would help a lot in saving battery life. To a certain extent, they did.

iOS 4 Multitasking

Multitasking on iOS 4 is a little different compared to what every one of us understands it. The truth is, most apps that are compatible with iOS 4 goes into a suspended mode as soon as you exit the app by pressing the Home button. There are however, some apps that simply gets killed when you exit – really. Developers are given the option whether to enable multitasking for their app or not.

Yoda: there is another.

Yes, there is an additional category of apps that remains running in the background when the users quit. Some example of apps in this category include those that plays music in the background like Pandora, some VoIP-based apps like Skype and apps that require constant usage of the GPS radio. These are apps that will drain your battery, per se.

Obi-Wan: So what I told you was true, from a certain point of view.

Certain iOS 4 compatible apps that go into a suspended mode, don’t really get suspended until 10 minutes later. Apple gave developers a grace period of exactly 10 minutes to complete whatever task that the app was actually doing. For instance, let’s say you are downloading a file in GoodReader (boy, I love this app a lot!). While the file downloads, you get an incoming phone call. You decide that the call is important so you picked it up. Moments later, you end the phone call and return to GoodReader. Your file may have been downloaded completely. GoodReader has just spent the 10 minute grace period to complete its task of downloading your file before telling the operating system that it is okay to put it (GoodReader) into suspended mode.

What happens if Good Reader didn’t actually finish downloading the file after the 10 minutes grace period is over? In this case, the app would have to give up the task and inform iOS that it is okay to be suspended. Failing to do so will result in the app getting killed by the iOS watchdog.

AppSwitch - Processes List

Apple did a great job with the way multitasking is handled. The implementation of their “multitasking bar” was a little flawed though. It is basically a list of “recently used apps” instead of “what’s still running” in the background. You don’t actually see what apps are really running in the background unless you dig further into iOS.

That’s where the idea of my recently released app, AppSwitch came about. The app was born out of the need to see what apps runs in the background, versus which doesn’t. Before AppSwitch, there were already a lot of apps that display a list of processes on your device. But I thought I could bring AppSwitch a level further.

A few months later, AppSwitch was born. And while it took a few weeks of “fingers and toe-crossed” moment hoping that it won’t get rejected, the app finally went thru Apple’s strict approval process.

iStat - Processes List

AppSwitch identifies and displays a friendly list of apps that runs in the background. Compare this to the usual processes listing app that simply gives a list of weird Unix-like names. AppSwitch can do this because of its own internal database of identified apps, all thanks to feedback from users and developers alike.

I tend to use AppSwitch to see which app remains running in the background, and decide if I should kill it from the Recently Used List. This has helped me save battery life by allowing only apps that I really need to run in the background and preventing others from running at all once I quit the app.

I’d have to say that we do get a lot of request from users asking to add a “kill” button into AppSwitch. Unfortunately, that will never be allowed by Apple.

You may be asking why would I want an app to see what other apps are running. Well, truth is, AppSwitch has its novelty and it’s other features like the Console can be helpful in troubleshooting an app. You can still kill apps from the Recently Used List.

On another note, you may also want to check out this article that I wrote many moons ago on how I actually maintain the long-life of all my battery-powered devices.

Apple Strikes on Social Media

xcool — Thu, 27 Jan 2011 06:22:45 +0000

It has begun. Well, since September 16 2009, that is when they first registered the account.

Apple’s @AppStore Twitter account is now finally alive and Verified. What does this mean? Well, that means Steve and Co would like your attention on Twitter – lots of it.

As of this writing, about 114,000 Twitter users are following that account which has so far sent out eleven tweets related to apps that are available on the iTunes Store. Aside to that, take note also that @AppStore follows five other iTunes-related property which are all, yes, Verified too.

If you are on Twitter, give @AppStore a hello and follow them. Oh, while you are there, do follow us @OneMoreTap, eh?

Steve Jobs’ Thoughts on Flash

xcool — Fri, 30 Apr 2010 04:13:11 +0000

This one’s been long awaited. The article was dated 27 April 2010 – I based this on the file name of the “Thoughts on Flash” image that appeared in Apple.com’s front page.

Read from the CEO himself after the break.

Apple has a long relationship with Adobe. In fact, we met Adobe’s founders when they were in their proverbial garage. Apple was their first big customer, adopting their Postscript language for our new Laserwriter printer. Apple invested in Adobe and owned around 20% of the company for many years. The two companies worked closely together to pioneer desktop publishing and there were many good times. Since that golden era, the companies have grown apart. Apple went through its near death experience, and Adobe was drawn to the corporate market with their Acrobat products. Today the two companies still work together to serve their joint creative customers – Mac users buy around half of Adobe’s Creative Suite products – but beyond that there are few joint interests.

I wanted to jot down some of our thoughts on Adobe’s Flash products so that customers and critics may better understand why we do not allow Flash on iPhones, iPods and iPads. Adobe has characterized our decision as being primarily business driven – they say we want to protect our App Store – but in reality it is based on technology issues. Adobe claims that we are a closed system, and that Flash is open, but in fact the opposite is true. Let me explain.

First, there’s “Open”.

Adobe’s Flash products are 100% proprietary. They are only available from Adobe, and Adobe has sole authority as to their future enhancement, pricing, etc. While Adobe’s Flash products are widely available, this does not mean they are open, since they are controlled entirely by Adobe and available only from Adobe. By almost any definition, Flash is a closed system.

Apple has many proprietary products too. Though the operating system for the iPhone, iPod and iPad is proprietary, we strongly believe that all standards pertaining to the web should be open. Rather than use Flash, Apple has adopted HTML5, CSS and JavaScript – all open standards. Apple’s mobile devices all ship with high performance, low power implementations of these open standards. HTML5, the new web standard that has been adopted by Apple, Google and many others, lets web developers create advanced graphics, typography, animations and transitions without relying on third party browser plug-ins (like Flash). HTML5 is completely open and controlled by a standards committee, of which Apple is a member.

Apple even creates open standards for the web. For example, Apple began with a small open source project and created WebKit, a complete open-source HTML5 rendering engine that is the heart of the Safari web browser used in all our products. WebKit has been widely adopted. Google uses it for Android’s browser, Palm uses it, Nokia uses it, and RIM (Blackberry) has announced they will use it too. Almost every smartphone web browser other than Microsoft’s uses WebKit. By making its WebKit technology open, Apple has set the standard for mobile web browsers.

Second, there’s the “full web”.

Adobe has repeatedly said that Apple mobile devices cannot access “the full web” because 75% of video on the web is in Flash. What they don’t say is that almost all this video is also available in a more modern format, H.264, and viewable on iPhones, iPods and iPads. YouTube, with an estimated 40% of the web’s video, shines in an app bundled on all Apple mobile devices, with the iPad offering perhaps the best YouTube discovery and viewing experience ever. Add to this video from Vimeo, Netflix, Facebook, ABC, CBS, CNN, MSNBC, Fox News, ESPN, NPR, Time, The New York Times, The Wall Street Journal, Sports Illustrated, People, National Geographic, and many, many others. iPhone, iPod and iPad users aren’t missing much video.

Another Adobe claim is that Apple devices cannot play Flash games. This is true. Fortunately, there are over 50,000 games and entertainment titles on the App Store, and many of them are free. There are more games and entertainment titles available for iPhone, iPod and iPad than for any other platform in the world.

Third, there’s reliability, security and performance.

Symantec recently highlighted Flash for having one of the worst security records in 2009. We also know first hand that Flash is the number one reason Macs crash. We have been working with Adobe to fix these problems, but they have persisted for several years now. We don’t want to reduce the reliability and security of our iPhones, iPods and iPads by adding Flash.

In addition, Flash has not performed well on mobile devices. We have routinely asked Adobe to show us Flash performing well on a mobile device, any mobile device, for a few years now. We have never seen it. Adobe publicly said that Flash would ship on a smartphone in early 2009, then the second half of 2009, then the first half of 2010, and now they say the second half of 2010. We think it will eventually ship, but we’re glad we didn’t hold our breath. Who knows how it will perform?

Fourth, there’s battery life.

To achieve long battery life when playing video, mobile devices must decode the video in hardware; decoding it in software uses too much power. Many of the chips used in modern mobile devices contain a decoder called H.264 – an industry standard that is used in every Blu-ray DVD player and has been adopted by Apple, Google (YouTube), Vimeo, Netflix and many other companies.

Although Flash has recently added support for H.264, the video on almost all Flash websites currently requires an older generation decoder that is not implemented in mobile chips and must be run in software. The difference is striking: on an iPhone, for example, H.264 videos play for up to 10 hours, while videos decoded in software play for less than 5 hours before the battery is fully drained.

When websites re-encode their videos using H.264, they can offer them without using Flash at all. They play perfectly in browsers like Apple’s Safari and Google’s Chrome without any plugins whatsoever, and look great on iPhones, iPods and iPads.

Fifth, there’s Touch.

Flash was designed for PCs using mice, not for touch screens using fingers. For example, many Flash websites rely on “rollovers”, which pop up menus or other elements when the mouse arrow hovers over a specific spot. Apple’s revolutionary multi-touch interface doesn’t use a mouse, and there is no concept of a rollover. Most Flash websites will need to be rewritten to support touch-based devices. If developers need to rewrite their Flash websites, why not use modern technologies like HTML5, CSS and JavaScript?

Even if iPhones, iPods and iPads ran Flash, it would not solve the problem that most Flash websites need to be rewritten to support touch-based devices.

Sixth, the most important reason.

Besides the fact that Flash is closed and proprietary, has major technical drawbacks, and doesn’t support touch based devices, there is an even more important reason we do not allow Flash on iPhones, iPods and iPads. We have discussed the downsides of using Flash to play video and interactive content from websites, but Adobe also wants developers to adopt Flash to create apps that run on our mobile devices.

We know from painful experience that letting a third party layer of software come between the platform and the developer ultimately results in sub-standard apps and hinders the enhancement and progress of the platform. If developers grow dependent on third party development libraries and tools, they can only take advantage of platform enhancements if and when the third party chooses to adopt the new features. We cannot be at the mercy of a third party deciding if and when they will make our enhancements available to our developers.

This becomes even worse if the third party is supplying a cross platform development tool. The third party may not adopt enhancements from one platform unless they are available on all of their supported platforms. Hence developers only have access to the lowest common denominator set of features. Again, we cannot accept an outcome where developers are blocked from using our innovations and enhancements because they are not available on our competitor’s platforms.

Flash is a cross platform development tool. It is not Adobe’s goal to help developers write the best iPhone, iPod and iPad apps. It is their goal to help developers write cross platform apps. And Adobe has been painfully slow to adopt enhancements to Apple’s platforms. For example, although Mac OS X has been shipping for almost 10 years now, Adobe just adopted it fully (Cocoa) two weeks ago when they shipped CS5. Adobe was the last major third party developer to fully adopt Mac OS X.

Our motivation is simple – we want to provide the most advanced and innovative platform to our developers, and we want them to stand directly on the shoulders of this platform and create the best apps the world has ever seen. We want to continually enhance the platform so developers can create even more amazing, powerful, fun and useful applications. Everyone wins – we sell more devices because we have the best apps, developers reach a wider and wider audience and customer base, and users are continually delighted by the best and broadest selection of apps on any platform.

Conclusions.

Flash was created during the PC era – for PCs and mice. Flash is a successful business for Adobe, and we can understand why they want to push it beyond PCs. But the mobile era is about low power devices, touch interfaces and open web standards – all areas where Flash falls short.

The avalanche of media outlets offering their content for Apple’s mobile devices demonstrates that Flash is no longer necessary to watch video or consume any kind of web content. And the 200,000 apps on Apple’s App Store proves that Flash isn’t necessary for tens of thousands of developers to create graphically rich applications, including games.

New open standards created in the mobile era, such as HTML5, will win on mobile devices (and PCs too). Perhaps Adobe should focus more on creating great HTML5 tools for the future, and less on criticizing Apple for leaving the past behind.

Steve Jobs
April, 2010

One More Tap » Apple

Thanks, Steve.

Related Posts

Screencasting Using Display Recorder for iPhone, iPad or iPod touch [Jailbreak Only]

Related Posts

iOS 4 Multitasking and Your Battery Life

Related Posts

Apple Strikes on Social Media

Related Posts

Steve Jobs’ Thoughts on Flash

Related Posts