DEV Community: Apoorv Karanwal

[Boost]

Apoorv Karanwal — Thu, 11 Jun 2026 10:57:16 +0000

Apoorv Karanwal

Apr 25

The Psychology of Practice: Flow State for Musicians #Apoorvkaranwal #melodymaster

#ai #programming #music #musicians

2 min read

Why 90% of AI Apps Fail (And What the Top 10% Do Differently)

Apoorv Karanwal — Thu, 11 Jun 2026 10:37:17 +0000

If you have been active on Twitter, LinkedIn, Product Hunt, Reddit, Indie Hackers, Hacker News, or Dev.to recently, you have probably noticed something impossible to ignore.

Every single day, new AI applications are launching.

An AI note-taking app.

An AI writing assistant.

An AI coding tool.

An AI study planner.

An AI legal helper.

An AI business coach.

An AI resume builder.

An AI logo generator.

An AI startup idea generator.

An AI tool that builds another AI tool.

At first glance, it feels like we are living in the greatest software revolution of our lifetime.

And in many ways, we are.

The barrier to building software has collapsed.

A solo developer can now build in a few weeks what previously required a full engineering team, designers, cloud engineers, copywriters, and sometimes even data scientists.

You can use Vertas, ChatGPT to write code. (If you are confused what is Vertas it is my project in development ones it ready you all can enjoy its benefits)
You can use Vertas, Cursor or Windsurf to build faster.

You can use APIs from Vertas, OpenAI, Anthropic, Google, Meta, or Mistral.

You can use Vertas Ai Workspace, Vercel to deploy instantly.

You can use Stripe to accept payments.

You can use Vertas Ai Workspace, Supabase or Firebase as a backend.

You can use Framer, Webflow, Next.js or Vertas's Rainbow.js for frontend.

In short, building has never been easier.

But here is the brutal truth:

Because building has become easier, winning has become harder.

Thousands of AI products launch.

Most disappear.

Many never cross 100 active users.

Many never make even one dollar.

Many get a small launch spike and then slowly die.

Some trend for a week on social media and vanish completely.

Others become yet another forgotten link in someone’s bookmarks folder.

So the real question is not:

“Can we build AI apps?”

The real question is:

“Why do most AI apps fail even when the technology is so powerful?”

After studying successful startups, failed side projects, SaaS businesses, indie hackers, AI tools, developer communities, product launches, and user behavior, one pattern becomes extremely clear:

The AI products that win are rarely the ones with the most advanced AI.

They are the ones that understand people, pain, workflows, trust, and distribution better than everyone else.

And this is exactly where most builders lose the game before they even begin.

The Biggest Mistake: Starting With Technology Instead of Pain

Developers love technology.

We get excited by new frameworks.

We get excited by new APIs.

We get excited by new models.

We get excited by benchmarks.

We get excited when a new AI model beats another model by 3% on some leaderboard.

The moment a new model launches, many builders immediately start thinking:

“What can I build with this?”

That sounds like a good question.

But it is actually one of the most dangerous questions in product building.

The better question is:

“What painful problem can this solve better than existing solutions?”

That difference is massive.

Most failed AI apps start with technology.

Successful AI products start with pain.

Failed builders say:

“GPT-5 is powerful. Let me make something with it.”

Successful builders say:

“Customer support teams waste 5 hours daily answering repetitive tickets. How can AI reduce that to 30 minutes?”

Failed builders say:

“I want to build an AI PDF chat app.”

Successful builders say:

“Lawyers spend hours extracting clauses from contracts. How can AI help them review documents faster and more safely?”

Failed builders say:

“I want to build an AI study app.”

Successful builders say:

“Students forget what they study because they do not revise properly. How can AI create personalized revision loops?”

See the difference?

One is technology-first.

The other is problem-first.

Nobody wakes up thinking:

“I wish I had an app powered by a large language model.”

People wake up thinking:

“I need to finish my assignment.”

“I need to save time.”

“I need more clients.”

“I need to write better emails.”

“I need to understand this document.”

“I need to reduce my workload.”

“I need to grow my business.”

“I need to stop feeling overwhelmed.”

Users do not buy AI.

They buy outcomes.

They buy speed.

They buy clarity.

They buy convenience.

They buy confidence.

They buy money saved.

They buy time saved.

They buy stress removed.

AI is not the value.

The solved problem is the value.

This one principle alone separates serious builders from hobby project creators.

