Reset Google User Account on an Android phone

Posted by Jens Lund Møller | Posted in Android, Google | Posted on 07-08-2009

0

How to reset the Google User Account on an Android phone without doing a “Factory Data Reset” if you need to login as another user:

Settings > Applications > Mannage applications

1. Click “Gmail” > click “Clear data”

2. Click “Gmail Storage” > click “Clear data”

3. Click “Google Apps ” > click “Clear data”

Do the above step to all the Google apps you have in the “Mannage applications” menu. Next time you open Gmail you will get the “Set up your Google account” screen and as a result you can login with another user.

Begynderguide, how to Twitter for begyndere

Posted by Jens Lund Møller | Posted in Twitter, guide, how to | Posted on 26-07-2009

0

Twitter er svær at gå til for nye brugere. Jeg husker selv hvordan jeg selv følte mig lettere lost første gang jeg var på Twitter. Jeg søgte efter guider, men synes ikke jeg fandt en rigtig begynderguide. Derfor denne How To Twitter for begyndere.

I princippet er Twitter det samme som Facebook’s statusopdateringer. Man kan skrive en kort tekst, maks 140 tegn, som sendes til alle de personer, der følger en.

Den store forskel på Twitter og Facebook for mig er, at på Facebook følger jeg venner og bekendte, og statusmeddelelserne handler mest om hvad man laver, tænker eller hvor man er.

På Twitter følger jeg personer, som interesserer sig for det samme som mig, og som Twitter om emner jeg følger med i. Facebook er til personlige meddelelser og Twitter er til professionelle meddelelser. Det medfører, at jeg følger personer på Twitter, som jeg hverken kender, eller har mødt.

Et eksempel på hvordan jeg bruger Twitter; jeg har lige været på ferie og før ferien tilmeldte jeg mig forskellige tweets, som twittede om restauranter, kaffe-barer, begivenheder mv. i den by jeg skulle besøge. Det gav mig en masse værdiful information, som ellers ville have krævet noget mere research at have fundet frem til.

Det står ikke skrevet i sten, at det er sådan man skal bruge Twitter. Andre bruger Twitter mere som de bruger Facebook, men det er den måde jeg foretrækker at bruge Twitter.

Tweet, reply og retweet
På Twitter kan man sende en besked, en såkaldt tweet. Man kan svare på andres tweets på to måder. Enten som en Reply, der kan læses af alle, eller som en Direkte Besked, der kun kan læses af den man sender beskeden til. Derudover er det også meget brugt, at tweete videre, hvad man har hørt fra andre via en Retweet.

Reply
Vil man svare eller kommentere på en tweet, er der to muligheder. Enten reply eller direkte besked. En reply laves ved at man skriver @ foran brugernavnet på den person, som man svarer, i svaret. Mit brugernavn er jenslund og vil man svare på et spørgsmål jeg har stillet, skriver man altså @jenslund som det første i svaret.

Eksempel på en, der har sendt mig en Twitter reply

Eksempel på en, der har sendt mig en Twitter reply

Visning af reply
Følger jeg den person, der svarer mig, vises personens svar i min nyhedsstrøm på forsiden og det vises også under @jenslund i højre menu. Følger jeg ikke den person, der svarer mig, vises svaret ikke i nyhedsstrømmen, men kun under @jenslund i højre menu.

En reply kan ses af andre Twitter-brugere. Ønsker man, at den besked man sender, kun kan ses af den man sender til, skal man sende en direkte besked.

Direkte besked
Ønsker man ikke, at ens besked kan læses af alle, kan man sende en direkte besked. Det gør man ved at skrive d som det første i beskeden. Man kan se, at teksten oven over tekstfeltet skifter fra “What are you doing?” til “Direct message” når man taster d efterfulgt af mellemrum. En direkte besked til mig skal altså starte med “d jenslund”.

Eksempel på hvordan man sender en direkte besked på Twitter

Eksempel på hvordan man sender en direkte besked på Twitter

Man kan se både sendte og modtagne direkte beskeder i Direct Messages menuen i højre side. Man kan kun sende direkte beskeder til folk, som følger en.

Retweet
Det er muligt at genbruge andres tweets ved at lave en retweet. Det kan være en tweet fra en person jeg følger, der er så interessant, at jeg mener alle i mit netværk bør læse den.

En retweet laves ved at skrive rt foran beskeden. For god ordens skyld skriver man derefter @ og brugernavnet på den oprindelige twitter, så alle ved hvem der er forfatter. Så hvis en person vil retweette en af mine tweets skriver han rt @jenslund og kopierer beskeden ind bagefter.

Jeg retweeter en besked fra Vega om en kommende koncert

Jeg retweeter en besked fra Vega om en kommende koncert

