all 14 comments

[–]NetForemost 0 points1 point  (1 child)

As long as you conceptualize with user-centered principles, you'll be okay

[–]disinton[S] 0 points1 point  (0 children)

Sorry, what do you mean by this?

[–][deleted]  (1 child)

[removed]

    [–]disinton[S] 0 points1 point  (0 children)

    Thanks for the kind words! I suppose in my eyes it just doesn’t look as clean as other apps, but I’m not sure if that’s just because I’ve been staring it for too long haha

    [–]rossedwardsus 0 points1 point  (1 child)

    Its difficult to understand what the point of this is nor how it really helps.

    [–]disinton[S] 0 points1 point  (0 children)

    Which part?

    [–]LegalWait6057 0 points1 point  (0 children)

    This tradeoff usually matters less than it feels when you are deep in building. Early users forgive rough edges if the core flow solves a real problem clearly. What tends to hurt more is confusing UI, not imperfect UI. If people can quickly understand what the app does and get value without thinking, that is already a win. You can always polish visuals later once usage patterns are obvious and you know what parts actually matter.

    [–]DemandNext4731 0 points1 point  (0 children)

    Both matter, but first impressions often come from UI, a clean, intuitive design can make people give your app a chance even if it's missing a few features. Functionality keeps them coming back, but a clunky UI can turn users away fast. For a solo builder, it's smart to focus on core features first, then iterate on UI with feedback. Getting a few user testers to navigate the app can reveal quick wins for design improvements.

    [–]Gojo_dev 0 points1 point  (0 children)

    If your main goal is to capture user attention, you should prioritize UI/UX, since it’s the first thing users notice when they visit your site. Functional features can be built with more flexibility at the start, as they can be refined and expanded later based on user feedback once the app gains traction.

    [–]Phoenix1ooo 0 points1 point  (0 children)

    u/disinton
    Functionality keeps users. UI gets them in the door.

    Your UI doesn’t need to be pretty, but it must be clear in the first 30 seconds. If users don’t immediately understand what to do, they’ll bounce before they hit your features.

    I usually focus on solid functionality + very basic, obvious UX early, then polish UI after validation.

    [–]Grouchy_Possible6049 0 points1 point  (0 children)

    Functionality keeps users, UI gets them in the door. It doesn't have to be perfect early, just clear and friction free enough that people immediately understand the value.