AI Is Becoming a Commodity

Here is something many AI founders do not want to accept:

AI itself is becoming a commodity.

A few years ago, adding AI to your product was impressive.

Today, it is expected.

Earlier, if you had an AI writing tool, people were amazed.

Now there are thousands of AI writing tools.

Earlier, if you had an AI chatbot, it felt futuristic.

Now every website has one.

Earlier, if your app could summarize PDFs, users were shocked.

Now users ask:

“Okay, but what else can it do?”

This is the new reality.

Most AI apps are using the same foundation models.

They are calling similar APIs.

They are using similar prompts.

They are producing similar outputs.

They are offering similar interfaces.

A text box.

A generate button.

A loading spinner.

A response.

That is not a product anymore.

That is a wrapper.

And wrappers are easy to copy.

If your entire product can be rebuilt by another developer in a weekend, you do not have a business.

You have a temporary demo.

This does not mean AI wrappers are useless.

Some wrappers become great businesses.

But only when they add something deeper:

A specific workflow
A strong use case
Better user experience
Domain expertise
Proprietary data
Trust and reliability
Distribution
Integrations
Automation
Team collaboration
Security
Brand
Community
Speed
Better onboarding
Better retention loops

In other words, the winners are not just adding AI.

They are building systems around AI.

That is where the real moat begins.

Why Most AI Apps Feel the Same

Imagine you are searching for an AI writing tool.

You open Website #1.

There is a text box.

You type your topic.

The AI generates content.

Then you open Website #2.

Again, a text box.

You type something.

The AI generates content.

Website #3.

Same thing.

Website #4.

Same thing.

Website #5.

Same thing.

After a while, everything feels identical.

Same landing page.

Same gradient background.

Same “10x your productivity” headline.

Same “powered by AI” badge.

Same free trial.

Same dashboard.

Same chatbot-style interface.

This is why users do not stay.

Because if your product feels generic, users treat it like a commodity.

They try it once.

They say, “Nice.”

Then they leave.

The problem is not that the AI is bad.

The problem is that the product is forgettable.

Successful AI products do not just answer prompts.

They create experiences.

They understand context.

They reduce steps.

They remember user preferences.

They fit inside existing workflows.

They help users complete an entire job, not just one small task.

That is the difference between a tool people try and a product people rely on.

A Demo Is Not a Product

This is one of the most important lessons in AI product building:

A demo proves that something is possible.

A product solves a complete problem.

Most AI apps fail because they are demos pretending to be products.

Let’s take an example.

Suppose you build an AI meeting summarizer.

The user uploads a meeting recording.

The AI generates a summary.

That is useful.

But it is still mostly a demo.

Now imagine a serious AI meeting product.

It automatically:

Joins your meetings
Records the conversation
Transcribes everything
Identifies key decisions
Detects action items
Assigns tasks to the right people
Sends follow-up emails
Updates Notion, Slack, Jira, or Trello
Creates reminders
Tracks whether tasks are completed
Learns your team’s communication style
Keeps a searchable memory of past meetings

Now the AI summary is not the product.

The workflow is the product.

That is where real value lives.

People do not want “AI output.”

They want the job done.

This is why the best AI companies think less like prompt engineers and more like workflow designers.

They ask:

“What happens before the AI response?”

“What happens after the AI response?”

“How does this fit into the user’s day?”

“What does the user still have to do manually?”

“What can we remove?”

“What can we automate?”

“What can we make effortless?”

The more friction you remove, the more valuable your product becomes.

The Hidden Metric: Trust

Most founders obsess over accuracy.

And yes, accuracy matters.

But in AI products, there is an even more dangerous metric:

Trust.

An AI product can be correct 95% of the time and still fail if users do not trust it.

Why?

Because users do not remember the 95 correct answers.

They remember the one embarrassing mistake.

If an AI email assistant sends one wrong email, trust drops.

If an AI legal tool gives one risky suggestion, trust drops.

If an AI finance tool gives one incorrect number, trust drops.

If an AI medical assistant gives one unsafe answer, trust collapses.

AI mistakes feel different from normal software bugs.

A normal app bug is annoying.

An AI hallucination can be dangerous.

That is why serious AI products invest heavily in reliability.

They use:

Guardrails
Validation systems
Human review
Confidence scores
Source citations
Fact-checking layers
Error detection
Retrieval-augmented generation
Testing datasets
Evaluation pipelines
Monitoring systems
Fallback logic
User feedback loops

