July 2010 – Stay N Alive

Sources Confirm Location of Twitter’s Utah Data Center

It’s pretty much confirmed at the moment.  Twitter, according to just about every employee at SEO.com and the people running lines to the building, is building their Salt Lake City-based hosting facility in the old Linux Networks offices right next to SEO.com in Bluffdale.

Shortly after my last post about the new job opening in Salt Lake listed by one of Twitter’s employees over the project, a flood of tweets and comments from employees at SEO.com, a well-reputed search marketing company in Utah all reported they were seeing activity in the old Linux Networx building next to them.  After some questioning, Ash Buckles, SEO.com’s Director of SEO confirmed via direct message on Twitter that 3 different workers laying line from the street to the building had confirmed that the building was indeed Twitter’s.  While still hearsay, I’d say that, in addition to other confirmations by the Salt Lake Tribune (thanks Joseph Scott), pretty much gives us a solid witness by multiple sources that is where it will be.  The kicker is it’s right next to “Camp Williams” (Twitter’s CEO is Ev Williams).  Of course it’s right next to a major Prison as well.

Linux Networx was acquired by SGI in 2008 as it closed its doors and laid off all its staff.  Linux Networx was a company that built HPC Clustering solutions, and based on some of the employees I know that have worked there, had some of the smartest employees I’ve ever worked with.  The building has remained mostly vacant since then.  It appears that Twitter very well could be changing that, with “large cranes”, “lost power”, and all sorts of construction happening at the complex as it prepares its expansion.

As I mentioned earlier today this is great news for Utah as it refills what was once a vacant building from laid-off workers and again re-employs many more for a well-recognized brand around the world.  Twitter will join the NSA, Ebay, FamilySearch.org, Ancestry.com, and Oracle in adding major hosting facilities to Utah’s already rich line of talent and economic solutions.  In the end this is great news for Twitter too, as it can hopefully finally accomodate its ever expanding user base as it grows globally at an immense scale.  One can only wonder what other companies will follow suite?

I have contacted Twitter for comment and am awaiting their response. (Update: Twitter’s response was, “we’re not commenting on the location of the data center or any other details outside of the info included in our post last week.”)

Image Courtesy Google Maps

Twitter Opens Up First Job Opening for its Utah Data Center

Just a few days ago, Twitter announced it was opening a new data center in Salt Lake City, Utah in order to expand its ability to accomodate its ever growing user base.  The announcement was still somewhat vague, not specifying much about how many local jobs would be available and where in the Valley the new location would be.  Just a few days after the announcement Twitter quietly revealed a few more details about that announcement by announcing a “Site Operations Technician” position in the Salt Lake City area through one of its employees.

In a post by Twitter employee, Brady Catherman, who lists on his LinkedIn profile as an Operations Engineer at Twitter (and graduated from the University of Utah), Brady told his brother who lives in Salt Lake City to send people to an unlisted page on Twitter’s job site advertising the job.  The listing doesn’t appear in the main list of Jobs however.  The job is still rather vague, but due to the fact no management positions are listed or were mentioned, it leads one to believe Twitter has either hired them, it will be through a third party, or Twitter will be moving some of their own employees over to manage the process.  Based on messaging by employees, it would seem to be the latter, as Catherman’s brother, Bryan Catherman, implied on his Twitter profile that his brother “would get to leave his Twitter office and visit often.” He also implied that it was his brother doing the hiring for people out here.

Where will the new operations center be?  In a response to Mark Nielson, Bryan Catherman also stated that it would be at the “South end of the Valley”, “easy access from I-15”.  He wasn’t willing to reveal any more info when I asked, but that would probably put the center somewhere either around Riverton (where there is still lots of real estate), or perhaps Draper or even South Jordan or Sandy.

Utah is known for its superb hosting accommodations.  With the high altitude, dry air, and cool climate, costs of hosting are very low for most hosting facilities.  It is the site for a massive NSA hosting facility in the West end of the valley, as well as home to other hosting locations for Ebay, and the billion-plus record database inside the Granite mountains on the East for FamilySearch.org.  As the home to the start of Wordperfect, Novell, Omniture, FreeServers.com, and home to 2 major Universities within an hour of each other (BYU and Utah), Twitter will also have no problem finding talent here.

Having a new hosting facility in Utah is an exciting thing for those of us that live here.  It is just one more proof that confirms the recent claim that Provo, Utah (near Salt Lake City) was recently named the 9th most innovative city in America by Forbes Magazine.  It is also one more confirmation that I have said before that the Salt Lake City area is one of the top tech and startup hotbeds in our nation right now.  I hope more tech news outlets are watching this and noting this great add to the already amazing talent we have in this area.

