We need to design and develop Hub App. The plan is to base it on Togethr, presumably in order to:
- take advantage of the work done on Togethr
- drive usage of and resource the further development of Togethr
- generally focus the two efforts in the same direction
However, the features required for a collaboration app don't map exactly onto Togethr and Togethr is currently far too complicated to articulate without getting a headache. The blurred concepts of context/space/place are confusing. It's not clear how users change and filter contexts. Implicit proximity filtering makes less sense the more users dig into the app.
I suggest we revise Togethr in line with the requirements of the collaboration app:
- simplify the basic structure
- strip out the complex aspects
- provide clear user pathways
- add in events and social media integration
Let's clearly define the following content objects:
User
- e.g.: @thrufloNetwork
- e.g.: The HubVenue
- e.g.: Hub WestminsterGroup
- e.g.: Friday Night Drinks
User
s can join Network
s. Network
s contain Venue
s and Group
s. User
s checkin to Venue
s and join Group
s. (Group
s can optionally be associated with one or more Venue
s).
- no actions (over and above basic !action word syntax highlighting)
- no badges (or donations or anything reputational beyond one-click appreciation)
- no jump to (or "to" fields in a reply)
- no proximity filtering with
Venue
s andGroup
s
When the User
opens Togethr, they see a Dashboard
that allows them to:
- login to their
Networks
- discover nearby
Venue
s - see what's going on near them (through a proximity-filtered, recent-first
Activity Stream
)
When they login to a Network
(equivalent to accessing hubapp.com
directly) they see:
- network info
- venues listing
- members directory
- message stream
The Venue
page provides:
- venue info
- events calendar
- resource booking
- message stream
The Group
page provides:
- group info
- message stream
The User
page provides:
- profile info
- message stream (messages sent by that
User
)
User
s have an Inbox
where they receive:
- messages sent to them
- messages sent to the
Group
s they're part of
Users can navigate up and down and between Network
, Venue
and Group
and can view a User
or Message
. As they do so, they can send a message to whatever they are looking at: "shout out" to a Network
or Venue
, "message" a Group
or User
or "reply to" a Message
.
Provide lightweight events:
- define an
Event
at aVenue
for a duration at a time and place - send an invitation
Message
to aGroup
and / orNetwork
and to individuals by email address - optionally restrict
Event
s to members ofNetwork
s orGroup
s - allow
User
s to accept or decline
Allow User
s to post to Twitter and Facebook from Togethr.