{"id":3402,"date":"2011-04-25T00:00:00","date_gmt":"2011-04-24T22:00:00","guid":{"rendered":"http:\/\/www.theill.com\/blog\/2011\/04\/25\/use-sensible-defaults-when-building-a-web-mobile-or-desktop-application\/"},"modified":"2011-04-25T00:00:00","modified_gmt":"2011-04-24T22:00:00","slug":"use-sensible-defaults-when-building-a-web-mobile-or-desktop-application","status":"publish","type":"post","link":"https:\/\/www.theill.com\/blog\/2011\/04\/25\/use-sensible-defaults-when-building-a-web-mobile-or-desktop-application\/","title":{"rendered":"Use sensible defaults when building a web, mobile or desktop application"},"content":{"rendered":"
While working on migrating “gomore.dk”, a Danish ridesharing service, to Rails 3, I figured it would make sense to look into the existing database to figure out if I could add some sensible defaults when creating e.g. new rides. The site already contains a decent database so I figured it would be rather easy to measure which defaults to use.<\/p>\n
As an initial example, I would like to know how many seats were shared on each trip and therefore I did a simple query as shown below:<\/p>\n
<\/p>\n
From this, it is pretty obvious that I should use “3” as a default number of seats available. In this case, some common sense would probably give you the same result (four seats in a standard car minus one for the driver).<\/p>\n
Same type of query can be used to figure out the most popular seat price:<\/p>\n
<\/p>\n
It is even possible to remove<\/em> options if you look into providing sensible defaults for your users. As in this case where the existing gomore.dk contains a checkbox for specifying if car is “smoking” or “non smoking” area. A query showed me<\/p>\n <\/p>\n i.e. we really don’t need to have users decide on this .. more than 95% of all rides are non-smoking rides so the rest should either write it in a comment field or edit the ride afterwards to mark is specifically as “smoking”. So in this case we just removed an option from our wizard to avoid clutter. Lovely.<\/p>\n The examples above should go for all defaults .. also stuff your marketing department would like to decide e.g. when a user creates an account and have to uncheck instead of check a “Subscribe to our daily, fancy, not-to-miss newsletter” box. Focus on pleasing your users by pre-selecting choices they probably are<\/em> going to make themselves … follow the “don’t make me think” principle! It makes users happy and allow them to complete a task faster.<\/p>\n Using sensible defaults goes for any type of application you are creating being for web, mobile or desktop.<\/p>\n","protected":false},"excerpt":{"rendered":" While working on migrating “gomore.dk”, a Danish ridesharing service, to Rails 3, I figured it would make sense to look into the existing database to figure out if I could add some sensible defaults when creating e.g. new rides. The site already contains a decent database so I figured it would be rather easy to … Continue reading Use sensible defaults when building a web, mobile or desktop application<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"amp_status":"","spay_email":"","jetpack_publicize_message":""},"categories":[1],"tags":[],"jetpack_featured_media_url":"","jetpack_publicize_connections":[],"yoast_head":"\n