I'm introducing the concept :

Suppose a webapp aiming to suggest some meetings to targeted people so that they can participate to at least one of them. So there's a page listing the items and a page showing the details of each item, when clicking.

Let's illustrate the meetings list page:

enter image description here

So here we see two published meetings waiting for participants.

So let's click on the first item: Engineers Meeting, displaying the detail page:

enter image description here

We can detect that Michael (the creator) and Kevin are participating (obvious for Michael since he's the creator).

So to sum up the use case: Michael wants 9 participants for his meeting. Kevin has seen the publication and clicked on "Participate". (I don't show the Participate button in the mockup since it doesn't matter).

All this workflow seems (I think) to be intuitive for any users.

So now my new use case, a little touchy:

James publishes a Meeting announcement waiting for 10 participants (him + 9 others).
However, he expects some people to be present like, let's say, Julia.
So while creating the meeting announcement, James marks Julia as being a "Favored participant". Meaning that Julia is likely to NOT participate BUT her place is LOCKED anyway unless she desists.
This would prevent 9 other people participating, getting the meeting complete/full, BEFORE she could participate too.

So my question is: how should I represent the people effectively participating and favored people (a place locked for each one) that should participate, but are not forced to?

My expectations are:

  • Any user (potential participant) MUST see the favored people, so that they can know which people are likely to participate.
  • A favored people that has not participated yet MUST not be counted as a participant.
  • A meeting MUST not be full before favored people respond. They are priority.

I imagine this way:

enter image description here

Any better idea?

2 Answers 2


I would suggest you to use iconography for this. You can treat part above the line as list view and once user tap on it show the detailed view. (As shown below)

IMO you can use the entire block in list view.

enter image description here

enter image description here

  • The favored participant has been shown with a heart. (Obviously the ticked one are those who have accepted the meeting)

  • The help icon will help other participants including favored one to know more about the favored feature.

  • "Waiting for XYZ more to join" is self explanatory.

enter image description here

  • Once All 9 participant accept the meeting except "Favored" one. Simply use the favored person name there to grab the attention i.e "Waiting for Julia to join" (I am not sure you have more than one favored participant)

enter image description here

  • Lets say favored participant rejects then invitation. You can make the text catchy for the last person to join. i.e "Waiting for last engineer to join"

enter image description here

  • In cae favored participant accepts the invitation. We can show the participant as regular participants who have accepted the request.
  • Amazing! That's exactly what I should do. Thanks a lot for this answer :)
    – Mik378
    Commented Jul 20, 2014 at 19:33
  • Pleasure is mine :) Commented Jul 21, 2014 at 2:55

Maybe you are trying to reinvent the wheel. Restaurants, theatres, and other venues have the concept of:

  • Reserved seat
  • Free seat

And they also have a limited number of seats for each session (dinner, play,...). When you want to buy a seat, they display you the number of available seats as:

Total seats - Reserved seats

This way, if Julia reserved a seat, no one will take her place.

One thing that you are missing in your application, is the opportunity for someone to give up their seat. If Julia has a reserved seat, but she knows that she will not attend, it makes sense that she can tell that to the organizer, so that they stop reserving her seat, and someone else might take her place.

  • Sorry but I'm not sure that you well interpreted the post. I don't want a case when Julia gives its response too late, meaning that the meeting is already full as soon as she wants to participate or desist. I did implement the functionality of "cancelling" a participation. (Julia or any other participant may cancel/desist). The point is I expect Julia to have priority against any other participants: if I expect 10 persons, and already 9 persons said "Ok for me", I don't want to accept a 10th BEFORE having the response of Julia => she's priority. I hope I well explained ;)
    – Mik378
    Commented Jul 20, 2014 at 11:01
  • "This way, if Julia reserved a seat, no one will take her place." => of course, but the point is that Julia may reserve its place too late... perhaps busy, or other emergency etc. I want to KEEP its place unless she desists explicitly, in this case letting someone take her place. It's like saying: "Julia is my best friend, I do want her presence unless she can't come.
    – Mik378
    Commented Jul 20, 2014 at 11:10
  • 1
    With slight re-wording of @jff's answer, this is still accurate. The organizer can reserve Julia's seat for her, and it is assumed that the seat is reserved for her until she explicitly says that she will not attend. In that case, you can simply show the reserved seats (and for whom they are reserved) and the free seats (which anyone can take). A reserved seat gets converted to a free seat either if Julia turns down the seat, or if the meeting organizer changes their mind about reserving the seat for Julia (ex: Julia is on vacation and isn't able to respond, so the organizer frees her seat).
    – nadyne
    Commented Jul 20, 2014 at 18:17
  • Thanks @nadyne, Dinesh Golani has illustrated your answer with a little improvement.
    – Mik378
    Commented Jul 20, 2014 at 19:35

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.