Everyone remembers the Galaxy S III as the flashy plastic Android that sold like crazy; I remember it more as the phone that locked in some of Android’s worst habits while accidentally nailing a bunch of things manufacturers are still failing at.
This wasn’t a one-feature wonder. It was a pile of incremental moves that, combined, pushed Android forward and locked consumers into a new definition of “flagship” – for better and for worse.
Design: Plastic, Huge, and Weirdly Influential
On paper, the Galaxy S III’s hardware styling should’ve been a disaster.
You got a glossy plastic shell with Samsung’s “Hyperglaze” coating, a fake brushed-metal plastic band around the sides, and a battery cover so thin you could flex it with two fingers. Next to HTC’s metal and polycarbonate unibodies and even Motorola’s Kevlar experiments, Samsung looked cheap.
Yet this 136.6 x 70.6 x 8.6 mm slab with a 4.8-inch display basically set the template for what Android phones became: big screens first, materials second. At 133g, it was lighter than it looked, and once people turned it on, the conversation shifted from “this feels cheap” to “okay, that screen is insane.”
Samsung did just enough: the Hyperglaze layer made the back slightly grippy and less fingerprint-disgusting than press shots suggested, and the build was solid even if the vibe wasn’t premium. Call it a B+ in looks, A- in practicality, and a warning shot that consumers would accept plastic if the spec sheet was stacked.
That 4.8″ HD Super AMOLED: Flawed, But Addictive
The real hook was up front: a 4.8-inch 720p Super AMOLED panel.
Resolution and contrast were the selling points. Blacks were effectively excellent, colors were aggressively saturated, and the 720p resolution made icons and text look printed compared to the older WVGA Galaxy S II. Yes, it used a PenTile matrix, but at this pixel density you had to go hunting for issues at eyeball-destroying distances.
Samsung also did what they almost never get credit for: actual tuning options. The display settings let you pick between four modes – Dynamic, Standard, Natural, Movie – so you could go full neon-storefront or dial it down closer to accurate. No other Android screen of that era let users choose their own color personality like that.
Sunlight legibility? This thing topped GSMArena’s charts. Not by brute-force brightness, but by low reflectivity and solid optical work. Outside, in brutal daylight, you could still read the screen without squinting yourself into a headache. Toss in excellent viewing angles, and you had one of the few panels from that time that still feels usable today.
So yes, PenTile purists had a point, but in real-world use this display made more impact on buyers than any camera spec or CPU graph could.
Specs and Battery: Exynos Muscle Meets 2100 mAh Reality
Under the hood, the international I9300’s Exynos 4 quad-core chipset wasn’t just about benchmark bragging rights, but it definitely produced those too.
In multithreaded tests like Linpack and composite suites like Quadrant, the S III either matched or beat rival quad-core Cortex-A9 phones like the Tegra 3-powered HTC One X, despite running at 1.4 GHz vs 1.5 GHz. GPU tests showed the Mali-400MP outpacing both Tegra 3’s GPU and Qualcomm’s Adreno 225 in 3D workloads, even while pushing a 720p screen.
In browser benchmarks like SunSpider and BrowserMark, the S III didn’t just edge out its predecessor; it actually surpassed other ICS phones and even Krait-based devices like the HTC One S. Whoever tuned Samsung’s browser and JS stack knew what they were doing.
The 2100 mAh battery sounds tame now, but back then it was “humongous” and – crucially – removable. GSMArena’s tests put overall endurance at 43 hours, with strong individual call, web, and video numbers. And when that wasn’t enough, you popped off the paper-thin back and swapped in another pack. No begging a wall socket. No glued glass–back anxiety.
Combine a power-efficient AMOLED, an aggressive but smart power-saving toggle in the notification shade, and a physically swappable battery, and you get the part of the S III ecosystem that modern flagships still haven’t fully beaten.
TouchWiz Nature UX: Useful Tricks Drowned in Gimmicks
TouchWiz on the S III was where Samsung went from “Android skin” to “we’re going to rebuild the OS in our image.” That wasn’t entirely a compliment.
You got Android 4.0.4 Ice Cream Sandwich, buried under “TouchWiz Nature UX,” complete with watery lockscreen ripples and bird-chirp ringtones. Underneath the cosmetic noise there were some legitimately smart ideas:
- A heavily customizable lockscreen: four app shortcuts, a news or stock ticker, dual clocks, weather, shortcuts for missed calls and texts, and even a funky twist gesture to jump straight to the camera.
- Smart Stay: the front camera checked if you were looking at the phone and prevented the screen from timing out mid-article or ebook. Creepy eye icon in the status bar or not, it actually worked in normal lighting.
- Direct Call: lift the phone to your ear while viewing a contact or SMS thread and it just starts dialing. Zero taps.
- Smart Alert: pick up the phone and it vibrates if you’ve missed calls or texts since it last sat down.
Individually, these are small wins. Collectively, they’re the kind of context-aware tweaks Google itself would slowly absorb years later.
But Samsung couldn’t stop there. S Voice – their Siri-style assistant – used Vlingo and Wolfram Alpha, just like Apple’s solution, and suffered the same problems: decent command recognition for simple actions, shaky dictation, inconsistent behavior, and enough friction that your fingers were still faster 95% of the time.
Menus everywhere, hidden functions behind the hardware Menu key, long scrolling option lists in core apps – the UX philosophy was “expose everything, then expose five more things.” ICS had just introduced cleaner action bars and on-screen controls; Samsung promptly buried them under old habits.
And yet, power users loved having a full-featured file manager (My Files), a capable Polaris Office editor, and deep widget customization, including resizable widgets and up to seven home screens. This was peak “everything and the kitchen sink” Android.
Media & Camera: Where the S III Actually Earned Its Hype
If you cared about media, the Galaxy S III was a beast.
The music player carried Samsung’s SoundAlive DSP with multiple presets, 7.1-style virtualization, and a genuinely useful “Music square” mood grid that auto-generated playlists based on how “exciting” or “calm/joyful” your tracks were. DLNA support through the player meant your NAS or PC library was as accessible as your local MP3s.
The default video player was even more aggressive:
- Grid view where every visible thumbnail was a live, reduced-framerate preview.
- Full support for WMV, AVI (DivX/XviD), MP4, MKV (H.264) at up to 1080p, with large high-bitrate files handled smoothly.
- Subtitle selection from multiple files, not just strict filename matches.
- Pop-up Play: a floating video window you could drag over other apps while you browsed or checked email.
This wasn’t token codec support. This was “throw your set-top box in a drawer” territory.
The 8 MP rear camera, on paper, didn’t move beyond the Galaxy S II’s resolution, but the execution was better almost across the board.
You got:
- 3264 x 2448 stills with very good detail, low noise, and strong dynamic range.
- Faster F/2.6 lens with a slightly wider field of view.
- Zero shutter lag and a burst mode: 20 full-resolution shots in roughly six seconds.
- Best shot, HDR, face and smile detection, and the ability to shoot 1080p video while grabbing 16:9 stills.
- 1080p30 video at ~17–18 Mbps with solid detail and stereo audio, plus 720p30 at ~12 Mbps.
Benchmarks showed the S III’s camera topping a lot of the 8 MP competition in sharpness and white balance, especially indoors. Video held up too: fine text in test scenes stayed legible, and low-light noise stayed under control.
There were quirks – boosted greens, some oversharpening halos – but this was one of the first Android cameras you could rely on instead of apologizing for.
Connectivity, Sharing, and the Local-Versus-Cloud Problem
On the radio side, the I9300 model checked the basics: quad-band GSM/EDGE and quad-band 3G (though no AWS), with separate LTE variants for specific regions. Wi-Fi a/b/g/n on both 2.4 GHz and 5 GHz, Bluetooth 4.0 HS, NFC, MHL over microUSB with an adapter – nothing exotic, but everything you actually needed.
Samsung’s real obsession here was “sharing,” interpreted as “flinging files around a room,” not “posting them online.”
They split AllShare into:
- AllShare Play: pushing files between your phone, PC, and other devices, plus SugarSync integration.
- AllShare Cast: DLNA-style streaming to TVs and other screens.
Then they layered on proprietary tricks that only really worked between Galaxy S III units:
- S Beam: touch two phones back-to-back, let NFC do the handshake, then Wi-Fi Direct moves photos, videos, or music at a few MB/s.
- Share Shot: every photo you take is auto-pushed to other S III phones in the same Wi-Fi Direct group.
- Buddy Photo Share and Social Tag: face detection wired into your contacts so the phone could suggest sharing pictures or show status updates next to recognized faces.
Technically, a lot of this was impressive. Practically, you needed a small cult of S III owners in the same room and a reason to prefer local transfer over just… uploading to a social app. As cloud services ate photo and music workflows, Samsung’s local-first sharing push looked more and more out of step.
Why the S III Still Matters
Strip away the nostalgia and marketing, and the Galaxy S III was exactly what its more honest reviewers called it: not notable, but a very strong, very calculated refinement.
It locked in ideas that define Android even now:
- Big, bright, high-resolution displays, even if that meant trade-offs like PenTile.
- Performance-first chipsets that dominate benchmarks and real-world tasks.
- Removable batteries and microSD as core pillars of “power user” phones.
- Feature-heavy Android skins that mix legitimately helpful behavior with exhausting gimmicks.
It also codified some bad habits: over-reliance on a legacy Menu button, overloaded UIs, and a taste for proprietary ecosystems that didn’t age well.
But for buyers jumping from older Androids or feature phones, the Galaxy S III was a landslide upgrade: faster, longer-lasting, more capable with media, better at photos, and packed with tricks that, whether you used them or not, made the phone feel alive in a way stock ICS didn’t yet.
You don’t have to love what the S III started to admit what it did: it set the bar so high that even Samsung could afford to “ease off the gas” and still watch everyone else chase it.
Check back soon as this story develops.