Open clearhythm opened 10 years ago
i've spent some time with the status growl...
for mobile and specifically these use cases, i don't think it's best to obstruct the user with a toaster. rather, i think the current status mechanism (a red bubble with a number, pointing to an activity feed with updates) should be sufficient.
the task now becomes to design the activity / update view, where both successful posts, stuff you've received, and also errors (things failed) can appear there. also, for errors, there is a use case where you tried to post to Facebook, and we immediately update the DOM, but then FB returns an error code. in this case, it would be best to update the failed DOM node with a message about the error and a link to "repost" or something.
so instead of global toast, we just have a simple "status notification" bubble mechanism to handle most situations about updated activity, and an inline error notification to handle errors on the FB response.
Further design detail needed