If you have any more details about this announcement, please e-mail me at jesse@staynalive.com or feel free to mention them in the comments.

Texas Proves Once Again Everything is Bigger, Even on Facebook

If you ask which State is biggest on Facebook, at least if you ask a Texan, the winner would be Texas. Today at about 11:30pm Central, the Facebook Page, “I bet Texas can get 1 million fans before any other state.” did just what it set out to do – it became the first Facebook Page for a State to get 1 million fans on Facebook.

The Page went up against Pages like “I bet Alaska can get 1 million fans before any other state.”, and “I bet New York can get 1 million fans before any other state.”  Texas was the clear winner.  The biggest one I could find was New York, with only about 200,000 fans.  Looking through AllFacebook’s Page rankings, there were no State pages above Texas.

The enthusiasm for the state is evident.  The accomplishment was met with comments like, “cool now can winter come?????? lol”, “YEP CUZ TEXAS IS THE BESTEST!”, “Lets go for 2 million now!”, and “i think that texas should just be its own country”.  You may even see some of your friends partying and waving their Texas flags and holding up horn signs tonight as a result.

It’s hard to tell if any other state really tried, but if you’re a proud Texan like myself, tonight is a glorious occasion.  We have dominated all y’all!  Let’s go light a bonfire, say the pledge, eat some jalapenos, and cook some brisket!  I’ll be hanging my Texas flag proudly tomorrow.  And starting today we can all join this man in understanding our state’s bird, tree, reptile, and yes, now the official Texas Facebook Page which is way better and bigger than y’all’s:


Don’t Mess With Texas.

Buzz Opens the Firehose With New API Features

Just a few minutes ago, on his Buzz update stream, Google employee DeWitt Clinton announced that Google had opened up their real-time stream of information for Buzz. Now, any application can access, in real-time, all updates across the entire service as they come through. This incredible stream of information will serve useful to Data warehousing and collection apps such as PeopleBrowsr and others that provide images and statistics surrounding the real time streams of Social Networks.

In his update, Clinton describes that the entire API was built around Pubsub Hubbub (PSHB) by Brett Slakin and John Panzer, and also integrates Atom and ActivityStreams standards as part of the integration.  In addition, new API methods to retrieve all the comments and likes of any user were also added to the Buzz API.

Even more significant is the addition of Share counts for any given URL.  Now you can expect to see services such as TweetMeme provide widgets that show and track the number of times that URL has been shared on Buzz and the ability to click to share even further.

In what seems like a long lull of time since any updates on the Buzz API or service, these changes are refreshing.  I think there’s no doubt the Buzz team is working hard to make this platform special and we’ll continue to see results in the near future.

What other API features would you like to see from Buzz and its API?

To Whom Much is Given, Much is Required

Just the other day a kind Single mother was nice enough to share a story with me about how, as a newly Single mother, one of my books had helped her get off the ground and start her own business.  It’s something I never thought of before, and I admit, I was very touched (and still am).  I think some times we don’t think about the potential of what it is we share and do with our talents and knowledge.

I just found this video about a High School girl with Muscular Dystrophy whose fellow Cheerleaders thought of what being a Cheerleader would mean to someone who would otherwise never have the chance.  It made me think about how important it is for us to be thinking about those around us.  When we are given talents and strengths, are we using those strengths to also strengthen those around us?  Here’s her story:


Yes, I cried too.

Breaking Down the Signal – The Android, iOS, and WebOS Comparison

There’s no shortage of criticism, complaint, or praise of the various mobile operating systems. The iPhone, Android, the Pre, or even Blackberry and Windows Mobile – no matter which phone you review you’re bound to find someone who either absolutely loves the device they own or completely hates those that do. I tried to make this known in my previous article on my preference towards iPhone, stating the features I liked about it and showing why, despite connectivity issues I thought it was the best phone I’ve tried. I thought it was worth stepping back even further though.

I realized very quickly after my previous article that nothing I said was going to sway those that had already made the Android choice, or the Pre/WebOS choice, to switch back to the iPhone. So I decided not to fight it – here I’m going to take some time showing you the different devices I’ve spent significant time with, what I liked about them, and what they lacked.  Then I’ll let you make the choice on what phone works best for you.  You might notice there aren’t many articles like this – that’s because they take a lot longer to write and involve a lot more research.  This one is no exception.

The Experiment

