How should I design if I have to store multiple social platform profile?

I think you need to ask yourself what the relationship is between these various entities. user_profiles, for example, appears to be a 1-to-1 with the users table and so it would seem redundant in this case. A user can only have one name, age, etc. and so I would store these attributes on the users table directly. Incidentally, age changes and so I would store birth date instead and calculate an age accordingly.

I also wouldn't store things like followers on the platforms table since a platform will have many followers. Instead, store data that is unique to a platform instance on your platforms table and link things like users through a platforms_users table.

In the case of relating users to platforms, these three tables: users, platforms, and platforms_users are all that is needed to track those associations. In other words, your users and platforms have a many-to-many relationship and the platforms_users table serves as the pivot to form that relationship.

From this point, any additional related attributes to users or platforms can be stored in their own respective tables and, depending on their relationships, linked back directly or through other pivot tables.

@zidance Most “connect your account” or “login with X” services are based on OAuth, so when the user approves the connection you’ll get an OAuth access token to act as that user. So you can merely have an access_tokens table with a foreign key pointing to the owning user. You’ll also need to store the service name, and you could also optionally store the service’s unique identifier for the user in this table.

So I usually have an access_tokens table that looks something similar to this:

$table->id();
$table->foreignId('user_id')->constraint();
$table->string('provider'); // Twitter, Facebook, etc
$table->string('provider_id')->nullable(); // Users ID on external service
$table->string('access_token');
$table->string('access_token_secret')->nullable(); // For services using OAuth 1.x, i.e. Twitter
$table->unique(['user_id', 'provider_id']);

The unique constraint ensures a user can’t connect to the same service more than once.