Multiple iOS Simulator Instances

If you do any type of web development, more than likely you will need to check your code on various iOS devices. The iOS simulator is great for this, but generally you are trying to check your layouts against multiple screen sizes, and the standard simulator only gives you one device at a time, with no possibility of viewing two devices side-by-side.

I created a little script that runs as an application which will launch two instances of the iOS simulator so you can view two devices at once!

Prerequisites– OS X 10.9.4+- Xcode 6.0.0+

Using MultiOS Simulator.app1. Unzip the app and move it to your Applications folder (or wherever you want)2. Launch MultiOS Simulator.app. (You will see the error below. Simply click “ok” and move one of the simulator windows to the side to reveal the second instance.)

  1. *Important Select each simulator window and choose a device for each. Menu —> Hardware —> Device.
  2. *Important You must use 2 different devices. Running two identical devices will not work (this is what causes the initial error above).

That’s it, have fun! Hope this is helpful. Feel free to reach out with any questions / comments.

Note You may need to Right Click the application and choose open the first time you launch it.

Download MultiOS Simulator

Download Source on GitHub!

Enyo or Eny(N)o?

I have hit a fork in the road. A week or so back I decided to port a project of mine over to the Enyo framework. Enyo looks to be a perfect fit for this application and its intended use / audience. Today I had one of those moments of panic when you find yourself too focused on the present and not enough on the future. I had to ask myself that sobering question, “what is the track record of this project?” After the horrendous handling of WebOS by HP, that lead to its demise, can Enyo ever get off the ground with HP still attached? Or is this a truly new beginning for the excellent product that was once know as WebOS?

If I port to Enyo, I will be getting into the platform at the ground floor, much as I did with WebOS. This has many positives, but as we have seen, can lead to harsh negatives as well. In the case of WebOS shutting down, the very successful app I had in the Market was left to die as the dev tools were never updated to work with current versions of OS X. This left me with no choice but to open source the project and move on. Granted, being a web framework, it would be less of a pain to pack up and move out, but avoiding that scenario entirely would be ideal.

What to do, what to do..

What would you do? What mobile web frameworks do you use? Comment below!

Browser Testing

A couple months back I decided to see what it was like to use various browsers. This was mostly to see if I was missing anything. At the time I was using Google’s Chrome browser, so I was going to try the other 2 in the top three. Of course the top three are Chrome, Safari, and Firefox. You may be thinking, “what about Opera!?”. Well that is a browser, but that’s like saying a Blackberry is a smartphone.I set out to try Safari and Firefox for a full 30 days with no other browser being looked at during that time. I tried Safari first, and then moved to Firefox. Here is the short version of the results.

SafariPros: Bookmark sync with my iPhone and iPad.Cons: It handles tabs weirdly, just couldn’t get used to it.

FirefoxPros: Has pretty good syncing across multiple computers, and an iPhone app.Cons: MEMORY LEAKS!!!! OMG! It was not uncommon for this thing to use over 1GB of memory! WTF!?

Winner: Chrome!

As I write this I am using Chrome again. I really don’t have any complaints about the browser, it really just feels like it is doing it right.

What do you think?(flame me for the BB comment below. After that, tell me how good your blackberry is at email!) 🙂