I’ll admit, my experiment wasn’t the most scientific one could muster.  But I will tell you I own 3 phones currently.  The first, my work phone, a Palm Pre, which I’ve now owned since March.  Secondly, is Apple’s iPhone 4, my main phone where I forward most of my calls now, and recently replaced an iPhone 3GS (my wife having previously owned the iPhone 3G).  Lastly, I have the HTC Evo, a test phone I borrowed for a month or so from work so I could understand Android better.  My hope was to try to play with the Android products my employer creates in order to design and build Social architecture and end-points into that experience (which is what I do for a living).  I am also forwarding all my calls to that phone, through Google Voice.  In addition to that, I have access to a Droid Incredible which gets passed around at work, as well as a Blackberry, which I admit I’ve never really touched (nor do I have much desire to play with – I’ll leave that for others to review).

So, the three phones I put to the test were the iPhone 4, the HTC Evo, and the Palm Pre.  The minimum amount of time I’ve used any of them has been 2 weeks (the Evo, just barely newer than the iPhone 4).  I have carried each for a significant amount of time, playing with them, answering calls, making calls, and trying to get to know the features.  I’ve also been trying to get to know the development environments of each as I try to learn the advantages to each development environment.  I think I’ve given each phone a fair amount of time to try to have a good understanding.  So let’s go into the features, and I’ll let you be the judge:

Palm Pre

Hardware Features:

Let’s face it, the Palm Pre just feels good.  When you hold it, it naturally feels good in  your hand.  Being one of the only mainstream Smartphone devices with a keyboard, I admit that’s an advantage, not a weakness.  I have yet to find an on-screen keyboard that you can type on and know what keys you’re typing without looking at the phone.  With the Pre, you can almost do that.  The Pre, when you slide it open to reveal the keyboard (without, it just looks like a smooth eggshell), has a mirror that you can use to either look at yourself, or see yourself if you need to take a picture of yourself.

The Pre doesn’t have a front-facing camera, and the rear-facing camera is far from what the Evo or iPhone 4 can provide.  The other failing part of the Pre is that due to its plastic casing it wears down after about a year or so.  I have several friends all with Pres and each one of their phones after a year or so starts to show a lot of wear, and even issues when sliding the case open and shut.  That’s part of the problem, the more moving parts you have.

The battery on the Pre is also pretty good.  With little use, you should be able to get away with charging it only ever other day or so.  Using it as a hotspot, you’ll have to charge it much more frequent.  It definitely lasts much longer than my Evo.

As for signal, Sprint in general provides a pretty good signal.  The building I work at has repeaters throughout so it’s a tough comparison, but at home I haven’t had many issues, and even taking to the Bay area I always treat it as my backup phone because I know I can always guarantee a signal there.  The Pre is a pretty reliable phone, in terms of hardware.

The other thing I really like about the Pre is you can also purchase the charging stone that works with it.  With that, you can simply place the phone on the stone and it charges, without any need for connecting wires.  This saves countless charging cords and keeps its smooth look as you don’t have to open the little charger opening on the device.

The Operating System:

The Pre is hands-down the most beautiful operating system out there right now.  Even Steve jobs gave note to it in their recent press conference.  The Pre has just one button (other than the default volume controls and mute switch), which shows you all the programs open at once when you press it.  However, it also has a gesture where if you swipe backwards, it always goes back to the previous screen you were on, and if you swipe forwards, it goes forward to the next screen.  This works in applications as well.

Let’s not forget that the Pre and WebOS was the first operating system to support true multi-tasking on the phone.  Even today its interface is the one that seems to make the most sense.  At any time you just press the main button on the phone and all your open applications pop up as windows on the phone.  If you want to go to one you just select it.  Want to surf through the open applications? Just swipe left or right and you can see all the open “screens” for your applications.  If you want to close any, just swipe the screen up and the application gets flung off the canvas, closed forever.  It’s a very natural interface that anyone can get used to.

As for the rest of the operating system, well, it’s all based on Linux so it’s very open and very customizable.  I have a friend who completely removed his default browser and other apps in the phones he gave to his kids so they couldn’t access the internet.  It’s that open.

They’ve taken developers to heart, and even enabling “developer mode” on the phone is a matter of just typing in the Konami code (“upupdowndownleftrightleftrightbastart”) in the search bar.  Doing so enables a whole host of features, enabling you to get access to a shell and the heart of the phone.  There is also an entire “homebrew” community of applications not officially in Palm’s app store that you can easily install on your phone.  My coworker even showed me how to view the source code on these applications – the entire experience is very open to the very core, something not quite the same as Android, also Linux-based.

With developer mode enabled you can also enable tethering on the phone.  Searching for it reveals all sorts of articles on the subject, not requiring much effort.  The great thing about it is neither Palm nor Sprint seem to object to the hack and openly encourage the homebrew apps such as tethering.  The entire experience is, well, beautiful.


As I mentioned, the entire application experience on the Pre is a very open experience.  Palm makes the entire developer SDK free (normally $99 to closed-source apps) to developers willing to developers willing to make their code open source.  Developers of such apps are then required to release their code to the community under open source terms they specified.

