Support common usage of shared resources in a group

User story:
A foodsharing group collectively owns a cargo bike which can be used for pick-ups. The storage and maintenance are organised in a place and through activities (similar as taking care of a food share point). But how do I know whether the bike is available or not and how can I reserve it for my pick-up?
Another story:
A group of cycling without age decided to use Karrot. It’s about coordinating rides for elderly with rickshaws. The places are the different elderly homes where you offer rides, pick up the people and drop them off again. Certainly you can do several rides with one rickshaw, but how to coordinate across places?
Or booking rooms.
Or having a paid license for some kind of digital product which only one user at a time can use.

Complexity:
If the resource is used only in one place, the activities could suffice. A calendar view would help to determine if activities overlap or when there is no activity ‘booked’.
It needs more design for the more relevant use case, to have one resource which somehow can be booked across different places.

Outcomes (or what needs to be done to move forward):
pick this up, think further about design, ask questions, potentially bring this to a meeting, development further down the road

Also referring to Application to the Prototype Fund as a source of ideas and collaboration.

That is the case now here in Gothenburg! :slight_smile: They created a group on Karrot and I think they put up a bunch of activities with a time range (say 1pm-4pm) so people who want to book the bike can sign up for it. I will join the group to be sure what I’m talking about…

My design thoughts
Feature activities seems to be useful, although this is more like a non-intended use of it and has certain limitations:

  • a lot of missed activities counting when people do not book the bike
  • calendar view as mentioned above is missing, to see when it’s taken or available
  • no focus on the resource itself, showing info and picture, rather focus on the booking/activities
  • place requirement (maybe that’s good?)

I can definitely see the design of this feature based on the activities feature, but what I think the points above should be considered and maybe redesigned, the crucial difference being the last one, allowing the user to start the flow of booking something displaying the share resource first

1 Like