We have produced an intuitive user interface with clear tabs, making it easy to navigate. Throughout the development we prioritized user experience, ensuring each detail was carefully considered from the user's perspective.

However, when we showed our tool to a member of a different team, it was suggested that we add an "All episodes" note to make it clear that the episodes page contained all the episodes, and also we were suggested to move the names of the tabs to the middle for a cleaner look. On the good note, we were told that the UI did not distract from the overall podcast listening experience.

The main goal within functionality was ensuring seamless episode listening and easy episode discovery for the users. We have successfully implemented the core requirements related to functionality part of the project.

Following user feedback, we were told that the current features work well without any concerns raised. However, incorporating additional optional requirements could further enhance the functionality of the podcast."

Our platform has undergone some testing, during which it has demonstrated consistent stability without experiencing any crashes or technical errors. However, it's important to note that the platform has not been subjected to heavy usage scenarios, which may affect its reliability under more severe conditions.

While user feedback has been positive regarding stability, further testing is certainly required to ensure robust performance.

Our podcast makes use of AI to generate most parts of it, including script, audio and image generation, meaning it might take up some time to load the episodes, especially if the user suggestions feature is used. Improvements could be explored by experimenting with alternative models and utilizing additional Python libraries. Additionally, as we integrated multiple APIs during development, it introduced some dependencies on charging services, potentially resulting in occasional or permanent feature limitations."

User feedback highlighted that episodes took longer than expected to generate. It's important to note that immediate generation isn't feasible, especially for the unique topics. However, we realise that there is room for improvement in speeding up the generation process, which we will address to enhance the overall user experience.

Our platform works best on the desktop website and even though it remains accessible on smartphones and tablets, it was primarily designed for a desktop website usage. On the positive side, it works well across different operating systems.

Multiple members of other teams have said it would be very convenient to comfortably use the podcast on a smartphone by either implementing a mobile version of the website or by uploading the episodes of our podcast to streaming platforms such as Spotify or Apple Podcasts. We have taken a note of this feedback and are committed to addressing it in the near future.

The podcast is fairly easy to maintain as episodes could be manually generated by simply adding a topic. Also, as script, audio and video generation files have been coded separately, it is easy to fix a bug within each part or add a new feature to a specific part of the generation process. This modular approach facilitates efficient maintenance and future enhancements to the podcast platform.

Although we successfully met the core requirements, additional planning could have facilitated the implementation of more features. Our approach to work allocation was effective; each team member was assigned a big part of the project, allowing for focused expertise and efficient integration of project components. This method minimized the need for extensive explanations or collaboration on individual sections, as team members were proficient in their respective areas and could easily fix a bug or implement a new feature, if needed. However, we could have also spent less time researching and have started coding sooner as this would have allowed for a better functionality without compromising the quality of our project. Finally, we adapted well to changes and incorporated additional requirements as needed. as well as addressing the challenges we faced whether they related to coding or other project-related complexities.