The application experience, while not quite as consistent as the iPhone’s (iOS), still makes fairly nice apps.  With the surrounding OS, they still look beautiful – the OS makes everything on the phone look beautiful, so ugly or not, the application should not affect the overall experience.

The main problem I saw with applications on the Pre was the lack of them.  While in general, I was able to find something for every need I had, the main vendors weren’t always producing my favorite apps for the phone.  Things like TomTom, Sling, and others may not ever provide apps for the phone, so the high quality apps may never make it unless there is a viable amount of competition.

In addition, because the Pre no longer supports iTunes (previously they had found a hack to be able to make iTunes recognize the phone), there is no default music player for the device.  Therefore if you’ve bought all your music on iTunes you’re out of luck syncing with it.  It does work well with solutions like DoubleTwist, so there are alternatives, and I didn’t find the lack of iTunes support to be that big of a deal.  It will be less of a deal if cloud-based apps like Spotify start supporting the OS.  That said, the apps were my biggest turn off for the Pre.

Development Environment:

Pre had my favorite development environment of the 3.  Since most native apps support plain HTML, CSS, and Javascript (that’s why it’s called “WebOS”), it’s dirt simple to learn how to develop on the device.  You can use the HTML/CSS/Javascript model, or even port your C/C++ apps into the phone, making porting of heavy OpenGL apps to the phone from iPhone and other devices simple.

The SDK doesn’t have an incredibly powerful IDE experience like the iPhone’s InterfaceBuilder, but it is still sufficient, and since it’s just HTML and Javascript, not a very difficult thing to manage.


Hardware Features:

The Evo is a machine.  From its huge size to its heavy processor, it’s built to run things fast.  Out of the box it comes with a 1GHz processor, an 8MP camera, 1.3 MP front-facing camera, an FM Radio, and more.

It’s much bigger than the other phones.  I don’t know if it’s the size making it a psychological thing, but it feels much heavier, too.  That’s probably one of the biggest downsides in my opinion.  It’s a clunker.

The phone reception is pretty good, and boasts 4G speeds on Sprint’s 4G network if it’s available in your area.  I was able to get up to about 5Mb/s on mine, and the web experience is very snappy.  In fact the entire experience is very snappy due to the speed of the processor.

If anything, I’d say the hardware is the main reason to get this phone (minus the size), except for one thing: the battery.  The battery life is horrible!  It makes the phone unusable, and goes dead by noon each day when you enable 4G on the phone.  When 4G is off, it only lasts until about 2pm each day before having to recharge (my measurement of battery life is by what time you have to recharge it after the time it is fully charged in the morning when I disconnect it from the charger in the morning).  Unless you’re willing to carry a charger around with you, this phone will be very difficult to use.

The Operating System:

The Android operating system, like the Evo, is clunky.  Everything is very boxy and not very smooth.  When you scroll the UI is shaky.  I get error messages from the operating system about applications crashing all the time.  While the hardware may make up for it on the Evo, the operating system really ties down the potential of the hardware.  I hear much of that will be changed in the Gingerbread version of Android, which I have yet to see.  At the moment the user experience is far behind its two rivals I’m reviewing here.

The one thing I really like about the Android operating system is the tight integration with Google products.  It works seamlessly with Gmail.  It works seamlessly with Google Voice.  Many of Google’s other products are all integrated tightly into the operating system.

In addition, Google includes deep integration into Facebook and Twitter and other social networks, right in the operating system.  However I think you will find greater benefit from dedicated social clients like Seesmic or Tweetdeck or the Twitter app.  I don’t think the Social Integration is enough to push one over the edge, at least not yet.

The Android OS, like WebOS, is very open.  Being Linux based, you can do many things as a result, offering many customizations you can’t get from the iPhone.  That said, whatever you do, you’re still tied to the flavor of Android your provider has given.  I’m not sure if Sprint has blessed hacking the Evo or not, and how tightly they’ve locked it down.  That’s all up to the phone manufacturer and the cell phone provider.


Android has a very rich application environment.  While there are still not near as many high quality apps as the iPhone, the number for Android is steadily increasing at a rate faster than the iPhone, and will probably exceed the number of applications the iPhone has at some point.

That said, the application experience on Android isn’t nearly consistent as the iPhone’s.  Applications are bulky, crash often, and don’t have nearly as beautiful a UI as the iPhone.  The approval process for Android’s store isn’t nearly as strict, so you’re likely, when searching in the app store to find a kid’s app right next to a porn-related application.  You’re likely to find very amateur applications, and my bet is at some point the majority of applications built for Android (if that is not already the case) will mostly be those types of applications.

