Have to figure out how you want to handle existing lists...

For account-oriented lists, you'll want to privatize the lists, or still keep them shareable?

Do you want to generate unique access urls for each list?

rather than using touchevents

1. swiperight to complete > swipeleft to undo > swipeleft again to delete (or expose delete button)
2. on an uncompleted item: swipeleft to delete (or expose delete button)

Basically the swipe only shows delete if it isn't complete. If it's complete you have to undo it to delete it... is that good? Good enough for now.

Include a 'clear completed items' button at bottom of list?

At least on first visit or before first actions.

We'll be using backbone to switch which list is displayed, so there should be a sidebar of some sort? This will be crucial for the move to everything on a single page.

This will allow users to use the new uuid format /s/:token/lists/:uuid instead of /s/:token/lists/:slug, while preserving any links/bookmarks users may have pointing to a specific slug (which is fickle anyway since they change whenever a list name changes).

use a backbone comparator function based on ... created_at ? (since you dont want the list to reorder every time you update an item's attributes.)

Because it's an action that cannot be reversed.

"My lists" should have the same styles that your list titles have on a list show page.

It inserts the corrected spelling in the field instead of clearing the field.

Try wrapping the input in a form and binding on a submit instead of keypress. Make the enter icon a submit as well?

If so, is it confusing?

If not, fix it!

Also change styles on it to match/uppercase both places, or Title case both places? Bold?

on long entries, edit mode should maintain height and the text should be in the identical position.

Probably need to use textarea's and use JS to determine the height. height should readjust bigger or smaller as necessary.

Probably need some sort of real demo users can interact with on the homepage, with tooltips (see http://disqus.com)

PUT request for a collection of tasks to be updated.

For instance, when sort order changes it updates all models...

stack-less and stacked alike

generate a token url?

Should probably serve a static public/index.html page on all routes except home.

Everything else should respond with json??

Investigate how to ensure json is served at routes, but that the html page always loads on refresh or back/forward in browser.

Need a disclaimer to tell people that empty lists will be removed after a certain time of inactivity.

class Stack
   has_many :lists
end

class List
   belongs_to :stack
end

use:

empty_stacks = Stack.includes(:lists).where( :lists => { :stack_id => nil } )
empty_stacks.map { |stack| stack.destroy }

https://github.com/furf/jquery-ui-touch-punch