BANDXBandX
A platform for presenting, publishing, and connecting Iranian independent rock and metal bands.
To protect data and infrastructure, a functional diagram replaces a real screenshot.
How does the project work?
The four stages below show the product’s primary flow without exposing sensitive data or details.
- 01 / 04
Band profile
Each band’s identity, members, and introduction are recorded in one reference.
- 02 / 04
Releasing work
News, music, and related content are presented to the audience.
- 03 / 04
Discovering the scene
Users find new paths through bands and independent content.
- 04 / 04
Connection
The platform supports familiarity and networking among scene participants.
An active scene without a central reference
Independent music groups introduce themselves across scattered social networks and channels. Content gets published, but the connection between a band’s identity, members, work, and news is easily lost.
BandX emerged as an effort to build an independent, structured reference for this community.
Profiles, content, and connection in one place
The product was not only a music magazine or a band directory. The idea was for every band to have a referable identity, publish its own content, and be seen within a wider independent-scene network.
This combination connected the needs of content publishing and artist discovery in one shared product model.
Balancing public discovery with identity ownership
Pages needed to be browsable for audiences while bands still felt their identity had not been reduced to a temporary feed. The profile and content-archive structure mattered for retaining that continuity.
Publication-policy and community-management details are not documented in the public version and require review of archive data.
A product outside the constraints of public networks
An independent platform allows its content structure, categories, and discovery path to be designed for the logic of that community, rather than a general social-network algorithm.
Conversely, sustaining such a platform requires continued community participation and a clear operating model—costs that were part of the product’s reality from the beginning.
An archived-product case study
BandX is now presented as an archived project, and no public domain link is given until the service status is confirmed.
A product sample and archival images are available through private contact. This page deliberately avoids fabricated screenshots or statistics.
A social platform is not built with features alone
The product’s technical value is necessary, but not enough to keep a network alive. Participation cycles, content ownership, and member return must be designed alongside the interface and infrastructure.
This experience later informed a product-led view of content and community systems.
What was built within the project scope.
This list is based on project outputs that can be stated publicly—not speculative features or unverified technology.
- 01Product-model definition
- 02Band profiles
- 03Content publishing and archive
- 04Artist discovery path
- 05Interaction and networking
- 06Independent product management
- COMMUNITY PRODUCT
- CONTENT PLATFORM
- PRODUCT DESIGN
- WEB EXPERIENCE
Do you have a similar challenge?
If your project sits between web, operations, content, and automation, we can first clarify the problem and the shortest path to build it.
Start a conversation on Telegram