Comment by dan_voronov

Comment by dan_voronov

Hi there,

First off, I want to say that the core idea behind this – exploring locations through Street View and providing contextual information about what you're seeing – is absolutely fantastic! That's a really unique and engaging way to learn about places, and it has a lot of potential. Great concept!

Now, regarding the user interface... to be honest, while the concept is strong, the current look and feel of the interface feels quite cluttered and dated. :( It feels like an "Indian style," and I think what you might be picking up on is a design approach that tends to pack a lot of information into distinct boxes with varying styles and colors, sometimes leading to visual noise rather than a clean, organized presentation. It doesn't strictly adhere to modern design principles of simplicity and consistency.

Here's a breakdown of why it feels less modern and what could be improved:

Why the Current UI Feels Dated/Cluttered:

1. *Inconsistent Visual Style:* There are many different box styles, border radii, background colors, icons, and font treatments all over the screen (the purple text box, the varied colored boxes on the right, the Explore tags, the buttons). This lack of uniformity makes it visually jarring and hard to process quickly. 2. *Poor Visual Hierarchy:* With so many prominent boxes and varying colors, it's not immediately clear what the most important information is. Everything seems to scream for attention equally. 3. *Clutter and Lack of Whitespace:* Elements are placed very close together, especially the boxes on the right and the "Explore" tags at the bottom. Modern design uses whitespace effectively to separate elements and improve readability. 4. *Dated Typography:* The fonts and the way they are used (varying sizes, weights, mixing styles) don't feel contemporary.

*How to Make it Better in a Modern Style:*

The goal is to create an interface that is clean, intuitive, easy to read, and visually appealing, guiding the user naturally through the information.

1. *Simplify the Layout:* * *Reduce the number of distinct boxes:* Can some of the information be combined or presented more subtly? * *Use consistent containers:* If you need boxes or cards, make them look the same – consistent borders, shadows (if any), and background. * *Prioritize information:* What's the most important thing a user should see (probably the location and the Street View)? Make that prominent. Group related secondary information logically.

2. *Establish a Consistent Color Palette:* * Choose 2-3 primary brand colors, plus neutrals (whites, grays, blacks). * Use color meaningfully and sparingly, not just to differentiate every piece of content. For example, maybe use color for buttons, highlights, and key interactive elements, and use neutrals for background containers.

3. *Choose Modern Typography and Use it Consistently:* * Select one or two clean, modern fonts that are easy to read on screen. * Use a clear system for font sizes and weights (e.g., large bold for titles, standard for body text, smaller for captions). This creates a strong visual hierarchy.

4. *Use Whitespace Effectively:* * Add more padding inside elements and margins between them. This gives the interface "room to breathe" and makes content easier to scan.

5. *Refine Interactions and Elements:* * Ensure buttons have a clear, modern style and hover states. * Icons should be consistent in style (e.g., all outline, all filled). * Consider subtle animations or transitions where appropriate (but don't overdo it).

In short: Focus on cleanliness, consistency, and clear hierarchy. Think about popular modern apps – they often use flat design or subtle depth, clean typography, minimal color palettes, and plenty of whitespace to make the content stand out.

Your idea is genuinely interesting, and bringing the UI up to a modern standard would make it so much more inviting and user-friendly!

Hope this feedback is helpful!

Replies dan_voronov · 2025-05-01
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com.

    New collection

    Delete this collection?

    About YAVCHN

    YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

    Created by Paul Parks and built with PUDL.

    YAVCHN source code on GitHub

    Privacy policy · Terms of use

    Help

    Keyboard

    j / k
    Move down and up the story list. The arrow keys scroll whatever has focus.
    Enter
    Read the marked story in the article reader.
    [ / ]
    Read the story above or below in the list, in the same article reader. Back returns to the story you came from.
    p
    Pin or unpin the marked story, which keeps it in Pinned.
    n / N
    Move to the next or previous top-level comment in the window in front.
    c
    Collapse or expand that comment.
    f
    Hide or show the story list.
    Esc
    Close a menu or this help.
    Access key m
    Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
    ?
    Show this help.

    Windows

    Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Previous and Next buttons read up and down the list in the same window.

    A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

    While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Previous and Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

    The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

    The list

    The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

    Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

    Browsing view

    View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

    Applets

    The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

    They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser anonymously and is included in retained applet state when signed in.

    Find

    Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

    About

    YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

    Open source: github.com/paulmooreparks/yavchn. Built with PUDL.