Hey everyone, I’m hopeful someone can help as I’m at the stage where I’m ready to pull my hair out…
I’m having difficulties with my app and wondering if the origins of the problems I’m having are bigger than ‘workflow’ based— it could go back to the data structure and how I’ve setup my databases.
Context:
I’m working on a podcast app and would like to have a list of ‘shows / podcasts’ that when clicked, enter into the next page showing a list of ‘episodes’ for that Podcast. When the ‘episode’ is clicked, I’d like to load a new page unique to that specific episode. I’m using repeating groups for this and have got it working up to a point.
So far I can get this to work [see page ‘PODCASTS’],
but when I click through to the next page, I encounter problems.
As you can see in the image above, nothing is loading (I’ve edited and tried to fix it so many times it needs to be completely rebuilt at this point). I’ve had this Repeating group working to the point where it would load a list of ALL Episodes, but they are not split up by ‘parent’ podcast.
IE: Joe rogan Experience show has episodes from ‘No Code Podcast’ as well as ‘Joe Rogan’
I’m looking for guidance on how I could set this up. I’m also wondering if I have my data structured properly (and if this might be the source of my problems)
Regarding the database:
I have a database for ‘Podcast’ with the following fields
my thinking is that this is the list of fields pertinent to the ‘podcast’ data type: List of episodes, the PODCAST* description / PODCAST* Thumbnail / PODCAST* Title. I then have a SEPERATE database for EPISODE, where I capture similar data but specific to the Episode (rather than the Podcast)
*nb: these fields are different from EPISODE- Description / EPISODE - thumbnail / EPISODE - etc…
How can I pass this data along from one page to another?
What is the proper workflow for this to maintain the parent / child relationship?
What should my repeating group in the “EPISODE DETAIL” page look like?
Further, I have all the data setup such that the actual media content (the audio file for the podcast episode {episode - MEDIA CONTENT in the db}) is a separate database. I’ve done this with the thinking that if I can call this specific data only when required then I wont have to constantly pass this throughout various parts of the app where it is not needed, and performance will be better.
Please advise if this is best practice.
Many thanks for your help and advice fellow Bubblers!