How an app gets recommended

The recommended page lists 32 apps. The standard is not complicated, but it is not a scorecard either: compatibility is the prerequisite, and everything after it is a judgement call.

Prerequisite: it ships, and it is genuinely adapted

The app has to be on the store, and its status in Mainland China has to be adapted — the main screens, the switch between folded and unfolded, and the core actions have all been looked at on the Duo. Anything marked partially adapted, in progress or not checked stays out, however much I like it; the build-time validator enforces this too.

The rest is a composite

• does the interaction match user habits, with muscle memory still where it was after unfolding;
• does the design hold up, since a large screen magnifies the details;
• does it flow, instead of one extra wait at every step;
• is there a good idea — the hardest to quantify, and often what decides it;
• does it actually use the extra space, rather than the phone layout scaled up.

No weights, no total score. A great idea with plain design can get in; something competent that gives no reason to open it twice will not.

Where the evidence comes from

Official release notes, public posts from developers or users on social media, hands-on use, visitor feedback. These are leads, not conclusions — if it says "big screen support", it still has to be seen on the device.

Scale is not a gate

Most apps on the list are not on any chart. A few have very few downloads, or are only available in the China store. A young app with a clear idea and real polish is more worth recommending than a heavily downloaded one that has simply been scaled up. Ratings are reference only.

The list changes

A new release does not inherit an old conclusion. If the unfolded experience breaks, the status is rolled back and the app leaves the recommended page — the directory record and its history stay.