This is where many small AI apps fail.

They launch quickly, but they do not build trust.

And without trust, users will not put your product into important workflows.

They might use it for fun.

They might test it.

They might share it once.

But they will not depend on it.

And if users do not depend on your product, retention will be weak.

No retention means no business.

Accuracy Alone Is Not Enough

Many builders believe that if their AI gives better answers, users will automatically come.

That is not true.

Better output helps, but it is not enough.

A product can have excellent AI output and still fail because:

The onboarding is confusing
The interface is slow
The pricing is unclear
The value proposition is weak
The target audience is too broad
The product lacks integrations
The user does not know when to use it
The output requires too much editing
The product does not fit into daily workflow
The founder has no distribution

This is why “better model” does not always mean “better business.”

Users do not compare products like researchers compare benchmarks.

Users ask simpler questions:

“Is this useful?”

“Is this easy?”

“Can I trust it?”

“Does it save me time?”

“Is it worth paying for?”

“Will I use this again tomorrow?”

If the answer is no, your model quality does not matter.

Speed Is a Feature

One of the most underrated advantages in AI products is speed.

People love fast products.

A slightly weaker answer in 2 seconds often feels better than a perfect answer in 30 seconds.

Why?

Because humans are impatient.

Waiting creates doubt.

Waiting makes people feel the product is heavy.

Waiting breaks flow.

The best AI products understand this deeply.

They optimize:

Response time
Page load time
Onboarding speed
Time to first value
Number of clicks
Input effort
Editing effort
Export speed
Integration speed

Speed is not just technical.

Speed is emotional.

If your product helps users reach the “aha moment” quickly, they feel value immediately.

And the faster users feel value, the more likely they are to stay.

That is why the first session matters so much.

If users sign up and do not get value within the first few minutes, most will never return.

Distribution Beats Features

This is another painful truth:

The best product does not always win.

The best-distributed product often wins.

Many developers believe:

“If I build something great, people will come.”

No, they will not.

The internet is too crowded.

Users are busy.

Attention is expensive.

Nobody cares about your product until you give them a strong reason to care.

This is why many technically excellent AI products fail.

They have good features, but no distribution.

No audience.

No content engine.

No SEO.

No partnerships.

No community.

No sales motion.

No founder brand.

No viral loop.

No marketplace presence.

No clear niche.

Meanwhile, a simpler product with better distribution grows faster.

Distribution can come from many places:

SEO
YouTube
LinkedIn
Twitter/X
TikTok
Product Hunt
Reddit
Newsletter
Cold email
Partnerships
Affiliate programs
App marketplaces
Chrome Web Store
Slack/Notion/Shopify integrations
Founder-led content
Community building
Word of mouth

A weak product with distribution may get users.

A great product without distribution may stay invisible forever.

The top 10% of AI builders understand this.

They do not just ask:

“What should I build?”

They also ask:

“How will people discover this?”

The Niche Advantage

Most AI apps are too broad.

They say:

“AI assistant for everyone.”

That sounds big.

But in reality, it is weak positioning.

When your product is for everyone, it feels like it is for no one.

Compare these two:

“AI writing assistant”

vs.

“AI writing assistant for real estate agents that creates property listings, client follow-ups, and local market updates.”

The second one is more powerful.

Why?

Because it speaks directly to a specific audience.

A real estate agent immediately understands the value.

The product can have better templates.

Better workflows.

Better language.

Better examples.

Better marketing.

Better SEO.

Better pricing.

Better customer support.

Niches create clarity.

Clarity creates conversion.

Many successful AI companies start with a narrow wedge.

They dominate one specific use case.

Then they expand.

Do not start by trying to be “AI for everyone.”

Start by becoming painfully useful for someone specific.

The Real Moat Is Not the Model

Many founders worry:

“What if OpenAI builds this?”

“What if Google adds this feature?”

“What if a bigger company copies me?”

These are valid concerns.

But the answer is not to avoid building.

The answer is to build something that is not just a thin model wrapper.

Your moat can come from:

1. Workflow Depth

You solve the entire process, not just one prompt.

2. Proprietary Data

Your product improves because of unique data, user behavior, or domain-specific knowledge.

3. Distribution

You have an audience, brand, SEO, community, or sales channel others cannot easily copy.

4. Integrations

You are deeply connected to tools users already use.

5. Trust

