Present: Doug W (Minutes), Raphael F (Mission and Vision), Raphael W (Development), Martin S (User Needs) and Sara P (Design)

Apologies: none

[Meeting begins 10:30]

RW: Update that Development has decided to split the Front-end into Web Front-end and Mobile Front-end.

• Building of separate mobile view with stripped down functionality.

SP: Proposal within design to integrate Design with the Front-end to reduce work repetition and generally improve work-flow.

RW: Presented;

• Current Web-view development
• Mobile-view UI with Angular framework demo page

SP: Update on Design work with Laura;

• Items originally on far left, Manuele suggests moving to left of map.
• Wall on left.
• Groups/communtites/etc on far left.
• Proposal that start-page has local wall and info (a window into Yunity for prospectives).
• 2 buttons easily visible for share and receive.
• Manuele suggested active chat on far right. Concerns within design that poor implementation of chat could lead to a migration of physical community to online community. [User Needs issue?]
  RF: Responds that chat is a necessary feature for many coming from Facebook.
  MS: Responds that chat encourages Yunity use, leading to more sharing and physical community.
  [Long discussion on chat feature]

SP: Does Design need to factor in adverts (for participating stores)?

MS: Yunity page explicitly states no adds.
RF: Participating stores will eventually receive 'good advertisement' from being
FoodSharing/Yunity compliant.

MS: Update on User Needs, presents mockups;

• Store mockup
• Event mockup

[Long discussion on UI]

RW: Responds that whatever UI design is, Dev can get on with developing agreed core functionality.

MS: Discussion with User Needs suggests need for a voting feature for the platform to keep in touch with what user needs really are.

RW: Asks that User Needs could summarise a list of all strictly necessary features for the Dev team.

RF: Questions whether the Coco is useful in it's current format where the heads of branches aren't able to make decisions at Coco meetings. Suggests that the team could perhaps trust the Coco to make some decisions on their behalf. A general concern that the current Coco protocol doesn't address all eventualities.

[General agreement]

SP: Asks for clarification whether Design is just to take mockups from User Needs (Martin) and work upon them (or reject if really bad)?

MS: Responds that this is the case.

SP: Suggests simplification of store feature to "I can" or "I can't" and the addition of an emergency request feature (e.g. no-one has signed up for tomorrow and someone is required).

SP: Asks to confirm that current work for design should be to connect existing work with the new

MS: Responds that this is the case

[Meeting ends 11:30]

Mockups

Mockup event

Mockup store