Inspiration
VibeSync was born from a simple but loud realisation: Gen Z lives in a constant emotional bandwidth crisis. Everyone is overflowing with inputs — content, conversations, deadlines, burnout cycles — but no system actually syncs with how we feel in real time. Traditional AI tools are extremely IQ-heavy but EQ-blind. They respond, but they don’t understand.
We wanted to flip the script. Instead of building another “smart” tool, we wanted something emotionally intelligent, something that vibes first and computes second. That became the origin story of VibeSync — a lightweight, EQ-powered AGI layer that reacts to mood, emotional context, and intention.
In short: We built what we personally needed — an always-on emotional co-pilot that cuts the noise and tells you exactly what you need to hear.
What We Learned
This project taught us a few hard truths:
Emotion is not a clean variable — it’s messy, subjective, contextual.
LLMs can imitate empathy, but getting reliable emotional inference requires a layered prompt strategy.
Lightweight systems outperform over-engineered stacks in high-iteration builds.
EQ-based systems need feedback loops to avoid becoming generic.
Users respond better to micro-actions than long advice blocks.
We also dove deeper into modelling emotions mathematically. A simplified representation that guided our design was:
E = f(c, t, i)
Where:
= context (conversational cues)
= tonal intensity (sentiment score)
= intention (what the user is trying to do emotionally)
This gave us a baseline to map emotional states to actions.
How We Built It
We kept the architecture brutally lean and execution-focused:
Frontend (Base44) Built a mobile-first flow with mood input, chat UI, vibe plan output, and emotional history screens.
Backend Logic (n8n Workflows) Created an orchestration pipeline:
user input →
emotion classifier →
micro-action generator →
final EQ-tuned response.
- LLM Emotional Engine Custom prompts classify user mood across:
emotional valence
intensity
cognitive load
action readiness.
- Feedback Memory Loop After each suggestion, user feedback updates a simple reinforcement function:
A_{next} = A_{current} + \alpha(R - \hat{R})
Where:
= future action weighting
= user rating
= predicted satisfaction
= learning rate
This allows personalisation without heavy ML.
- Minimal Infra Philosophy We avoided bloated stacks, ensuring low latency and zero crashes (after early overengineering failures).
Challenges We Faced
- Emotional Noise
LLMs over-interpret or under-interpret emotions depending on phrasing. We had to build multi-layered checks to stabilise mood inference.
- Avoiding Overengineering
The first version had too many features and crashed the UI. We re-architected everything around a lean EQ core.
- Personalisation Without Data Overload
Building memory without storing sensitive data required creative use of local scoring and anonymised emotional vectors.
- Balancing Empathy + Action
Users don’t just want emotional validation — they want direction. Designing micro-actions that were both empathetic and directive took iteration.
Log in or sign up for Devpost to join the conversation.