Users rely on you because your product is safe, reliable, and consistent.

6. User Experience

Your product is easier, faster, and more pleasant than alternatives.

7. Switching Costs

The more users store, create, automate, or collaborate inside your product, the harder it becomes to leave.

8. Brand

People remember you, recommend you, and associate you with a specific problem.

A model is not a moat.

A complete system can be.

Pricing Is Part of the Product

Many AI apps also fail because their pricing makes no sense.

They either charge too little and lose money, or charge too much before proving value.

AI products have real costs.

Every generation can cost money.

Every image, transcript, document, or agent workflow can consume compute.

If your users are heavy and your pricing is weak, growth can actually hurt you.

This is why AI founders need to understand unit economics.

You need to know:

Cost per generation
Cost per active user
Average revenue per user
Gross margin
Free trial abuse
Usage limits
Upgrade triggers
Retention by pricing tier
Which features create willingness to pay

Many AI apps attract free users but fail to convert them into paying customers.

Free users are not a business.

Usage is not revenue.

Traffic is not profit.

A real AI product needs a pricing model that matches the value delivered.

If your product saves a business 10 hours per week, you can charge more.

If your product is just a fun toy, users may not pay much.

The closer your product is to revenue, productivity, or mission-critical work, the stronger your pricing power becomes.

Retention Is More Important Than Launch Hype

A launch can give you attention.

Retention gives you a business.

Many AI apps get initial excitement.

They launch on Product Hunt.

They get a few tweets.

They receive some signups.

They maybe go viral for a day.

But after that, reality hits.

Do people come back?

Do they use it weekly?

Do they use it daily?

Do they invite teammates?

Do they pay?

Do they complain when it is down?

Do they feel pain if they lose access?

That last question is powerful.

If users would not care much if your product disappeared, you do not have strong product-market fit.

The top AI products become part of someone’s routine.

They are not just interesting.

They are useful again and again.

Retention usually comes from:

Repeated use cases
Stored history
Personalization
Integrations
Team collaboration
Notifications
Automation
Clear ROI
Workflow ownership
Trust

If your product is used once and forgotten, it is not a business yet.

It is an experiment.

What the Top 10% Do Differently

The best AI products are not winning by accident.

They usually do a few things extremely well.

1. They Start With a Painful Problem

They do not build because AI is cool.

They build because someone has an expensive, repetitive, annoying, or urgent problem.

2. They Choose a Specific Audience

They do not target “everyone.”

They target a clear group with clear needs.

3. They Solve a Workflow, Not a Task

They do not stop at generating output.

They help users complete the entire job.

4. They Build Trust

They use citations, checks, guardrails, review systems, and transparent behavior.

5. They Make the Product Fast

They reduce waiting, clicking, thinking, editing, and setup.

6. They Own Distribution

They do not depend on luck.

They build channels that bring users repeatedly.

7. They Measure Retention

They care less about vanity signups and more about repeat usage.

8. They Understand Costs

They know their margins, usage patterns, and pricing logic.

9. They Improve With Data

They learn from users and make the product smarter over time.

10. They Focus on Outcomes

They do not sell AI.

They sell results.

The Future Belongs to Problem Solvers

Every year, AI models will become more powerful.

They will get faster.

They will get cheaper.

They will become more multimodal.

They will write better code.

They will understand longer context.

They will reason better.

They will connect with more tools.

But as AI becomes more powerful, the value of simply “having AI” will keep decreasing.

The real value will move upward.

From model to product.

From product to workflow.

From workflow to outcome.

From outcome to trust.

The winners of the next decade will not just be model collectors.

They will be problem solvers.

Because technology changes fast.

But human needs remain surprisingly stable.

People will always want:

More time
More money
Less stress
Better health
Better learning
Better communication
Better productivity
Better decision-making
Better opportunities
More control over their lives

If your AI product connects directly to one of these needs, you have a real chance.

If it only exists because a new model launched, it will probably disappear when the next wave arrives.

Final Thoughts

The biggest lesson from studying successful AI products is simple but powerful:

Do not fall in love with AI.

Fall in love with the problem.

AI is a tool.

A powerful tool.

A revolutionary tool.

A world-changing tool.

But still, just a tool.

A hammer does not matter if you do not know what you are building.

A model does not matter if you do not understand the user.

A feature does not matter if it does not solve real pain.

The real opportunity is not building something that “uses AI.”

The real opportunity is building something that makes people’s lives meaningfully better.