I find the Android’s application experience to be sub-par to that of iOS.  That’s not to say it will always be that way – it’s just the way it is now.

Development Environment:

I really like the approach Google took with the Android application development environment.  It’s a Java-based environment, something just about every programmer has had some experience with since they teach it in most schools as the beginner class.  The development environment will be very familiar to most developers.

In addition, there aren’t near as many hurdles a developer will have to go through to get their application in the app store.  It’s a relatively pain-free experience, and Google is making that even easier with their recent Scratch-like App Builder that anyone can use.  It will be very simple.

Registration for the app store is $25 – there is no open source program like WebOS.  However, the SDK is free for download to anyone, and the entire operating system source code is also made available online.  It’s a very developer-friendly operating system.  Perhaps that’s its greatest weakness, though.

Apple iPhone 4

Hardware Features:

The iPhone 4 is simple and sleek, plain and simple.  Similar to the Pre (with the exception of the Open Source part), since Apple also controls the hardware, they have the added advantage of seamlessly integrating the entire hardware and software experience to work well with each other.  It’s hard to not talk about the hardware without mentioning the software, and vice-versa.

The size of the iPhone is just perfect – it’s smaller than the iPhone 3Gs, not much lighter though.  It fits in the palm of your hands just perfectly, and its glass exterior is very beautiful.

The phone comes with a 1.4MP front-facing camera, making it slightly better than Evo’s, and 5MP rear-facing camera.  Despite the camera being lower resolution than the Evo’s 8MP camera, you won’t be able to notice.  In my comparisons of the two side-by-side in various environments the iPhone 4 produced far superior photo and video quality than the Evo.  The difference is very noticeable, and Apple seems to have really compensated the hardware with software.

In addition to the superior cameras, the Retina screen completes the experience, with absolutely the best phone picture I have ever seen.  Using this phone will make you want to read books on it, just so you can see the pristine quality of the text and images on the phone.  It’s absolutely fun to take pictures and video on the device because they look better than most other monitors and TVs I have in my home.  It’s a beautiful device, through and through.

The phone has a similar processor speed to the Evo, however Apple made their own processor so I’m sure there are some advantages there.  The operating system through and through is very snappy and smooth as a result, providing for a very seamless experience.  The phone also comes with 16GB or 32GB of memory that isn’t limited to music or apps, which is different from most Android devices, which only allow you a limited amount of space for apps, leaving the rest for music and data.

The battery life on the iPhone 4 is amazing.  It’s not quite at the level of the iPad, but still the best battery experience I’ve had on a phone so far.  I can keep it running all day with normal use and not have to recharge it until the next day or even later.  You will not be worrying near as much about recharging with this phone.

Then there’s the part that seems to get the most press – the connection.  I noticed the connection problem.  I was able to reproduce it (but I admit it would have taken me longer to notice all this had the media not been all over it).  Very occasionally I see a dropped call which I didn’t see on the 3GS.  That said, it just doesn’t bother me.  The phone is still useable, even without the bumper.  Adding the bumper seems to make most of the problems go away, and in fact, the black bumper almost makes the phone look a little better.  Given the fact that Apple is giving these away free now, it seems like it’s almost a non-issue.  That said there will be people in areas with even less connectivity that will have “the AT&T factor” – this will always be a factor so long as Apple is tied to AT&T and it’s one worthy of considering.  If you normally have issues with AT&T and don’t want to deal with them, maybe this phone isn’t for you.

That said, I think the new antenna actually improves the internet speeds.  When combined with the faster processor, the two seem to work very well together and provide a much faster web experience than the iPhone 3GS.  It’s actually somewhat comparable to the Evo from what I can tell (that’s without detailed experiments).

The Operating System:

iOS is, well, iOS.  It’s the Apple experience.  It’s simple.  There’s not much to it.  You have one button and a bunch of icons to click on.  That’s why people use Apple.

iOS 4 is a very smooth experience, only amplified by the iPhone 4’s beautiful Retina screen and faster processor.  Multitasking, once you figure it out and as applications start to adapt it, makes things much easier.  You open an app and it opens right to the place you left off.  There is a bit of a learning curve in learning the multitasking features though.  Once you learn to double-click that home button you’re in multi-tasking heaven.

Folders makes things much more organized, with fewer swipes if you have a lot of apps.  The biggest issue with folders is figuring out how to add applications to new folders and create new folders (you do so by just swiping an application icon over to another icon or folder).  Once you figure it out though, it “just makes sense.”

