Navflow Beta extended until the 30th of July
posted July 19th 2010A quick note, as a few people have asked, we are extending the Navflow Beta until the 30th of July. Please ensure you have concluded your testing and taken you results before then.
We will still be deleting all beta test data from that date. The new version will be up on the 31st as planned.
Major Update coming July 31st
posted July 14th 2010Introducing UsabilityHub.com
On July 31st we’ll be launching UsabilityHub.com. Usability Hub isn’t much at the moment, just a pair of web apps really. But it is the start of something bigger and better than anything we’ve done to date.
The goal of UsabilityHub.com is to provide a place for designers and developer to work together, share ideas and help each other improve websites and applications. It’s about providing a focal point for all things UX. We want it to be about more than just our applications, we want it to be a place where all designers can learn from each other, and help each other out. In the coming months we’ll talk more about what our plans are, but for now let’s just talk about what it means for our current applications.
Navflow Beta
Navflow.com beta will be finishing next week. All existing data will be deleted at the end of next week (23rd July). Where possible we will migrate user accounts across to the new system enabling you to keep your login in. Part of this migration is migrating our existing Fivesecondtest users. Obviously if there is a clash with your existing 5st account, we’ll keep your 5st account in preference over the Navflow beta account.
Five Second Test
We have a completely new Five Second Test which you’ll get to see very soon. Whilst we think our new site is better in all regards, we understand that a lot of people really like our existing system. Rather than delete it, we’re going to let you continue to use it! The old fivesecondtest.com will be renamed to original.fivesecondtest.com. So if you’re currently running tests there, don’t be scared that it’s all going to vapourise, you can keep on keeping on. Please keep in mind that the two systems are completely separate. Tests created in the old version are not available in the new, and vice versa.
Credit
Users with credit from Fivesecondtest.com will have their credit copied across to the new site. This will enable you to continue creating tests with the credit you have purchased on the old site until your credit runs out, at which point you’ll need to sign up to one of the new plans (or keep creating free tests using karma!).
As the new site is subscription based, we have to migrated your credit to match the new system. We’re using a fairly generous conversion to the new system to ensure everyone gets a good deal. The old 5st had a variable return on credit which moved from a high of around 25 responses per credit down to around 10. This meant that (depending on traffic) $5 credit bought a different amount of results. I thought it was cool, but the consensus was that it was all a bit weird. To keep this fair, all old tokens ($5) will be worth 30 responses in the new system. This means no matter when you bought your credit, you’re getting a good value upgrade in the new system. What’s more, we’re going to let you keep your credit on original.fivesecondtest.com as well! So consider this a warm introduction to our new system!
Accessing old Five Second Tests
One of the big changes we’re making is a complete revamp of Fivesecondtest.com. Click tests have been removed as Navflow will now concentrate on our “click tests” portion of testing. Our old Memory test is being shelved in favour of a new form of the Five Second Test which we feel gives better results and is better value for money than our old system. This means that old tests will not be viewable in the new site. Users wishing to get data will continue to be able to get it from original.fivesecondtest.com when we launch. This will be kept available indefinitely. If you really want, you can even continue using the old site.
The future of Usability Hub
What you’ll see in the next few weeks is really only the beginning. We’ve worked long and hard to make fivesecondtest.com more user friendly and more business friendly. We’ve listened to our users – and to the experts – and we’ve improved how the test itself works. We’ve integrated two great products into one set of tools. But we’re not finished.
These two new products are really fairly young, and we have a lot of upcoming features post-launch. So if they’re not perfect for you right now, we hope in the coming months they will be.
These two applications are just the first in a suite of tools that we call Usability Hub. We have 3 more coming before the end of the year, and each additional tool will be available at no extra cost to subscribers. We hope to make Usability Hub the one stop shop for all things usability testing and design. We’ve still got a long way to go, but we think today is a big step in the right direction.
Go from .NET to Ruby in One day. For (and by) the complete Linux n00b
posted May 31st 2010There are 1001 guides out there for installing bits and pieces of Ruby, Linux or Rails. This is intended as an absolute beginners guide, specifically for Windows users who don’t know jack about Linux, Ruby OR Rails. I’m a complete n00b at this. I spent a day or two trying to get this setup, finally worked it out and have gone back and done it all again whilst writing this guide on how I did it. I’ve tried to find the easiest way with the least complications. Advanced users will laugh at me, but they can go #&^$ themselves. If this whole setup wasn’t so difficult to use, I wouldn’t have needed to spend so long working out half of this stuff in the first place. I hope it helps other .NET Ruby hopefuls, but please keep in mind, I am FAR from an expert, so comments/improvements/suggestions are more than welcome!
I was issued something of a challenge last week: To write our next web app in Ruby.
Not such a big deal right? I mean, it’s just another language? Can’t be that hard? I read this quickstart guide, and whilst Ruby is rather odd little language, it didn’t appear to be anything that I couldn’t handle. So, I decided to give it a go..
The first thing I’d suggest as a .NET developer of nearly 10 years, is that if you’re seriously considering giving Ruby on Rails a go, I strongly suggest playing around with .NET MVC first. As a big fan of MVC, getting into Rails was a lot easier, as many of the concepts found in MVC were…well…stolen fromRails. If you’re familiar with Models, Views, Controllers, lambda expressions, partials and all that stuff, Rails will be a breeze. Ruby is still an ugly SOB in my opinion…but at least Rails will feel familiar to you.
Step 1. Installing Linux.
You could use Cygwin, or even Windows, but I’d really suggest not. I tried this, and it’s just a pain in the ass. Besides, you won’t be using either in our production environment, so you best get used to Linux sooner rather than later! I chose Ubuntu, just because that’s what came up in Google. If that statement doesn’t make it clear, I’m a complete Linux beginner. I used Linux about 10 years ago, and haven’t touched it since. So if lack of knowledge of Linux is what’s been stopping you, have no fear. If I can manage it, anyone can.
You have a couple of options to get up and running with Linux. Setup a new Linux box, or run a Virtual Machine. I didn’t have a spare box lying around, so I chose the latter. So, first thing you’ll need to do is go off and download Oracle VM VirtualBox and Ubuntu. Then mount the Ubuntu ISO as a virtual CD drive in Windows (there are plenty of apps to do this, google it).
Install VirtualBox and create a New Machine, Call it Linux, choose Linux/Ubuntu as your OS Type. You can pretty safely click next repeatedly during the rest of the install. Once it has installed the VM, go to settings > storage. Click the little empty CD controller and from the CD/DVD device on the right, choose the drive which has your Linux ISO. Click ok and start up the VM. If you’ve done everything right to this point, Ubuntu should start installing. If it crashes because it can’t find your ISO, go back and check your settings.
Assuming you have a fairly standard machine, it should all install easily enough. Skip the language packs if you don’t need them, they take forever to download and install. Once it has installed, you’ll need to “power off” the VM, and remove the ISO so that Linux can boot. When you first get into Linux, it’ll want to install a heap of updates…just let it.
Ok, so If you’re a Linux n00b like me, you wont even know where to start. In fact, you’re probably wondering why the damned VM window is so small. To fix this, go to the Devices menu in VirtualBox, click the Install Guest Additions. This will mount another ISO in Linux. Go to Applications>Accessories>Terminal. Welcome to Linux’s DOS prompt
cd /media
cd VBOXADDITIONS_3.2.0_61806/
(bit of a tip for the REAL n00bs…rather than typing the directory, just hit TAB and it will autocomplete)
sudo sh ./VBoxLinuxAdditions-x86.run
This will go off and install a heap of stuff to make Linux run nicer with your host environment….including allow you to have nicer screen resolutions. Once it is done, do a reboot. Couple of quick tips. Right Ctrl is your host key. Ctrl+F will give you fullscreen.
That’s it. Step 1 complete! The best part is that you haven’t completely committed to using Linux, it’s not too late to back out. You’re only ever a delete key away from being back in the safe hands of Uncle Bill and his crazy Cousin Steve.
Step 2. Installing Ruby.
Unfortunately, that was the easy part. The next part caused me a lot of grief. I eventually worked it out, but only after a lot of Googling, and a lot of swearing and it turns out I didn’t actually need to do most of it. Hopefully I can save you from the same fate. The first thing you need to know is, whenever Googling, resist the temptation to Cut and Paste helpful command line tips and tricks. These often include references to a specific version of a package, and can screw everything up real quick. If you need to install ANYTHING, make double sure that you’ve got the right version. The problem here is that so many versions of Ruby, Gems and Rails have come and gone, and the installation methods, requirements and problems are all different. This can be a major headache for Linux beginners! Even going through this the second time, I’m still running into issues!
So, crack open the terminal again. If you haven’t already guessed you’ll spend a lot of time here! First thing to note is a command called “sudo”. Sudo is the Linux verison of “run as administrator”. Most of the commands you run for installation will be prefixed with this. It will prompt you with your admin password and then carry on. Second thing to note is that for the most part, you won’t need to download anything from any third party website when doing installs. Linux has a rather nifty package installer that gets and installs everything for you! If you’re keen you can download source packages and compile them yourself, but we won’t need to do any of that.
So theoretically, Ubuntu should have most of what you need already, but we do need to go get a few bits and pieces. Make sure that the updater has finished before trying this, as it won’t work if it is still running.
The first thing you need is ruby.
sudo apt-get install ruby-full build-essential
Run this to make sure it installed ok.
ruby -v
This will print the version you just downloaded (hopefully!)
This will go off and get the latest version of ruby and install it and a heap of other libraries for you. Done! You’ve run your first Linux command and installed ruby!
To install gems :
sudo apt-get install rubygems
Run this to make sure it installed ok
gem -v
While you’re here, install the ruby-debug gem
gem install ruby-debug
Done and done.
Step 3. Installing Rails
Ok, so now we have ruby, and ruby gems. Now we need rails.
sudo apt-get install rails
Yeah…that’s it.
Now that all looks pretty simple, and you could’ve done most of it from the one line. But there are PLENTY of guides out there that will show you how wget your source packages, untar them, compile them, run them blah blah blah. Linux zealots want to know why people still use Windows over Linux? Have a read of your guides! You have to have a PhD in astrophysics just to learn how to run a web app!
Step 4. Install your IDE
Given that you’re a .NET developer, you’re going to need an IDE. None of this command line editing BS. We’ll be using Aptana Studio.
Go here: http://www.aptana.org/studio/download
Download the archive. You’re most likely using Firefox, so you should be able to find the zip in the downloads folder. Extract the archive to your home directory. You can then run aptana directly from there. You can also create a shortcut in your Applications menu. In Ubuntu, go to Preferences > Main Menu > Programming. Click the New Item button. Fill in the details, navigate to Aptana executable and select it, and also click the icon to change it to the Aptana one. Click Ok, close. And check it out in your Applications menu!
Great, that was easy! Well…not so fast! This is Linux! You can’t install something so easily! You need to do some more command line hacking. Ubuntu doesn’t come with Sun Java, which appears to be a prerequisite for Aptana. So now we need to install that.
First we need to add the java repo:
sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner"
Then get the updated list of files
sudo apt-get update
Then install Java
sudo apt-get install sun-java6-jre
You can now run Aptana. Once you open Aptana, you’ll also want to click on the Plugins button and install RadRails. It’s pretty self explantory.
That’s about all you need to get up and running.
If at this point, you’re wondering “why the hell am I doing this???”, I don’t blame you! We’re nearly done…hang in there! At this point you should be able to run a pretty basic website. So this a good time to….
Step 5. Watch a video
As you won’t have installed it, you’ll need to install curl before you get too far in the video, and mongrel (a webserver) too. Just run:
sudo apt-get install curlsudo apt-get install mongrel
If you ever find yourself missing something, that’s usually a good way to try to install it.
This 15 minute video will take you about 2 hours to get through. With a bit of luck, everything you’ve done till now will see you through the video. Use Aptana as your text editor for the examples. You’ll be pausing every ten seconds, but stick with it. By the end of it you’ll understand why so many developers love RoR….even if you still think Ruby is a pile of poo (like me), you’ll see how quick it is to get something up and running in Rails.
Before watching the video, make sure you create yourself a code directory.
cd ~ mkdir code cd code
And now enjoy the video!
http://media.rubyonrails.org/video/rails_blog_2.mov
Step 6. What next?
The good news is, that if you got through the video and everything worked, then you have everything you need to create your first web app. One good thing about Ruby is that there is a plethora of resources out there to get you moving from here. The one major pitfall is that there are HEAPS of tutorials that are hopelessly out of date, and can not only lead you astray but cause you some serious headaches if you mess up your installation!
There is a lot still to learn about RoR, especially for me, but I hope this is a good starting point. My goal was to write something that got ME up and running. I figure there are plenty of Windows developers out there (like me) that wouldn’t have the foggiest idea where to start, so if that is you, I hope this has helped!
Cheers,
Alan
Fivesecondtest migration to Navflow system
posted May 03rd 2010As you all know we’ve been very busy building our new app called Navflow. What you may not know is that we’ve also been rebuilding Fivesecondtest.com as well! The new Fivesecondtest will sit along side Navflow as part of our new system called UsabilityHub.com. There are lot of changes as a result of this move. I can’t talk about most of them just yet, but I DO need to give you a heads up about a few things. In the coming weeks we will be migrating a lot of data from the old site to the new site. All your user accounts, karma, credit and tests will be migrated across to the new system.
A few days before we migrate, we’ll turn off the ability to create new tests. You’ll still get results for all your existing tests, and you’ll still be able to do everything else. We’re just turning off the test creation. During that week we’ll be migrating all the data across, and we don’t want anyone’s test to vaporise. Most importantly, we want everyone to have their full quota of results BEFORE we move. There’s a very good reason for this…but I can’t tell you just yet!
Now, one other fairly major change is coming. We’re moving from pay-per-test, to a subscription service. The main reason we want to do this is because as fivesecondtest users we want you to also have access to Navflow. Buying a subscription to one, will give you full access to the other. Our monthly pricing is pretty damned good value too. The best part is that we will allow you to create many tests each month for just a little more than one Gold test costs right now. Not only that but, you’ll be able to mix and match your tests, and have much greater control over the number of results you want. Create a couple of fivesecondtests with 30 responses each, and maybe then go create a Navflow test with 40 results. Whatever you need! The best thing about these plans is that unused “value” from one month will roll over to the next month! I’ll go into more detail about what “value” means in the coming weeks.
Now…an important notice to people who currently have credit with us! Your credit will be migrated to one of the new plans based on your current credit. Your plan won’t automatically renew however. Given that our plans allow value to roll over, month to month, you will still have full access to the full value of your credit indefinitely. You can still use it up whenever you want! Of course, should you choose to sign up to a plan, the new value will be added to your existing total!
This is all happening in the coming weeks. We’ll keep you updated with news and changes! Thanks to everyone for your support, I hope you will enjoy the new Fivesecondtest.com as much as we’ve enjoyed building it!
Navflow Beta 1.5 Update
posted April 22nd 2010I was hoping to announce the release of Beta 2 today, but alas, we can only really call this Beta 1.5! First thing’s first, if you have any problems with the Navflow beta test, please contact us at support@navflow.com
There isn’t a whole lot of “fun” stuff in this update. Mostly bug fixes, a few feature requests, and a LOT of behind the scenes work preparing for the migration of Fivesecondtest.com. We could’ve held off on releasing this until we’d had a lot of other “features” added, but we have some fairly important things to get out in this version. So what’s here?
1. Karma – We’re releasing the first iteration of what will become the new Karma system. This system is based on the same philosophy as the fivesecondtest.com karma system, but with some important distinctions. First of all, we’re unlocking the amount of Karma you can earn in a day, and we’re taking the cap off how many results you can get with Karma. As of right now, however, you NEED Karma to make tests. To get new users started, you will get 20 karma when you sign up. So you can go ahead and use that straight away to create a test. What this means in the future however, is that for every result you want for free, you need to help out someone else. At the moment, this is a free for all. But there are some “checks and balances” being put in place to prevent “gaming” the system. So be good for goodness sake!
2. Language support – This isn’t full localisation unfortunately, but it does give you the ability to view tests that are in YOUR language. When users create a test, they let us know what language it is in, and then we only show that test to people who speak that language. This is based on your browser language, but for registered users is configurable from the settings page. Registered users will ONLY be shown tests for languages they’ve selected. Anonymous users, however, will be show tests in their language until there are none left, and then will start seeing international tests. Test owners can also set to only allow users who explicitly state they speak that language. Whilst this should significantly improve the quality of your results, this option could slow down the rate at which you receive results depending on what language you choose. As a result of this change, we’ll be adding a lot of our international sign-ups later this week.
3. User dashboard – There have been a few comments about how the Navflow logo not taking users “home”. This is actually because we hadn’t finished our user dashboard page yet. It’s now (mostly) finished. What this means is that if you’re a registered user, you will no longer need to go to the front page of the site. You will be taken to your own dashboard showing you how much credit, karma and results you have. There is a lot more coming to this page, so stay tuned!
Ok well, that’s the bulk of it. There are a lot of other minor changes, and a lot more to come. We’ll be adding some more testers today, so if you are desperate to get into beta, email us at support@navflow.com and let us know! If you read all of this, you deserve to get in!
Topics
Search
Archive
- July 2010 (2)
- May 2010 (2)
- April 2010 (3)
- March 2010 (1)
- February 2010 (3)
- January 2010 (3)
- November 2009 (1)
- October 2009 (2)
- September 2009 (4)
- August 2009 (5)
- May 2009 (2)
- April 2009 (1)
- March 2009 (4)
- November 2008 (1)
- December 2007 (2)
Comments(2)