Something that saves time.

Something that reduces stress.

Something that increases income.

Something that improves decisions.

Something that helps people do what they already wanted to do, but faster and easier.

The future will not belong to builders who ask:

“What can AI do?”

It will belong to builders who ask:

“What do people desperately need?”

And then use AI to deliver that outcome better than anyone else.

That is the difference between an AI demo and an AI business.

That is the difference between getting users once and keeping them forever.

That is the difference between the 90% that disappear and the 10% that dominate.

In the AI era, building is easy.

Understanding people is the real superpower.

IF YOU LIKED THIS ARTICLE PLEASE COMMENT AND LEAVE ME A HEART 💖 OR UNICORD 🦄 FOR MY MOTIVATION ALSO GET READY I WILL PUBLISH VERTAS AI WORKSPACE AS SOON AS POSIBLE

The Psychology of Practice: Flow State for Musicians #Apoorvkaranwal #melodymaster

Apoorv Karanwal — Sat, 25 Apr 2026 13:14:39 +0000

Have you ever been practicing your instrument and suddenly realized that two hours have passed in what felt like ten minutes? Your fingers moved effortlessly, the music felt "right," and the rest of the world simply ceased to exist. This isn't just a good practice session; this is Flow State.

Coined by psychologist Mihaly Csikszentmihalyi, Flow is the state of total immersion in an activity. For musicians, it is the ultimate goal. In this guide, we explore the science of Flow and how to hack your brain to enter it every time you pick up your instrument.

1. The Science of the 'Zone'
When you enter Flow, your brain undergoes a process called Transient Hypofrontality. This is a temporary deactivation of the prefrontal cortex—the part of your brain responsible for self-criticism, doubt, and complex planning.
In Flow, your "Inner Critic" is silenced. You stop worrying about whether you're playing well and simply play. This allows your subconscious to take over, leading to faster motor-skill acquisition and deeper emotional expression.

2. The Three Conditions for Flow
To enter Flow, you must meet three specific criteria:

The Challenge-Skill Balance: The task must be slightly beyond your current ability. If it's too easy, you'll be bored. If it's too hard, you'll be anxious. The M.U.S.I.C System in MelodyMaster is designed to find this "Goldilocks Zone" by dynamically adjusting the difficulty of exercises.
Clear Goals: You must know exactly what you are trying to achieve in that moment (e.g., "I will play this 4-bar phrase perfectly at 90 BPM").
Immediate Feedback: You need to know instantly if you are succeeding. This is where MelodyMaster's real-time accuracy engine is your greatest ally.

3. How to Hack Your Flow with MelodyMaster
Kill Distractions: Use 'Deep Practice' mode. Turn off notifications and let the app's dark, glassmorphic UI pull you into the focus zone.
The 4-Step Warm-up: Start with a task you know well (like the C Major Scale) to build momentum and confidence before tackling new material.
MM GPT Mediation: Ask the AI assistant to set a 20-minute timer for "Deep Focus." Having a set container for your practice session helps the brain surrender to the task at hand.
Conclusion: Music as Meditation
Flow is not just about getting better at the piano or guitar; it’s about the joy of the process. When you practice in Flow, you aren't just learning a song—you are recalibrating your entire nervous system for peak performance.

Ready to enter the zone? Start a Deep Practice Session now and let the world fade away.

Melody Master - https://melodymasterapp.vercel.app

Apoorv Karanwal (MelodyMaster Founder)

Apoorv Karanwal - I have build an AI Music Learning Platform from Scratch 🎵

Apoorv Karanwal — Wed, 15 Apr 2026 09:04:36 +0000

Hey Dev.to! 👋 I'm Apoorv Karanwal, a 14-year-old student developer from India. Over the past year, I've been building Melody Master — an AI-powered music learning platform that helps people learn piano, guitar, and music theory with neural AI guidance.

Today I want to share how I built it, the tech stack I used, the challenges I faced, and what I learned along the way.

🎵 What is Melody Master?
Melody Master is a full-stack, AI-powered web application for learning music. It's not just another tutorial app — it features:

🧠 AI Neural Guidance — Personalized learning paths that adapt to each user
🎹 Interactive Piano & Guitar Lessons — With real-time audio feedback using the Web Audio API
🎮 Gamified Learning — XP points, levels, streaks, achievements, and a competitive Music Arena
🏆 Verifiable Certificates — Earn certificates with unique verification codes
🌐 Immersive 3D Interface — A Spline 3D robot on the landing page with GSAP animations
📊 120+ Progressive Levels — From beginner to advanced
📈 Analytics Dashboard — Track your progress and performance over time
👉 Check it out live: https://melodymasterapp.vercel.app

