Case study
The social flow that continues after the concert is over.
PodsyLive
The liveliest moment of a concert does not start with a ticket, nor does it end after the doors are closed. PodsyLive is a social app that carries this interest after the event — we developed it from the idea to the product on the air.
- Alan
- Music & Activity
- Our role
- Product development
- Type
- Mobile application
Problem
When the event ended, engagement ended too.
The interaction around the concert is squeezed into a narrow time frame: the day of the event rises, the next day falls. The content shared by the participants is scattered on scattered platforms and dispersed before the community is formed.
The need was a flow that centered on the activity but continued to live on after that.
Approach
Core flow first, then expansion.
We built the product on a single core stream: the activity, the content tied to that activity, and the interaction around the content. We have deliberately postponed side features — there is no point in expanding without retaining the core.
We continued the development in short cycles; a working version was released in each cycle and the next scope was determined according to the feedback.
Stack
What we used.
- Client
- mobile
- Service
- API
- authentication
- Process
- Product Development
- CI/CD
Result
From idea to live product.
PodsyLive went live with the core stream defined. For us, this case is a record of our ability to develop end-to-end products alongside the integration business.
- Core flow first, expansion later
- Short cycles, version running on each cycle
- Single team from design to broadcast
Are you going to build a product from scratch?
Tell the idea — let's separate what is core and what is postponed together.