<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Nick · FoldKit</title>
    <description>The latest articles on DEV Community by Nick · FoldKit (@foldkitme).</description>
    <link>https://dev.to/foldkitme</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4251030%2Fb98993d4-6325-45c0-af55-1eb6d3d62f7d.png</url>
      <title>DEV Community: Nick · FoldKit</title>
      <link>https://dev.to/foldkitme</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/foldkitme"/>
    <language>en</language>
    <item>
      <title>A Store Listing Is Not a Foldable Compatibility Test</title>
      <dc:creator>Nick · FoldKit</dc:creator>
      <pubDate>Wed, 18 Nov 2026 07:39:02 +0000</pubDate>
      <link>https://dev.to/foldkitme/a-store-listing-is-not-a-foldable-compatibility-test-77b</link>
      <guid>https://dev.to/foldkitme/a-store-listing-is-not-a-foldable-compatibility-test-77b</guid>
      <description>&lt;p&gt;When an app listing says “supports foldables,” what does that actually prove?&lt;/p&gt;

&lt;p&gt;It might mean the app fills a larger window. It might mean one developer tested one device. It might describe a two-pane layout, a cover-screen feature, or only a release-note keyword. None of those automatically tells us what happens when the device is folded, unfolded or half-open.&lt;/p&gt;

&lt;p&gt;While building &lt;a href="https://foldkit.me" rel="noopener noreferrer"&gt;FoldKit&lt;/a&gt;, I ended up treating foldable compatibility as an evidence problem rather than a yes-or-no field.&lt;/p&gt;

&lt;h2&gt;
  
  
  Three states, not one badge
&lt;/h2&gt;

&lt;p&gt;A useful source may cover one or more states:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Folded:&lt;/strong&gt; cover-screen or compact-window behavior&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Unfolded:&lt;/strong&gt; expanded layouts, multiple panes and larger-window behavior&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Half-open:&lt;/strong&gt; tabletop, book, hover or hinge-aware arrangements&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;An app can behave well in one state and still have unknown behavior in the others.&lt;/p&gt;

&lt;h2&gt;
  
  
  Four different kinds of information
&lt;/h2&gt;

&lt;p&gt;I also needed to keep these separate:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Listing metadata&lt;/strong&gt; — identity, version and storefront information&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Developer claims&lt;/strong&gt; — features described by the maker&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;User reports&lt;/strong&gt; — individual experiences with device and version context&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Scoped posture evidence&lt;/strong&gt; — a source that explicitly describes a result for a particular state&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Collapsing those into one score creates false precision. If no source explicitly covers a posture, FoldKit leaves it &lt;code&gt;untested&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Context changes the meaning
&lt;/h2&gt;

&lt;p&gt;A user report without a device, OS version or app version may still be useful, but it cannot establish a platform-wide defect. A reply that reports a fix matters. Conflicting results matter. A system setting that resolves the issue changes how the report should be summarized.&lt;/p&gt;

&lt;p&gt;The goal is not to discard imperfect evidence. It is to keep its scope attached.&lt;/p&gt;

&lt;h2&gt;
  
  
  Human review around agent collection
&lt;/h2&gt;

&lt;p&gt;Agents help discover and summarize candidate sources, but every new Kit entry starts as a draft. The intake pipeline checks structure, duplicates, source availability and repository metadata. Production excludes drafts until a human review approves them.&lt;/p&gt;

&lt;p&gt;The same boundary applies to the product itself: FoldKit does not install or run the apps and tools it indexes, and it does not present author claims as FoldKit testing.&lt;/p&gt;

&lt;p&gt;The first public release contains 45 guides and tools, 30 app profiles and 19 source-linked user reports. You can explore the evidence model at &lt;a href="https://foldkit.me" rel="noopener noreferrer"&gt;foldkit.me&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;I would be interested in how other developers model compatibility claims. What would you require before changing a posture from “untested” to a reported result?&lt;/p&gt;

</description>
      <category>mobile</category>
      <category>webdev</category>
      <category>ios</category>
    </item>
  </channel>
</rss>
