How to not get hacked when vibe coding an app

@swerikcodes

84.7K followers · usually 16.3K views a post

Views

170.9K

Likes

12.8K

Comments

105

Shares

1.3K

Selling · SaaS › Other SaaS

swerikcodes https://linktr.ee/swerikcodes ↗

Why it worked

The video provides practical, actionable advice on app security and scalability, addressing common pain points for developers. By focusing on essential steps like rate limiting, secure authentication, and efficient task management, it offers value to viewers looking to build robust applications.

Summary

The video explains how to build a secure and robust application by focusing on key steps like rate limiting, secure authentication, and proper data management. It emphasizes the importance of testing and scaling the application to prevent it from breaking under user load.

Structure

1Build the first version of the app
2Implement security measures like rate limiting and secure authentication
3Securely store API keys and secrets
4Focus on scaling with caching and asynchronous jobs
5Load test before launching

Product placement

The video mentions and implicitly promotes the creator's own services or platform, 'swerikcodes', linked in their bio, as the subject of the advice on building secure apps.

Original caption

How to build an app that ACTUALLY works when users start using it. #app #vibecoding #coding #learntocode #softwareengineer

More from @swerikcodes

Their other posts in the index, biggest breakout first.

On-screen text

How to not get hacked when vibe coding an app okay so now the first version that's step if people actually start using it you need to make sure it does not break or this this means stuff like adding this means stuff like adding rate limits so people cannot sign sign up or AI sign up or AI endpoints etc using a real using a real authentication like I mentioned like I mentioned with clerk or like I mentioned with clerk or Firebase Row-Level Security lock down your database lock down your database with row so users can only see so users can only see their own data Environment Files never expose or any secrets or any secrets in your front end securely store them side in environment then then as you scale then as you scale focus on then as you scale focus on the basics cash repeated cash repeated requests cash repeated requests with Redis Caching Redis cash repeated requests with Redis Async Jobs move heavy tasks move heavy tasks like email sending AI PDF PDF parsing PDF parsing into PDF parsing into asynchronous Load Testing and finally and finally load test and finally load test before launching shipping the app is making apart apart when users actually is is the more important

Transcript

Okay, so now you've built the first version of the app. That's step one. If people actually start using it, you need to make sure it does not break or get abused. This means stuff like adding rate limits. So people cannot spam your login, sign up or AI, M points, etc. Using a real authentication provider like I mentioned with click or firebase, lock down your database with low level security so users can only see their own data. Never expose your API keys or any secrets in your front end, securely store them server side and environment files. Then as you scale focus on the basics. Cash repeated requests with red is move heavy tasks like email sending, AI requests, PDF parsing into a synchronous jobs. And finally load test before launching. Shipping the app is one thing, making sure it doesn't fall apart when users actually use it is the more important part.