The new HD camera features are very slick.  With the still camera you can now zoom and pan.  Zooming reduces picture quality, and one won’t want to do it too often if you’re looking for high quality photos.  However, I’ve found using some of the apps like Pano or auto-stitch with the new camera make for a very beautiful photo experience.  HD video is amazing, and being able to auto-focus by clicking on anywhere in the picture while you are shooting video makes for a very professional-looking video that focuses and unfocuses just like a professional video camera.  The video shoots at 30 fps, which is the same as my more professional Canon Rebel T2i camera.

Oh, then there’s FaceTime.  Yes, there are apps on the Evo (and even the iPhone) with similar functionality, but the deep integration into the operating system makes all the difference.   It’s almost too convenient to video call your friends, and I find myself reaching for that FaceTime button whenever I can and I know my friends have an iPhone 4.  That’s also the biggest problem – knowing when your friends have an iPhone 4.  Hopefully more devices start to integrate with this and it becomes more of an open protocol than it is currently.

The operating system for the iPhone 4, in conjunction with the hardware makes it simply beautiful – it’s something you must experience to gain the full benefit.


Applications are Apple’s strength.  The benefit Apple has is it gets to add hardware features that applications can take advantage of as part of the experience.  With the iPhone 4 the photo applications are all going to be better, and I wouldn’t doubt there will be a slough of video editing apps that come out as a result.  Already, you can purchase Apple’s iMovie app and shoot and edit your movies all on the iPhone.

The application experience on the iPhone is always going to be consistent.  Apple reviews all applications thoroughly and ensures they all maintain a somewhat consistent look and feel that is consistent with the Apple brand image.  They are all about their customer and they want that experience to reflect even through to the applications that are installed on the phone.  If you have a bug that they notice, they won’t approve it.  If you aren’t consistent with their standards, they won’t approve it.  That’s simply the Apple way, and if you don’t agree, there’s always the web browser.

That said, some criticize the lack of being open as Apple’s weakness.  Currently tethering costs money because of this weakness.  It wasn’t even available before.  The customer is stuck waiting for Apple to release new features and approve new types of applications as a result.  This is frustrating for some.  For me the peace of mind that the experience will remain consistent is comfort enough for me.

Development Environment:

The development environment is somewhat consistent with the application strengths and weaknesses.  Because Apple wants to remain consistent, developers often get shut out.  If Apple doesn’t like your app, they won’t approve it.  Some developers aren’t even told why Apple doesn’t like it.  Others are left hanging waiting for their apps to be approved.  That said, the majority of applications, assuming they follow Apple’s terms and rules, will get approved.

My biggest beef with the development environment is Objective C – it makes me want to poke my eyes out.  It’s a purely object-oriented language that deals with events and other weird language paradigms most modern-day developers aren’t going to be familiar with.  Its InterfaceBuilder GUI IDE isn’t like visual tools such as Visual Basic.  You have to create a prototype, then re-duplicate most of that prototype in code later.  It’s a pain to deal with.  There’s a huge learning curve.  It’s one of my biggest hurdles towards developing for the iPhone.  That said, once you learn it, you’re in high demand and you’re producing high quality, highly usable apps in a beautiful environment.

The Verdict

Looking at the 3 phones, comparing hardware, software, applications, and development environment, I have to choose the iPhone 4.  It’s the best phone I’ve ever owned. Better than the other phones and barring a few weaknesses, everything just flows together and looks beautiful when you use it.  It feels natural to my every day workflow.  The Pre isn’t a strong enough device.  The Evo is too bulky and cludgy and buggy.  Not to mention the battery life making it practically unusable.

If I had only the choice of the Evo and the Pre, I would probably chose the Pre.  The Pre’s UI and overall experience far trumps the Evo’s.  The hardware isn’t quite as beefy as the Evo’s, but the software really makes up for it, and especially in recent OS updates, doesn’t have many speed issues you notice.  It also feels nice in the hand and is easy to carry around.  I like WebOS far better than I like Android.

If I absolutely had to choose Android, I don’t think I’d go with the Evo.  We have an Incredible laying around the office that is much smaller in form factor and almost as fast.  The battery lasts much, much longer than the Evo’s.  My choice of Android devices, at least at the moment, would be the Droid Incredible.  My iPhone’s battery still lasts longer, amongst the many other advantages it gives me.

So with all those details in mind, I hope you can see why I chose the iPhone 4.  If I had to recommend one device, it would be the iPhone 4 – it has the best experience, the best hardware, the best software, and despite a few connectivity issues and hurdles into the App store which the end user barely sees, it is absolutely the best mobile device I’ve ever owned.

I want Android to prove me wrong though.  I want HP/Palm to prove me wrong.  Heck, I want Microsoft to prove me wrong.  I hope they produce something better at some point – it could happen.  However, at this point in time, put side-by-side, my overall recommendation would be the iPhone 4.  If you’re a device manufacturer and think your device might be better, send it my way and I’ll do a review of it.  At least now I’ve set the bar and hopefully someone can make something better.  And hey, if you can do a better comparison with the phones you use, I’d like to see.

