Compare properties on your phone without losing the important details
Build a property comparison for a narrow screen that keeps listing details, sources and unanswered questions easy to distinguish.
Published:
This article was prepared automatically using AI and the cited sources.
Start with fields that serve your decision
Before placing listings in a table, write down what you need to compare on your phone. Location, the advertised price and a property feature that matters to you are possible starting points. Keep the compact view focused on fields that help distinguish the properties, and save other details separately. This is a suggested way to organize your review, not a rule that makes the decision for you: the useful fields depend on your search.
Give each field a consistent name and decide what its value represents. For example, do not label one entry as a locality and another as an address if you intend both to describe the same thing. The tabular data model allows column metadata to describe titles, data types and the meaning of missing values. Note those definitions in your working file before filling it in, so you do not have to guess what a cell means later.
- Write down the purpose of the comparison.
- Select the most useful fields for the compact view.
- Use a consistent name for each field.
Choose a layout that keeps each property identifiable
On a narrow screen, try a layout in which each property has a clear heading followed by the same fields in the same order. If you use a conventional table that requires sideways scrolling, check whether you still know which property a cell belongs to when you return to it. Reduce the fields shown at once if necessary, but retain explanations that affect what a value means. Keep the fuller record available for a closer review.
Before sharing the comparison, open it on a phone and answer a practical question: which property am I reading, and where is the equivalent field for the other property? If you keep returning to the headings, adjust the layout or divide the comparison into smaller parts. Accessible table guidance emphasizes the relationship between header and data cells; visual alignment alone does not establish that relationship for everyone reading the table.
- Give every property a clear heading.
- Open the comparison on a phone and scroll through it.
- Show fewer fields at once if you lose context.
Hypothetical example: a compact comparison template
This hypothetical example does not describe actual listings. The property names are placeholders, and the cells contain prompts rather than observations. Choose listings relevant to your search, replace the placeholder names and enter only information you can find in each corresponding source. Read each row together with its field label: that helps you keep the location separate from the listing source even when you move across the table on a small screen.
For the price row, copy the amount and its denomination as presented in the listing, if supplied; do not treat it as a final transaction amount. If a feature is not stated, write that explicitly instead of leaving a blank cell. Save a link to each listing beside its source in your working file. The template helps expose differences, but return to the sources to check the entries before using them to make a decision.
- Replace the placeholder property names with your own.
- Save each listing link alongside the relevant property.
- Mark unstated features as not stated.
Scroll the table sideways to see every column.
| Field | Hypothetical property A | Hypothetical property B |
|---|---|---|
| Source | Enter the source for this listing | Enter the source for this listing |
| Location | Copy the stated location or mark it as not stated | Copy the stated location or mark it as not stated |
| Advertised price | Copy the stated price or mark it as not stated | Copy the stated price or mark it as not stated |
| Feature important to you | Enter your chosen feature and check its value | Enter the same feature and check its value |
Separate an unknown value from an answer
Mark missing information so it cannot be mistaken for a negative answer. If a listing does not mention a feature important to you, write “not stated” rather than “no”. If you have not yet checked the source, use a separate label such as “not checked”. The tabular data model allows the interpretation of missing values to be described; you can add a short explanation of your own labels alongside the comparison.
Keep the source associated with each property and note what needs clarification. For example, if the source uses an unclear term for a feature, do not convert it into a more precise value based on a hunch. Write down the question and return to the original description. Clear sourcing helps a reader assess information, so when you share the table, include enough context for the recipient to find where each entry came from.
- Use different labels for unstated and unchecked information.
- Record a specific question beside an unclear field.
- Include the source for each property.
Make the comparison readable beyond the visual layout
If you are putting the comparison on a webpage, ensure its table headings are identified as headings and associated with the appropriate data cells. A table caption should identify its subject, and more complicated heading relationships may need explicit associations. Ask the person responsible for the page implementation to check these relationships. The goal is for someone using assistive technology to receive the context of a value, not just the value itself.
If you share an image of the table, do not make the image the only source of the comparison. A short description can identify a complex image, but its essential information also needs a detailed text equivalent. Place the data table or structured text nearby, including the properties, field labels and unknown values. The recipient can then review the information without having to rely on the visual image alone.
- Give the table a caption that identifies its subject.
- Check the relationships between headings and data cells.
- Provide a text equivalent alongside an image of the table.
Return to the sources before relying on the table
Before making a decision from a saved comparison, reopen the source for each property and check the fields that matter most to you. If information has changed, update the value and its accompanying note rather than merely changing a review date. If you cannot reach a source or confirm a value, mark that limitation clearly. An older entry should not appear to have been freshly checked when the underlying information remains unverified.
Finally, review the table on your phone as you would actually use it. Find a property heading, compare the same field with another property and open the recorded source. If any step is confusing, adjust the heading, field order or explanatory note. Useful content should serve its intended reader, so keep enough context for your own later review and for anyone with whom you share the comparison.
- Recheck important fields in their sources before use.
- Clearly mark values you cannot confirm.
- Test the path from a cell to its source on your phone.