With a Single Users Table and nullable fields is typically more efficient for simple flows. It minimizes joins and keeps queries straightforward. You can easily check if registration is complete by verifying if name or username is null.

However, separating profiles into its won table provides batter normalization and scalability. If you expect profile growth or need more structed data. This also cleanly separate concerns between authentication (OAuth) and user profile details.

With a Single Users Table and nullable fields is typically more efficient for simple flows. It minimizes joins and keeps queries straightforward. You can easily check if registration is complete by verifying if name or username is null.

However, separating profiles into its own table provides better normalization and scalability. If you expect profile growth or need more structured data. This also cleanly separate concerns between authentication (OAuth) and user profile details.