Disclosure: The iPhone was the only phone I paid for in this experiment.

LDS Church Launches New, "Social" Mormon.org for Learning About Mormons

mormon.orgJust last night, The Church of Jesus Christ of Latter-day Saints launched a newly redesigned Mormon.org to help those that are not members of the LDS Faith to know who their Mormon neighbors are.  The site, which takes a more “Social” approach to learn about the Faith, attempts to show you who your Mormon friends are, by letting them tell you about the Church.  The effort is perhaps one of the most social efforts from a technology standpoint in Church history.

Browsing the site, visitors can immediately search for people with like interests, locations, and ethnicities, showing that no matter where you are or what type of life you live, there is probably a Mormon who has been in, or is currently in similar circumstances.  In addition to being able to search around you, prominent Mormons are also featured, and you can learn about such influential Mormons such as Jane Clayson (Johnson), former morning show anchor and Journalist, or Chris Carlson, Creative Director at the Library of Congress.

The site features testimonies of members, answers to questions, videos, and information all about the Church, mostly by members of the Church themselves.  It includes very interesting and entertaining videos about featured members, which are scattered throughout the site and you can embed on your own website or blog.  The profiles are all written 100% by members, and include links to Twitter, Facebook, and even blogs that the members may write.  For each article about the Church (such as this one on Jesus Christ, or this one on The Book of Mormon), visitors can share and like the articles on Facebook and Twitter or e-mail.

So if you get a chance, head on over and check out the site – look for people like yourself.  Look for people that live around you.  There’s a good chance one of them is a Mormon.

You can read my profile here: http://mormon.org/me/1H2Y-eng/

My name is Jesse Stay and yes, I’m a Mormon. 🙂

Disclosure: In my day job, I am currently working as the Social Media Architect for The Church of Jesus Christ of Latter-day Saints. While they are currently my employer, this article by no means represents any official announcement, declaration, proclamation, or doctrine on behalf of the Church.  All claims or topics written are solely my own opinion and not the opinions or official word of the LDS Church.  To be clear, regardless of my day job, I am still a member of the Church and I still believe its teachings and will always have beliefs to share surrounding the Church and its teachings.  What I write here should be considered as such.

Name a Better Phone

Let’s put all partialities aside.

Currently, I own an iPhone, an Evo (which I’m borrowing through work for testing), and a Pre (my work phone).  I have been a Windows user most of my life, and spent 2 or 3 years with Linux on my desktop.  In the PDA days I ran a Palm Pilot, a Handspring Visor, and a Dell Axim (Pocket PC) device.  In all honesty I don’t care what the brand of the device is that I use – I care that it gives me the best experience for my money and will provide the same for my family.  At the same time my experience may be different than yours.  You may need something cheaper.  You may not need a camera.  You may just need the phone features.  All these factors go into the purchase of a cell phone.

Yet, when Consumer Reports says that it can’t recommend the iPhone 4 as a whole simply because of one feature, when it rates it higher than the competition on every other test, I call foul.  Something’s fishy in this review.

Partialities aside, when you rate phones, as a whole, feature-by-feature, side-by-side with the other phones that I own, the iPhone 4 still outperforms them, hands down.  Even Consumer Reports confirms that. The iPhone 4 takes better pictures than my Evo.  It takes better video.  The iPhone 4 has so much better screen quality than my Evo.  I can edit my movies on my iPhone 4.  The iPhone 4 lasts at least 3 times as long in battery life than my HTC Evo.  The iPhone 4 has a better, more consistent application experience than my Evo.  There’s simply no comparison on those features.  The iPhone beats the Evo in user experience and simplicity (My 2 year old has issues with the Evo – he has no problem with my iPhone).  It has better parental controls.  It has a much smaller, easier-to-hold form factor.  It has FaceTime, and before you say the Evo has apps that do that, the Evo has not integrated it into its Operating System and phone book, and that’s a huge difference.

Now let’s look at the Evo.  True, the Evo does have better call quality.  That’s perhaps the one advantage that matters to me.  The Evo has better Google Apps integration, although that’s not as big a deal to me either since at work we don’t use Google anyway. (and the iPhone 4 is good enough)  The Evo has social integration built in, but except for the hard-core techies and Social Media geeks, this simply won’t matter to the majority of the world, and the iPhone 4 has better apps to handle this anyway.  What else can the Evo do better?

