Skip to content
0:00 / 0:00

#apisecurity#apikeys#flutter

How We Exposed API Keys to 500,000 Users

Tyler Codes

4K subscribers • 8 videos on Hallway

YouTube
  • Recommended by 1 person: 1 in engineering communities.

Beginner. No background in the topic needed.

533 views2 years ago1 recommendation

SecurityWeb developmentWeb and application securityAPI design

Tyler Codes explains the security risks of storing API keys in client-side applications and how to properly secure them.

Get ready for an electrifying journey into the world of API key security! In this quick video, we tackle the timeless dilemma: how can you keep your API keys hidden from prying eyes? Whether you're building an app or a website, the truth is clear—if your front-end can access those keys, so can your visitors (if they know where to search!). So, how do we safeguard against this? Join me as I explore some thrilling options that you can implement with any tech stack! If you enjoy this content, let me know, and I might just whip up a coding video related to it in the future!

Why it's here

1 person recommends this

What people say. Engineers point to this video to explain why sensitive API keys should never be stored in client-side code.

u/tylersaveryin r/FlutterDev • Recommends

On “I built an AI agent inside a Flutter app — No backend, just GPT-4 + clean architecture”

No. Anything your client has your user has. This is true for react native, flutter, js, svelte, swift, java…, anything client side. No way around it.

u/tylersaveryin r/FlutterDev • Recommends

On “Securing Sensitive Data & Environment Specific Settings in Flutter Using .env Files”

Nothing client side is “secure”. link to this video