🛠️ The Tech Stack
Here's what I used to build Melody Master:

Layer Technology
Frontend React 18, TypeScript, Vite
Styling Tailwind CSS, shadcn/ui
Animations GSAP (ScrollTrigger, timelines), Framer Motion
3D Spline 3D (for the landing page robot)
Backend Supabase (Auth, PostgreSQL, Row-Level Security)
Audio Web Audio API for real-time instrument analysis
Charts Recharts for analytics/progress visualization
Hosting Vercel
Why This Stack?
I chose React + TypeScript because type safety saved me from so many bugs during development. Vite because it's insanely fast — hot reload in under 100ms. Supabase because it gave me auth, database, and row-level security without needing to build a custom backend.

For the 3D experience, I used Spline because I wanted the landing page to feel premium — not like a typical "student project." The 3D robot that greets users on the homepage was designed to make a statement: this is not just another app.

🏗️ Architecture Overview
Melody Master
├── Landing (3D Spline + GSAP animations)
├── Auth (Email/Password + Guest Mode via Supabase)
├── Dashboard (personalized learning hub)
├── Practice (interactive instrument sessions)
├── Learn (theory courses with gamification)
├── Arena (competitive music challenges)
├── Live (real-time jam sessions)
├── MelodyRings (rhythm game)
├── Progress (analytics + performance tracking)
├── Certificates (verifiable achievement certs)
├── Leaderboard (global rankings)
└── Profile (settings + stats)
Every route is lazy-loaded with React.lazy() and wrapped in Suspense for optimal performance. Protected routes use a custom ProtectedRoute wrapper that checks Supabase auth state.

💡 Biggest Challenges I Faced

WebGL Context Crashes The Spline 3D robot was causing WebGL context crashes on mobile devices. The GPU was running out of memory, and the entire landing page would go blank.

Solution: I implemented explicit WebGL context management with fallback to a Lottie animation when WebGL fails. I also added a deviceMemory check to skip 3D entirely on low-end devices.

Performance Optimization My initial Lighthouse score was 37 on mobile. Painful. 😅

After weeks of optimization, I brought it up to 90+ by:

Code-splitting every route with React.lazy()
Preloading critical assets with
Non-blocking font loading with media="print" + onload
Compressing all images to WebP
Removing unused dependencies

Real-Time Audio Analysis
Getting the Web Audio API to accurately detect which note a user is playing (especially on guitar) was the hardest technical challenge. Different microphones, background noise, overtones — it's a genuinely difficult signal processing problem.
Gamification That Doesn't Feel Cheap
I wanted the XP/leveling system to feel meaningful, not just "+10 XP" spam. Each of the 120+ levels has carefully designed progressive difficulty, and certificates are verifiable with unique codes.

📸 What It Looks Like
The UI design follows a dark mode + glassmorphism aesthetic with amber/gold accents. Every interaction has micro-animations via GSAP. The landing page features a full 3D experience.

👉 See it yourself: https://melodymasterapp.vercel.app

🎯 What I Learned
Ship it, then iterate. I spent too long trying to make everything perfect before launching. Just ship.
Performance is a feature. Users don't care how cool your 3D robot is if the page takes 8 seconds to load.
TypeScript saves lives. I can't imagine building this in plain JavaScript. The type safety caught hundreds of bugs before they reached production.
SEO matters. Even the best app is useless if no one can find it. I learned JSON-LD structured data, Open Graph tags, sitemap optimization, and Google Search Console the hard way.
Age is just a number. If you have a vision and the will to learn, you can build anything.
🙏 Thank You
If you made it this far, thank you for reading! I'm Apoorv Karanwal, the creator of Melody Master. I built this entire platform from scratch as a solo developer.

If you're interested in the project, you can:

🌐 Try it: https://melodymasterapp.vercel.app/
💻 GitHub: https://github.com/updeshkaranwal151-hash/
💬 Questions? Drop a comment below — I'd love to chat!
If you found this interesting, a ❤️ or 🦄 would mean the world to me. Thanks for reading, and keep building! 🚀

— Apoorv Karanwal, Creator of Melody Master