Reformed Software

Beware, hap hazard tech notes do follow:

So, warnings and precautions aside, it’s time to put down some notes on how to get going with ruby 2.0 and rails 4.0 in a new app. As of the start of these notes, ruby is 2.0.0-p195 and rails 4.0 is rc1.

The first step is to be wise and use a ruby version switcher such as rvm or rbenv. My preference is for rbenv, so the steps involved are using that.

Installing ruby 2.0

brew upgrade ruby-build

That will get you the latest ruby definitions for ruby and allow you to install them as part of rbenv.

rbenv install ruby-2.0.0-p195

If, for some reason you haven’t install openssl yet, that will complain. So, take two will involved

brew install openssl

Now, silly person, go and install ruby 2.0 via rbenv again.

CONFIGURE_OPTS="--with-openssl-dir=`brew --prefix openssl`" rbenv install ruby-2.0.0-p195

Install Rails

So, we are now good to go with ruby 2.0.0-p195. Let’s get rails 4.0 up and running and start building an app.

gem install rails --version 4.0.0.rc1 --no-ri --no-rdoc

Now. Make your rails app and remember to ‘Ship It!’

So, my brain is fried. That goes without stating having just returned from NTE (http://nte.org.au) for 2011.

Though, what does that have to do with the subject?

Well. Simply put. Everything. The first few people I talked to at NTE complained about the iPhone app. There was too much data required to get started. I thought it was all useful but they found it a hindrance.

Further, they complained that the values selected weren’t displayed.

You can present information in a lot of ways, but does it really communicate what you would like it to communicate. Does it convey the message you would like? Does it let people know what the next step should be?

These are basic things to do with usability that are often rushed. So my advice, to myself as well as to others is spend the needed time in working through the usability of the app.

Till next time.

Well, it’s that time of year again. Many students are gathering in Canberra in about 10 days to hear more about Jesus. But what does this have to do with software development?

Everything.

This year the students are able to get the most out of NTE by using an iPhone / iPad app that helps them to take notes while listening to the numerous talks which are being given. These include not only the main talks but also the electives and tracks.

Further, the students will know what’s happening as the app includes a complete timeline.

So what are you waiting for? Go get the app. http://bit.ly/nteapp2011

So having written an app for Super Summit run by Christian Union in Victoria (through whom I enjoy proclaiming the truth about Jesus to uni students during the day), there are a couple of lessons that I should learn from the experience.

1. What ever the project, how ever simple you may think it is, take your estimated time and allow yourself four times as much.
2. The little things count. Get the details right.
3. Go for stable and well known API’s and applications.
4. Set yourself goals.

Though, through the endeavour, which caused much stress due to unrealistic deadlines, I come out the other side waiting for Apple to approve the app. This is the second app I’ve submitted to the app store. Hoping that things go through smoothly and without any rejection.

I shall catch you on the other side of the approval.