Forkortede url’er
Da en tweet kun kan være på 140 karakterer, og da mange tweets har url-henvisninger til artikler i dem, bruger man url-forkortere. Der findes et hav af tjenester som kan gøre lange url’er så korte, så der er plads til andet tekst i tweet’en. Jeg benytter mig af den, der hedder Bit.ly. Bit.ly har en simpel statistikfunktion, så man kan se hvor mange, eller få, der har klikket på linket i twitten og derved får man et bud på, om der overhovedet er nogle, der læser ens tweets.

Denne artikels lange url og den korte Twitter-venlige bit.ly version

Denne artikels lange url og den korte Twitter-venlige bit.ly version

Dette var en meget ufuldstændig guide til at komme i gang med at bruge Twitter. Lad mig endelig vide, hvis der er noget, der skal forklares bedre. Jeg er jo allerede ramt af The Curse of Knowledge og kan ikke huske hvordan det var ikke at kunne forstå Twitter.

Jens Lund Møller på Twitter

“The Mobile User Experience Is Miserable”

Posted by Jens Lund Møller | Posted in Mobile phone, UX, User experience, usability | Posted on 20-07-2009

0

Acording to a study by Nielsen Norman Group browsing the web from a mobile phone today is as bad as it was to browse the web from a desktop 15 years ago.

The users had difficulties doing everyday tasks on their mobile phones, like finding information about a specific wine or finding arrival info for a plane.

Some of the hurdles they found was:

  • The screens are to small (users using phones with bigger screens had a higher succeed rate)
  • It’s hard to type on the small keyboards on mobile phones
  • The mobile Internet connections are to slow
  • Sites designed for mobile phones did better than the desktop version, but it can be really hard to find the mobile version.

These findings are exactly what a colleague and I found in our master thesis – “The User Experience of the Internet on Mobile Phones” (4,8 mb PDF in danish)- which is from 2008. Here is a very boiled down section from the abstract:

Screens and keyboards are factors that feel like a hurdle and therefore reduce usage. Also, the speed or lack of it, when loading pages seems to be a hurdle.

Nielsen Norman Group found that users did better in solving their tasks on websites designed for mobile phones and they do suggest, like we did, that servers should auto-sense users’ devices and auto-forward mobile users to the mobile site. I simply don’t understand why companies use money on getting a mobile website designed and then don’t do this simple operation.

Nielsen Normans Group used three usability methods. My colleague and I made our master thesis on basis of interviews, focus groups and surveys. But the results are pretty much the same.

Verdens ældste mand er død. Igen.

Posted by Jens Lund Møller | Posted in Uncategorized | Posted on 19-07-2009

0

Er han i virkeligheden en kat med 9 liv, der blot skifter navn og nationalitet, og i så fald hvor mange liv har han tilbage?

Henry Allingham, 113 år
Tomoji Tanabe, 114 år
Habib Miyan, 129 – 138 år
Chris Mortensen, 115 år

I’m still forced to think when using the internet

Posted by Jens Lund Møller | Posted in GUI, UI, usability | Posted on 10-10-2008

0

When participating in a online survey the other day I got a flash back to Steve Krugs 8 years old phrase “Don’t make me think“. The survey did indeed made me think. The highlighted text in the picture below says “Your answer is sent to Megafon when you click next”

The problem is there is not a button called “Next”. There is only arrows. Of course it’s obvious what you have to do to continue, but i was actually for a millisecond looking for a “Next” button. The balloon over my head indeed had a question mark in it.

The problem is that the visual design and the text are talking against each other. Either the text should state “Click the right arrow” or there should be a button labeled “Next”.

But i actually think there is a bigger problem. Since this is the last screen in the survey and since clicking the right arrow will send the result and finish the survey I think there should be a button with a label like “Finish survey” or “Send result” or something similar indicating what is going to happen when clicking the button.

What’s the difference between RSS 2.0, RSS .92 and Atom 0.3?

Posted by Jens Lund Møller | Posted in usability | Posted on 26-06-2008

2

And why should I care?

RSS is in my opinion one of the most usefull inventions on the net. It saves me alot of time using RSS instead of hunting for new stories on every news site and blog I read.

But even though I have used RSS for several years I have newer tried to figure out how i works. I’m not interested in the technology behind but in the goals it helps me to accomplish; to notify me every time a site has new material.

Since changing to Firefox 3 I have been kind of puzzled when I want to subscribe to a new RSS-feed. I often have to chooce between several kinds of feeds. (Don’t know if this was the case in FF 2 as well because I didn’t use FF 2)

Firefox is asking me to choose between RSS 2.0, RSS .92 and Atom 0.3. I don’t have a clue what the difference is. But I expect there is a difference since there is a choice. My mental model tells me that the difference might be in the amount of text that will be displayed in the RSS-reader. One will give me the first paragraph and another will give me everything. But I have no idea if this is true.

This is a great example of presenting choices to the user, that the user may not know how to act upon. If there is a difference in what I will get in my RSS-reader depending on what format I choose, describe the difference in words understandable by “average” user like myself. Not in technological terms. If there is no difference at all, don’t give me the choice in the first place.

