Resource Validation

In this section, we'll outline how the validity and reliability of resources used during the project were evaluated. Each type of resource was vetted using specific criteria to ensure accurate and trustworthy information.

1. YouTube Videos

YouTube was a key resource for learning new skills and exploring technical solutions. The following criteria were used to validate the reliability of the content:

• Engagement Metrics: Videos with a high number of likes and views were prioritized, as these metrics reflect community approval and usefulness.
• Commentary Validation: The comments section was reviewed to check if other viewers found the content accurate and helpful. Comments pointing out errors or providing alternative methods were also considered.
• Relevance and Quality: Tutorials that aligned closely with the project goals and had clear, step-by-step explanations were prioritized.
• Channel Credibility: Channels with a substantial subscriber base and a history of producing high-quality, relevant content were favored.

2. Code Forums (e.g., Stack Overflow, Unity Forums)

Forums provided solutions to coding challenges and were validated using the following methods:

• Related Answers: For every question, multiple answers were reviewed to identify a consensus or the most commonly accepted solution.
• Approval Status: Answers marked as “Accepted” or highly upvoted by the community were considered more reliable.
• Comment Feedback: Comments on answers were checked for additional tips or reports of errors in the suggested solution.
• Testing the Code: Any code snippet or solution was implemented and rigorously tested in the project environment to ensure it worked as intended.
• Forum Credibility: Answers from experienced forum contributors (as indicated by reputation points or badges) were prioritized.

3. Resources from Popular Trusted Companies

For tools, platforms, or documentation from companies such as Samsung and Google, the following rationale was applied:

• Corporate Reliability: Samsung and Google are established, trusted brands with proven track records in their respective fields.
• Official Documentation: Resources obtained from official websites, SDKs, or APIs were used, ensuring the information was up-to-date and accurate.
• Industry Standards: These companies set industry standards, meaning their documentation and tools could be relied upon without the need for additional validation.

This approach to resource validation ensured that all external content used during the project met a high standard of reliability, ultimately supporting the success and accuracy of the final deliverables.