Something to note here is that for every one of these widgets, you
could imagine the following:
The widget is available as an
+ iGoogle / Yahoo homepage widget
+ OS X Dashboard widget
+ Vista Confabulator widget
+ iPhone widget
+ We require users to have a Hub account and log in; OR
+ We allow users to access data with collection and/or item URLs
I don't think we need to support all permutations and combinations.
Instead we can think strategically and work through how each widget
is most useful to whom in what configuration.
Some examples:
For Chandler Desktop users, the quick entry widget on the Desktop
(Mac/Vista) will be useful to more people than an iGoogle widget.
If you're a Desktop user and you want to share a one-off item with an
ad-hoc group of people, some of whom have never heard of Chandler
Project, a ticketed URL to the item would be way more useful than
requiring that everyone get an account *just* to access that one item.
As Sheila said, she will be following up with a description of the
different users we'd like to serve with web widgets. I think gaining
a better understanding of who those people are and what functionality
is most useful to them will eventually guide us to a reasonable plan
for web widgets.
Mimi
On Feb 12, 2008, at 10:52 AM, Sheila Mooney wrote:
Mimi asked me to write up a summary and use case descriptions for
each web widget idea. This is simply an exploration of how people
might use these widgets and does not reflect any strategy details
or relative priority. That will be addressed in a separate email.
Quick Item Entry
+ Gives the user an easy mechanism to enter data into the
application when they are in another context. By default, all items
are notes.
+ The user logs into the server, gets pulldown populated with all
the collections on the server then selects which collection they
want to add the items to.
+ Until we have a list widget there is no way to see the items
without accessing the desktop or hub UI.
+ A way for current desktop users to add data to their collections
as well as a way for other desktop users or casual collaborators to
add data to a particular collection.
+ Use Case: I am researching contractors for my home renovation
project. Based on searches in yelp, craigslist, I find a number of
people to call. I bring up the quick entry widget and quickly add
them into my HomeReno collection so I discuss the list with my
husband and I can call them later and ask for quotes.
+ Use Case: My husband receives a phone invitation to friends
birthday party while on the road. He uses the web browser on his
phone to access our shared home collection. He adds a quick note
for me to setup a babysitter for that particular date.
Single Editable Detail View
+ Accessible via item URL created by a desktop user or in the hub
UI. There is a separate workflow to generate one of these things.
+ Read write is the most useful to have so we can do that one
first. We would also like read only but won't block on this if it's
considerably more difficult.
+ Users do not require an account to access the item.
+ Use Case: I create a grocery list in my Home collection in the
desktop and generate the item URL. I then bring up this item in a
browser on my iPhone while I am shopping at Whole Foods and check
off items as I get them.
+ Use Case: My spouse is planning a 40th birthday party for me and
generates an item URL to send to a small group of our friends. The
theme is black and white and we want people to bring some kind of
black and white dessert. The invitees can edit the item to indicate
if they can attend and what they are bringing.
Mini calendar and Preview area
+ Provides quick at-a-glance summary of today's schedule - all the
events in the dashboard collection.
+ The first implementation would be a simple read only view showing
the list of events for today and a single month mini calendar which
you then could move backwards and forwards by a month.
+ The next iteration would be to support viewing the read only
event details when you click on that event and perhaps support
multiple month mini calendar display.
+ The final iteration would present an editable detail view for the
event.
+ Use Case: I spend quite a bit of time working from the iGoogle
home page. I add my mini calendar widget to the home page so I can
see what my meetings are today without having to run Chandler.
+ Use Case: I access the mini calendar widget from my iPhone while
traveling for business. My assistant has access to my schedule and
added some new calls for me.
Bookmarklet
+ Add a bookmarklet for a web page you want to keep and send this
to your Chandler Hub account. For quickly adding content.
+ Login and select the collection destination for your bookmarks.
+ Use Case: I want to hire a children's photographer for my kids. I
find a number of reviews and links to sites online. I bookmark all
the sites I am interested in and send those to my Kids collection.
I can then go through them with my spouse and look at the sites in
more detail.
Search box
+ Login and search all shared collections or select a particular
collection.
+ This would generate a list and selecting an item would bring up a
read only detail view. The next iteration would bring up an
editable detail view.
+ Use Case: I wrote a friend's phone number in an event from a few
weeks ago. I am not running Chandler and I am on my way to meet
them. I quickly use the search widget to look up their name and get
the phone number.
+ Use Case: Our kitchen faucet is leaking. My spouse searches our
home collection for the name of the plumber we used last year to
fix our bathroom.
Single collection dashboard list + read only detail view
+ Login and specify the collection to view which displays a list
view for all items in that collection.
+ A more advanced iteration would display an editable detail view.
+ Very useful for people sharing a collection since they can look
at all the items and view triage information as well.
+ Use Case: I share seasons tickets to the San Jose Sharks with
some friends. We divide up the tickets amongst 4 people. I have
friends coming to town so I use the web widget to bring up the
collection and see if there are games this week and how has the
tickets so I can try and switch with them.
+ Use Case: My husband and I share a collection for planning our
vacation to Australia. He has a friend in Melbourne that wants to
meet us for dinner. He uses the web widget to check the itinerary
we have planned so far to see what date we can meet up.
Notifications via SMS/IM/Email
+ There would be a workflow in the desktop where you can set these up.
+ Works well for mobile devices.
+ Users login and specify a collection they want to receive
notifications for.
+ Use Case: I am managing a software release. I am out this week at
the conference and can't run Chandler all the time. I sign up to
receive notifications for new and changed items so I can monitor
the progress on tasks.
+ Use Case: I share a kids activity calendar with a few close
friends. I want to receive updates for items changed or added by
others so I know about new kids events ie: trip to the zoo on
Saturday.
Sheila
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