Does bigger screens on mobile phones lead to better usability?

Posted by Jens Lund Møller | Posted in GUI, Mobile internet, Mobile phone, UI, User experience, iPhone, usability | Posted on 22-06-2008

0

Screens on mobile phones is getting bigger. That is good because Jakob Nielsen says bigger screens leads to better usability. One reason mobile phones is getting bigger screens is that mobile phones just isn’t mobile phones anymore. They have become cameras, mp3-players and internet devices as well. All this new functionality requires a bigger screen compared to what is necessary for just making phone calls.

But even though i do agree with Jakob Nielsen that bigger screens leads to better usability, the usability is of course also depended of the design presented on the screen. As Buchanan et. al. state it in Improving Mobile Internet Usability one problem is that the design isn’t tailored to the screen size. Designers try to fill a sheet of paper even though what they are designing for is a Post-it.

The article The Myth of a Big Screen, Treating the symptoms rather than the cause state it this way:

“Making the screen bigger is just the current fashionable red herring to distract you from the plain and simple fact that the vendors can’t get the design right.”

These articles are from 2000 and 2001 and therefore im surprised to witness the new Samsung Instinct and specially the design of the browser on the Instinct.

But let’s first have a look on how Apple designed Safari on their iPhone. Both the iPhone and the Instinct have big screens. But they still have small screens for web surfing. To give the user the best experience it may be logic to use every possible pixel on the screen for content.

When scrolling in Safari on the iPhone the URL text field will disapear as you scroll down the page giving more space for content. But still there is 20 pixels used for the Status bar in the top and 44 pixels being used in the Button bar in the bottom.

I think it’s a good decision made by the Safari designers to let the URL text field disapear because on such a small device every single pixel used for content counts.

Therefore i was kind of puzzled when i saw the design of the browser on the Instinct. The Instinct as well as the iPhone has a URL text field in the top. Instead of a Button bar in the bottom, the Instinct designers have chosen to use space on both the left and the right side of the screen for buttons. This gives very little space for the content.

Luckily the designers have made it possible to enter a Full Screen View by touching an icon. The strange thing is, that a Full Screen View on an Instinct isn’t what i would expect from a Full Screen View. The only thing that disapears when you touch the icon is the URL text field leaving all buttons in on the left side of the screen.

The best aproach i have seen so far on designing a browser for mobile phones is Firefox. Though Firefox for mobile phones isn’t released yet a video shows how the Firefox mobile phone team have aproached the design challenge and have understood that on a small screen every single pixel used for content counts. All pixels are used for content which i think will lead to a better user experience than on both Safari on the iPhone and especially the browser on the Samsung Instinct.

To reach the navigation buttons on Firefox you have to scroll your finger to the right which reveals navigation bottons on the left side of the viewpoint. This aproach is very clever. Firefox use every single pixel for content which is what users are interested in when they read/scan pages.

It seems odd to me that the Firefox browser and the Samsung Instinct browser are designet the same year. The Safari browser does a deasent job but could learn from Firefox. But the Instinct seems to be designet before 2000 where the article mentionet at the top stated

“Making the screen bigger is just the current fashionable red herring to distract you from the plain and simple fact that the vendors can’t get the design right.”

It’s great mobile phones now have bigger screens which makes it easier to surf the internet on mobile phones. But to what use is the bigger screens when designers just don’t understand that we are not interested in their design but content?

The evolution of mobile phones

Posted by Jens Lund Møller | Posted in Mobil, Mobile phone | Posted on 14-05-2008

0

This video gives a short view of the evolution of mobile phones from 1985 until today and a glimse of the future.

Some of the interesting info is that one mobile phone is inspired by a communication device from Star Trek and another from a mobile phone in Matrix.

Feedback on the iPhone

Posted by Jens Lund Møller | Posted in User experience, feedback, iPhone | Posted on 12-05-2008

0

In this post “User experience factor 1: state glue” Martijn van Welie descripes the feedback you get from the iPhone when you delete a mail.

I think Martijn van Welie is right on spot when stating that the iPhones feedback “leads to a very satisfying experience”.

it’s particular important with tactile feedback from a device when there is no physical feedback like haptic feedback. On the iPhone it is well done with small “movie clips”.

The user needs to know that something is happening and what it is that is happening when interacting with a device in order to be able to know if the action was the expected one.

The iPhone does it in a way that makes you do it just for fun, show it to your friends or write a interesting post about it. I myself is being found guilty on all counts.

Design For Mobile

Posted by Jens Lund Møller | Posted in Mobil, UX, User experience, usability | Posted on 05-05-2008

0

Design For Mobile will be the first North American mobile user experience conference. This will be a two-day conference focused on strategy and tactics for user research, product definition, interaction and other design, and usability testing. A day of workshops and training will preceed the conference sessions.