"Your app is empty man!" / How to modify UI/UX to stop this kind of feedback?

I own an application aiming to make people meet each other around activities/outs.
There are two ways of suggesting an activity/out to other members:

  1. Inviting anybody at once. All members would then be able to see the suggested out and participate to it.
  2. Inviting only certain members, by selecting ones of our choice (members are well-listed in another tabs and selectable). Only those members would be able to see the out and participate to it. Full confidentiality.

I have a real issue with UX.
To introduce the issue, here's a basic and light structure of my current UI.

enter image description here

Basically, two tabs, listing actual suggested outs (current or future ones) or past ones; and a list of the out's main contents.

Main feedback from my users: "The app sounds empty, there aren't many suggested outs!"

The UI/UX clearly doesn't emphasize that "you, users, you are not expected to see every out, you are expected to only see outs that concern you, meaning to which you are invited in! ".

I briefly explain them: "It's like e-mails, if I send an e-mail to Julia, only Julia receive it, not you! So if you only see 3 displayed outs, it doesn't mean that any other member can't see 3000 outs in their side. All depends of whether they are invited or not."

When I explain that, everyone LOVES the app and really starts to invite other members and suggest outs themselves, without waiting. They become active and not passive.

How to transform my UI so that the user understands the idea of privacy/confidentiality of outs, and don't assume that "if I don't see many outs in THEIR side, it does mean that the app is 'desert'".

I thought about an interactive tutorial at the first launch of the app. I made it some months ago, but I noticed that majority of people skipped it, thinking that it's a concept already known with other apps and not innovative.
However, the confidentiality feature, is quite innovative compared to other apps in the market and should really be noticed by users.
So IMO, it's clearly a UX-issue in-app.

Tags: