A features page is a list of screens, and a list invites you to treat its order as incidental. It is not. The order is the argument the product makes before anyone reads a word.
When the real screens arrived, the order was the first thing that needed revisiting. It had grown one section at a time, and it looked that way.
Group what belongs together
The exploration screens had drifted apart: the discovery map, then a progress screen, then memories, then nearby places, then an insights screen. Several of those are moments inside one continuous act of walking. A collection screen sitting between them broke the thread.
Reordering so the map and session screens flow together made the page read as a single activity instead of a shuffled deck.
A feature list is a sentence. The order is its grammar.
Delete the section you cannot show
One section described an insights screen that summarised how you explore. The idea is real, but there was no shipped screen behind it, which meant it would have appeared as a labelled preview in the middle of a run of real ones.
We removed it. A promised screen that does not exist yet is better left out than propped up beside the ones that do.
Indexes are not decoration
The sections are numbered, and those numbers are referenced elsewhere on the page. Adding and reordering sections meant the numbers had to move with their content, and the smaller highlights that point at them had to be updated too. A number that points at the wrong section is a small lie.
The strip at the top
The page opens with a horizontal strip of every screen. As sections were added, the thumbnails were sized down so the row still fit without an edge running off the viewport. A preview that scrolls out of view reads as broken; a slightly smaller one does not.
None of this adds or removes a feature. It changes whether the page is honest about the shape of the product, which for a features page is the whole job.