I know you’ll bring up the issue of Choice.  I’ve covered this before – it’s a valid reason, but I ask you to define choice.  Can I run my Evo on Verizon, and run Verizon Android phones on Sprint?  How easy is it for you to switch services with your Android phone?  Can I port my iPhone Objective-C based apps over to the Android marketplace?  No matter what, there will always be elements of the OS you can’t port, and there will always be limitations in choice. History doesn’t change, so long as one company is controlling the infrastructure.  At the same time, no one is stopping me from Jailbreaking my iPhone to get the extra features I might want, should I want them.  Sure, Apple makes it harder, but that’s not stopping people from doing it.  There will always be some form of choice no matter what phone you’re using.

I don’t get all the bashing by mostly people that don’t even own an iPhone 4 based on solely connectivity issues.  I use my phone with my left hand.  Yes, I notice and can reproduce the reduced signal, but it simply isn’t that bad.  Especially contrasted to all the other amazing features I get from the phone.  Yet at the same time, Consumer Reports admits they didn’t even test it with the recommended case that Apple suggested all iPhone 4 users purchase.  Since Apple suggests that to fix the connectivity issues, I would definitely just consider that as part of the purchase price – it’s still a cheap phone!

I don’t understand all the negativity and targeting of the iPhone, asking for recalls and such because of simple connectivity problems.  I still think most of the vocal critics are all people that don’t even own the phone.  For those that do, go get a bumper, for goodness sakes!

And if you still refuse – I remain to ask: Name a better phone.

When that phone comes I’ll be all over it.

Facebook Kills Custom Publishers – Kills 15,000 of My Users Too

What’s a lot for one site may be miniscule for another.  Recently, Facebook announced they were removing the ability for developers to write custom Publisher boxes “due to low usage” of the feature on the site.  The feature, which enabled any application to customize the publishing experience for users, was a little-known, and little-advertised feature known to produce a good amount of traffic for applications.  It was a successful feature though, and perhaps “best-kept secret” for many developers writing for Facebook Platform.  Shortly after it launched I remember a few developers writing about how just a few tweaks to the custom Publisher and adapting the experience to each user provided tremendous conversion in application adds for users.  I was sold.

On SocialToo, one significant tool we provided was the ability to, using the custom Publisher (which is still working now, until Facebook turns it off), allow Facebook users to publish to any Twitter profile, and any Page they administer, just with a few checkboxes attached to the Publisher box at the top of Facebook.  This way users with a preference towards Facebook (which, despite the popularity of Twitter in the blogging world, is very popular amongst marketers) could easily publish to their multiple accounts on a selective basis straight from their Facebook profile.

This was a huge success for me on SocialToo – so much that despite the majority of our features being Twitter-focused, this one small feature was bringing in a significant amount of conversions for me.  Users would authorize the SocialToo app, get the publishing feature, and at the same time learn about the other tools we provided for Twitter and elsewhere on SocialToo, purchasing our premium features straight from Facebook.  20% of my traffic came from Facebook as a result.  Near 15,000 of my 70,000+ users were using the application.

Yet, according to Facebook’s response on a developer forum post, they seem to be looking at mostly usage of the Publisher, not net-effect towards conversion (which is why developers were using the publisher – it was an advertising tool for their apps).  According to Facebook:

“We understand that the publisher feature was successfully used by some developers and enjoyed by users.  While it’s never easy to have a feature removed, we made this decision only after carefully reviewing the feature’s usage over time. For the sake of transparency, here are some basic usage stats that illustrate the approximate daily usage:
–          47 applications with more than 1000 stream publishes
–          10 applications with more than 10K stream publishes
–          0 applications with more than 100K stream publishes”

Usage of the publisher, number of publishes, etc. is an important factor, but Facebook still seems to be neglecting what those 10,000+ stream publishes per day were producing for those developers in terms of monetary value and overall conversions.  For my application, it was priceless.

I’m disappointed that Facebook is killing this feature.  I’m disappointed that they did it with such short notice and without it being on the roadmap they revealed at the end of 2009.  Yes, the numbers, according to Facebook, are small, but with only one document tucked away on the developers wiki devoted towards the subject can you blame it for being such a non-used feature?  From my own experience, the conversions alone it produced, and the utility it provided were enough to make it well worth the integration, and I promoted it to all my clients.

If usage was so low, it certainly wasn’t because it wasn’t useful or valuable.  It was because Facebook didn’t promote it or show the usefulness well enough.  Perhaps the API for it was too complicated – I don’t know.  I do know this is one of the many Facebook Platform features that have gone away that will be sorely missed.

I think one thing with Facebook Platform we can now be sure of is that while Facebook continues to increase usefulness of their platform on the web, their own website’s platform on apps.facebook.com is slowly being removed, piece by piece.  If this is the case I really wish they would put that on their roadmap.  As for the custom Publisher – this developer is drastically effected by its removal.