Core Match Content & Fundamentals

Introduction

To create extensions that improve functionality and bring joy to users, it's important to focus on user-centered design, thoughtful layout strategies, and effective use of color and typography. Let's explore how you can seamlessly integrate your extensions with the Simple experience. If you plan to publish your App on the Marketplace, please review our Match Market Application Guide for the Design and Usability section.

Crafting your interface

Your viewing interface can operate within a standalone frame, allowing development with standard HTML, CSS, and JavaScript, much like building a single-page application. You can leverage various frameworks and libraries, for instance, building UI components with React or Vue, and styling with Tailwind CSS or Bootstrap.

While we don't mandate a fully native viewing interface, we believe that a more native-feeling application can better engage fans and deliver an exceptional user experience.

Design principles

Your interface should adhere to these core principles:

• Fan-Centric: The purpose and value of your application should be defined around fan needs, addressing their unique pain points.
• Simple and Intuitive: Your application should be easy to operate, requiring minimal learning to get started, and should abstract code visually rather than complicating it.
• Polished Design: Maintain consistent design elements such as colors, typography, and button styles throughout your application. This enhances user experience and makes your app easier to navigate.
• Inspire Creativity: Your application should not hinder the flow of watching and discussing matches. Avoid unnecessary steps or options that might interrupt a user's immersive experience.
• Clear Language: Use concise and straightforward copy. It should guide users and connect the relationship between visuals, layout, and usability.
• Accessibility: Strive to make your application accessible to all users. This means ensuring it adheres to accessibility standards and best practices.

Design guidelines

Select a color scheme that aligns with the match's purpose and atmosphere. The World Cup Football Portal primarily uses the Inter font; we recommend adopting it for consistency.

Common Error Messages

If you encounter such errors, please verify that your application is not excessively rate-limiting requests. For example, frequent polling of resource creation status or executing a high volume of concurrent API calls can trigger this issue.

{
    Messages: "Too Many Requests",
    Code: "too_many_requests",
    External References: Empty,
    Details: [],            
}

Data API Integration

Our APIs facilitate interaction with match data through user-friendly objects and methods. These APIs enable you to manipulate existing match elements or introduce new ones within your interface.

Summary and Outlook

Let's explore the core files needed to build your match information display, covering structure, styling, and dynamic content. You can learn more about application configuration, structure, and necessary files in our detailed documentation. Feel free to experiment and adjust as you explore and modify the template.

Practice is the best way to learn, and this platform offers a safe environment for experimentation.