Here is a mockup of my data relationships for a Marketplace app with Coaches (Fitness), Companies, and Attendees. Here’s how it functions:
Coaches - Create Profiles with Photos, Videos, Hourly Rate, Reviews.
Companies - Create Profiles with Photo, Rooms, Reviews, and Events.
Attendees - Minimal Profile and ability to favorite coaches or Events
How it works:
Coaches - Search for Company Events that are Hiring.
Companies - Search for Coaches to Hire… or post events that Coaches can apply to.
Attendees - Search for Company Events to Attend or Search for Coaches they can Favorite/Follow.
**My goal is Speed and Scalability.**
My biggest questions/hangups:
- Should Profiles be separate data types… or should I use the User Data Type as the profile?
- Is it better to user Primary/Foreign Keys everywhere to link Data Tables… or is choosing “List of Data Type” on corresponding tables enough? (@NigelG @boston85719 @jesse.r.hunter I see your names on a couple of the Join Table threads I’ve read here.)
- I read the “Ultimate Guide to Bubble Performance” by @petter (which was awesome) and there is some suggestion to create Search Data Types. Basically a truncated data type just for that search. Does this mean a data type that is linked with multiple tables… or a data type that has duplicated inputs that stemmed from multiple tables?
- Trying to do availability for Coaches based on A) Usual Days of week and times available, and then cross referencing B) Blocked out dates/times. Any tips on how to do this without creating a huge mess?
Would love feedback, suggestions, ect. Any help would be great.
*Also… if any of this is a “piece of cake” for anyone… what do you charge for an hour or two of coaching?