How to Make a Tier List on Your Phone

Most tier list makers assume a mouse. On a phone, precise dragging is slow and the rows are easy to miss. The fix is not a bigger screen; it is a workflow that uses taps and a roster that fits.

Use tap-to-place, not drag

In the maker, tap an item and then tap a tier. The item moves without a drag gesture. This is faster on a phone and works with one hand.

If you prefer dragging, start with the item nearest the row you want; long drags across a scrolling page are where most misplacements happen.

Keep the first board short

Ten to fifteen items is enough for a phone session. A long roster turns into a scrolling exercise and the board stops being fun. Publish the short version, then add a second board for the rest if you still care.

Check the export before posting

Download the PNG and open it at phone size. If the item names are unreadable, remove items or split the board. A dense board that looks fine on a desktop preview can be useless in a group chat.

Share the link, then the image

Send the link first so the reader can see the full roster and vote. Add the PNG only when the destination does not handle links well. The link is also the thing you can update later.

A 10-minute mobile workflow. Pick 12 items, place the obvious S and F picks first, then fill the middle. Check the board at arm's length, export, and share. Do not try to rank a full game roster in one phone session.

When the page fights you. If a drag keeps landing in the wrong row, switch to tap-to-place. If the page is slow, close other tabs before exporting. A smaller roster is the most reliable performance fix.

Choose a phone-friendly roster

A phone session should start with a roster that fits on one or two screens. Twelve to fifteen items is comfortable; twenty is workable; forty is a scrolling project. If the full roster matters, build the top and bottom on the phone and finish the middle on a desktop later.

Short names help. “Mewtwo X” fits; a full character title with a subtitle does not. If the official name is long, use the name people actually search for and add the qualifier in the page notes.

The goal is a finished board, not a complete database. A small board that you actually share is more valuable than a large one you abandon halfway through.

Tap targets and scrolling

Drag-and-drop is the hardest gesture on a phone. A long press can trigger text selection; a short drag can land in the wrong row. Tap-to-place avoids both: tap the item, tap the tier, done.

If you must drag, start with the item nearest the target row and keep the drag short. Scroll first, then drag. Trying to drag while the page is still moving is the most common source of misplacements.

Give yourself room: zoom out slightly if the browser allows it, or use a tablet. A board that is easy to place is more likely to be finished.

Portrait or landscape?

Portrait is better for browsing the roster and tapping items. Landscape is better for seeing all six rows at once. Use portrait for the ranking pass and landscape for the final check if your phone supports rotation.

Do not design the board around landscape if most readers will see it in portrait. The exported image should be readable in the orientation it will be shared in, which is usually portrait.

A simple test: hold the phone at arm's length. If you cannot read the item names without zooming, the board is too dense for the format.

Exporting from a phone

Export after the board is final, not after every change. Repeated exports create duplicate images and make it harder to know which version you shared. If the maker supports a share link, use that for iteration and export only the final board.

Check the PNG in your photos app before posting. Some browsers render a larger canvas than the phone can display; the exported file may be sharper than the preview, or it may crop unexpectedly.

If the export fails, reduce the roster or close other tabs. A smaller board is the most reliable fix on a memory-constrained phone.

Sharing from a phone

Use the native share sheet when it is available. It preserves the image quality better than a screenshot and lets you send the link and the image together. If the share sheet is not available, save the PNG and paste the link separately.

Put the criterion in the message, not only in the image. A phone screenshot often loses the page title; the message is the only context the recipient gets.

For a group chat, send the image first and the link second. The image starts the conversation; the link gives people a way to vote or remix.

A five-minute test routine

Open the maker on the phone you will actually use. Add the roster. Place the obvious S and F items. Fill the middle. Check the board at arm's length. Export. Share to yourself. Open the shared image and the link on the same phone.

If any step takes more than a minute, the board is too large or the workflow is fighting the device. Cut the roster and repeat. The test is not about speed for its own sake; it is about finishing before the phone session becomes frustrating.

Keep the final board and the link together. A board that exists only as a camera-roll image is hard to update and impossible to vote on.

Mobile accessibility

Use the largest text size you can tolerate. Keep the tier letters visible; do not rely on colour alone. If the page supports dark mode, check the board in both themes. A dark-on-dark row is unreadable outdoors, which is exactly where phones are often used.

If you share a PNG, add a short text summary of the top and bottom rows. The image has no alt text, and some readers cannot see it. The summary also helps anyone who is scrolling without loading images.

Accessibility on mobile is mostly about restraint: fewer items, larger text, and one clear action per screen.