COMMUNITY / AUTOMOTIVE
Pokaż Brykę
A community for car projects with vehicle profiles, modification histories, rankings, categories, a Spotted module and engagement features.
- Product
- Community platform
- Content
- Projects, photos, history
- Activity
- Rankings, reactions, Spotted
THE CHALLENGE
Turn car galleries into an evolving project history.
A car project changes over time, with modifications, photos, events and new goals. A simple gallery does not show this process or give the owner an organised vehicle profile.
The platform needed to bring together media publishing, change history, categories, rankings and community interactions. Licence plate privacy, moderation and protection against abuse also needed consideration.
A distinctive visual identity had to fit tuning and motorsport, while the information structure remained readable on a phone and with large numbers of projects.
Give car owners a place to document the development of their projects, and the community tools to discover, rate and comment on interesting builds.
SCOPE AND DECISIONS
What was designed, and why.
The functional scope is presented alongside decisions that affect everyday use and future product development.
- 01
User and car profiles with galleries, descriptions and specifications.
- 02
Project histories with dates, modification categories and updates.
- 03
Daily, weekly, monthly and yearly rankings, and vehicle categories.
- 04
Comments, reactions, messages, notifications and a Spotted module.
- 05
Moderation, content verification, licence plate privacy and an administration panel.
The project at the heart of the product
The main object is the car and its history, rather than a single post detached from its context.
An automotive UI language
Black, red, strong typography and track-inspired elements build character while retaining a clear hierarchy.
Multiple paths to discovery
Rankings, categories, recommendations and Spotted help users find projects regardless of how many people they follow.
Privacy within publishing
Cropping and licence plate masking are part of the upload process, and the result must be visible in both the thumbnail and full preview.
ARCHITECTURE
Product layers and their responsibilities.
The architecture is described in functional terms to make clear where logic, data, integrations and operations belong.
- 01
Community frontend → projects, rankings, galleries, messages and activity.
- 02
API → authorisation, votes, comments, relationships and visibility rules.
- 03
Database → profiles, cars, history, reactions, notifications and moderation.
- 04
Media layer → uploads, cropping, thumbnails and privacy protection.
- 05
Administration panel → review queues, reports, bans and statistics.
SELECTED SCREENS
The interface as part of the whole process.
The screenshots show the appearance and how users are guided through the main tasks.
OUTCOME
What the project delivered.
Specific product, process and deployment capabilities delivered by the project, without invented metrics.
- A coherent model for car profiles, galleries, modifications and project history.
- Discovery through rankings, categories and recommendations.
- A Spotted module connecting community photographs with car owners.
- A foundation for messages, notifications, reactions and comments.
- A moderation panel and processes addressing privacy in published photographs.
NEXT PROJECT
AISeeRisk
A security audit platform combining an authorised scope, reliable evidence, risk prioritisation and controlled remediation with subsequent verification.