Reference · PodsyLive
Concert discovery and social planning in one app.
We developed the iOS and Android apps, real-time chat, and back-end infrastructure end to end.
- Status
- Live · in development
- Field
- Music and events
The work
PodsyLive brings concert discovery, planning with friends, and event-specific communication together in one community platform.
We built the React Native app alongside Node.js and Python services. Real-time components such as event chats and iOS Live Activities are central to the product experience.
The app is live in both stores and continues to evolve through regular releases.
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.
Scope
- iOS and Android
- Back end
- Real-time chat
- Store releases
Technologies
- React Native
- Node.js
- Python
- MongoDB
- Live Activities
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
