Performance problems plague social casino mini-games. Three freelancers who deal with this daily explain why.

Q: What's the most common performance issue?

"Particle effects," Nina says flatly. She's optimized games for five different casino platforms. "Designers want explosions of coins, cascading gems, sparkle trails on everything. Each particle costs resources. I inherited a slot game running at 18fps on iPhone 11. It had 400 particles per spin. Cut it to 80, got it back to 58fps. Looked almost identical."

James points to another culprit. "Memory leaks from improper cleanup. Developer spins up a bonus round, doesn't dispose of textures properly when it ends, does this 50 times, game crashes. I spend probably 30% of my time hunting down unreleased resources."

Q: What about asset sizes?

"Everyone wants 4K graphics now," Maria explains. "I'm building games that need to load over cellular networks in 3-4 seconds. A client sent me 8MB worth of PNG files for a single mini-game. That's insane. I spent two days converting everything to compressed texture atlases and got it down to 1.2MB. Quality difference? Negligible on a phone screen."

Q: Do clients understand these constraints?

James laughs. "Not initially. They test on WiFi using flagship phones. I now send them Android mid-range devices to review builds. Changes the conversation quickly when their game stutters on hardware that 60% of their users have."

Q: What's your testing process?

"Profile on the worst device you can find," Nina says. "If it runs smoothly on a three-year-old budget Android, you're good. I keep an old Moto G7 just for testing. If frame rate holds there, I ship."