Skip navigation.

Posts tagged with "Community"

avatar

Community Review: The pitfalls of system expectations

, , ,

The situation

Not too long ago, Opera Community software allowed us to create our own URLs based on our free text, or the post title. This is certainly a welcome addition as its much easier to remember a URL based on words than some system generated numbers: show.dml/27659. But I've noticed a hiccup in how the users expect the system to act, and how it actually does.

If you want to follow along, it's easy to reproduce:
  1. Create a blog post (w/title)
  2. Click preview
  3. (On the preview screeen) Now, change the post title
  4. Save blog post

You'll find that the "Post URL" is based off the first title instead of the second. I know there's a reset button which will (obviously) reset the title, but it's asking me to reset something I never "set" in the first place. In other words take action to correct something I never initiated. The system generated that URL and I was oblivious to it.

That's a poor solution IMO. Either the user is going to specify his own URL with that box or the user is not (leaving it to be an automated process). Where does the reset button fit in with the latter? And heaven forbid if it's hidden because the "show advanced options" menu isn't activated... Then the users wouldn't have any idea that a URL was being generated at all!

Great Expectations

The real problem goes beyond the implementation/technicalities of web forms and into the realm of "system expectations." We could argue what the user has responsibility to check before hitting submit, but the bottom line is that our expectation of "preview" across all software systems is that changes made there will not be reflected in the final version. Changing the title in the preview page should carry that change over when I hit "submit" whether I hit reset or not.

It's not hard to imagine* someone blogging without the "show more options" dialogs open, who drafts a half hearted, or possibly offensive post titled:

"our drunken boss at the christmas party"


...and clicks the preview button and get a change of heart, moment of clarity, more witty, etc etc... and end up with:

"He knows how to have fun!"


Then the user passes the URL out to the office:

Hey, I put up pictures from last night! Enjoy:
http://my.opera.com/aboutToBeFired/blog/our-drunken-boss-at-the-christmas-party


...even if the user does have the "show more options" dialogs open, it's not hard to overlook something like that at all. If you're used to autogenerating URLs, why would you bother checking it? I see the reset button only being useful to those that took the conscious effort to create their own URL string in the box.

It's not hard to come with some solutions to the problem though, here's a quick list of suggestions to alleviate this problem:
  • Don't hide the URL in the advanced options.
  • If Opera generated the title from the post title, set a flag. If the user entered the text, then don't
  • Then, on "submit" generate the URL from the final title and compare with what was already in the "Post URL" field. If different and the flag is set, ask which to use. (Opera created the first one, but the user could have edited... we're unsure if the user is aware of the title). This step could also be done if the user has changed the title of the post.
  • If the flag is not set, keep the old, user generated title (the user has shown they are aware of the titling by creating their own)
  • If the "Post URL" field is empty, then generate from the title as you would going to the preview page and submit away!


This was posted to the Community Forums on 17 October 2006:
http://my.opera.com/community/forums/topic.dml?id=163058

*not hard to imagine because it happened to me. I often put up temporary titles until i can see how everything comes together... how it looks on the screen with the pictures, or maybe I just haven't thought of a title yet.

**We'll also say that I purposely set up this post to have the title and URL mismatched.. yeah, that's the ticket.
avatar

Opera Mobile Profiles

, , ,

Here's a rewrite of my post from the Opera Mini blog...

When it comes to the Opera Mini browser, it's very important to be able to have a profile (user settings, bookmarks, feeds, etc) that is independent of Mini.

Several reasons why:

  • If we could save and edit bookmarks on our desktop *in addition to* our phone, it would create a seemless experience. Our bookmarks are the same if we save them on our phone or our desktop, or through a web app.

  • When updating Mini, you lose it all. You can't back up your bookmarks and "remember me" information. You start over at every upgrade.

  • Opera CTO and CEO have hinted at this, most recently in this Capitol Markets Day presentation

  • There's millions (ten!) of Mini users that could potentially be getting involved in the community. If they have an "easy in" and a reason to create a profile, it should be easier to get more community involvment.



Use the Community! Since the compressed page is coming from Opera anyway...*AND* you have such a great community, you could have the users:

1) Download mini

2) on the page with the EULA include some text asking: "if you'd like to backup/sync your mini data..." along with the standard "login/create account" prompt that would allow the user to create a my.opera.com/ profile (or login for all of us that have one already)

3) That will establish a link up so that any bookmarks created on the handset will also be copied to the users profile.

4) The user can manage the bookmarks (at least), and some mini settings (like: **-fullscreen on startup!) from this page. It's defaulted to private viewing, but able to be viewed public. So Opera profiles created via Mini would have an "About" page and a hidden "Mini" page that could be made viewable.

...Opera gets community members, users get to keep data that gets lost everytime we update Mini, we get an easier UI to manage, we can share our mobile bookmarks with the community... sounds cool to me! Give the millions of Mini users more than just that "my Opera" bookmark that many of them probably wouldn't know what to do with- but now they have an account and can easily get right to community involvement.

It's only natural to then extend this capability to the desktop as well. I picture a "local" and an "online" bookmark setting. The online could be flagged as public or private as noted in the Mini example, but will always be available to the user.

Then any desktop upgrades, beta testing multiple computers will all be synced together, including Mini.

I bookmark slashdot.org one time and it's available on any version of Opera I install via my Opera Community Profile (which I may choose to share with the rest of the community).

January 2009
S M T W T F S
December 2008February 2009
1 2 3
4 5 6 7 8 9 10
11 12 13 14 15 16 17
18 19 20 21 22 23 24
25 26 27 28 29 30 31