elguennuni / rtm4bb

Automatically exported from code.google.com/p/rtm4bb
0 stars 0 forks source link

Alpha version first impressions #1

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Some observations about the alpha:

First of all, the interface design is very good.  It's clean and intuitive. 

The one thing I would change globally is the sub-text/supplemental
information font color.  When I scroll over an item, the supplemental
information remains the original dark color and disappears into the
background.  This also includes item counts in the home screens.  For me,
this causes an involuntary mental jerk as I expect to be able to see the
date, list, etc. just as easily as the task name.  This looks like it would
be an easy fix and would improve the overall experience for me.  I would
ask around before I made the change though.

The OTA install went flawlessly.  I had the app up and running in less than
five minutes to include registering the API.

When the home screen came up, all he message counts were correct.

The Lists screen was correct and displayed in the same order as
RTM->Settings->Lists.

The Tags screen showed only 5 of the 16 tags I have.  These 5 were the only
ones with active tasks, so that might be the criteria.

The Locations showed empty since I have no locations.

When I clicked on Today, BBRTM displayed ALL the currently due tasks.  This
included overdue items.  Since the few items I have in RTM are all overdue,
this behavior did not mimic RTM.  When I logged into RTM and looked at the
Today screen, it shows no tasks.  All the tasks are in the Overdue tab.  I
don't know if this is planned behavior or not.  It works for me since
overdue tasks are due today anyway.

All of the tasks displayed correctly.  The only confusion that I could
anticipate is the way the due date is displayed on overdue tasks.  Since
none of my tasks were overdue more than one week, they all showed weekday
names.  This makes them appear to be due next week instead of overdue. 
Though the task is bold and underlined to indicate overdue, it still made
me have to think a bit.

So, clicking on a task and pressing the menu button returned the following
values on an overdue task:

Complete - Completing Tasks: 1
Edit - Editing Task Index: 0
Delete - Deleting Task Index: 0
Postpone - Postponing Task Index: 0
Snooze - Snoozing Task Index: 0
Undo - Undoing

These were all performed on the same overdue task.

One thing that grabbed me was the realization that there is no way to see
All Tasks.  You can only see Today through This Week.  So, I can't tell if
I have entered a task for next month.

Also, there is no manual refresh option.  I added a task due on Tuesday via
RTM web interface from my laptop and had to close then reopen BBRTM to see
the change.  I don't know if there is a hard coded refresh cycle or not.

When I looked at the Tags screen, the tags displayed with @-prefixed tags
at the bottom of the list.  This is counter-intuitive to the GTD system of
tagging for quick access.  I don't know the sort options you have, but just
a thought.  Each of the tags displayed its associated tasks appropriately.

Overall, I think you have done a GREAT job so far.  I can think of many
things that could be added, but I don't know the roadmap well enough to
suggest yet. I think that when you implement CRUD fully in the screens that
you have right now, you will have a pretty good little app.  At the very
least, it will be a great basis for a Rev 2.

I hope this info helps.  I didn't which of these items you knew about,
which were there by design or which were errors.  The biggest thing for me
is the color of the list items.  That one change would polish the app
immensely.

Feel free to query me any time.  I am online 24/7.

l8r,
bk

Original issue reported on code.google.com by bking39...@gmail.com on 1 Feb 2008 at 5:00

GoogleCodeExporter commented 8 years ago

Original comment by jemer...@gmail.com on 1 Feb 2008 at 5:13

GoogleCodeExporter commented 8 years ago
see issues 9 - 13 that i added.

Original comment by jemer...@gmail.com on 2 Feb 2008 at 5:27