2
Karthik22
79d

Hey guys,
I need a suggestion
I work for a website project
I Still have a confusion about that.
Which one mainly focus on first when I start from the beginning
Either focus on design or focus on functionality

Comments
  • 3
    I build functionality first, then strap the UI on top or in parallel depending on what's being worked on.
  • 0
    @C0D4 thank you for your suggestion
  • 3
    @Karthik22 I've found it easier to have the backend built up to work and then build the frontend towards the end as the stakeholders will want to be able to see that magic button that's going to save them time actually do something when it's pressed, they seem to be more impressed that way 😉
  • 0
    @C0D4 thanks again 🤗
  • 1
    Form follows function, that breeds usable stuff. So first think what exactly the user will be doing with your website, what his intended workflows will be. The architectural design needs to implement them, after all. If the WHAT is not clear, thinking about HOW won't make sense.
  • 1
    @Fast-Nop thanks for you memorable suggestion 🤗
  • 3
    @Fast-Nop true but that's what detailed analysis are for, or mockups from requirements gathering.

    You need to know what before how, but you need to build the inner workings for a form can actually be used.

    That's why I mentioned in parallel, as you can have a shitty form on the page that's "usable" and then comeback later and throw the design concepts on top to make it "pretty" later.
  • 0
    @C0D4 yeah🤗
  • 2
    @C0D4 It's not about making it "pretty", this is not what design is about - because things can be pretty and still unsuited for the task, although users tend to be more forgiving if the unusable stuff looks good.

    My poster child for such a UI is below. No matter how pretty you make that, it's beyond repair because the whole design is feature-centric, not task-oriented.
  • 4
    @Fast-Nop not going to argue with that. But I will raise you my poster child for such feature over task design 😎

    Hopefully @Karthik22 can have the foresight to plan ahead and have the business agree on what they want and how it's going to be presented before he starts building a thousand buttons onto a UI.

    I feel we have had this battle of designs before 🤔
  • 1
    @C0D4 ok yeah thank you 🤗
  • 2
    @C0D4 Yeah that's the typical result of "design by compromise". Two stakeholders can't agree which way to implement, so they end up offering both. Rinse and repeat, and you get such abominations. Also typical for OSS team collaboration with the usual bad OSS UIs.

    Remember these "portal" websites that never could decide what they wanted to be? Remember the totally overloaded Lycos search? And then Google came, it wanted to be a search engine. BAMM.

    The hard part e.g. in a large store is how to organise stuff, i.e. the information architecture (not the SW architecture). On the one hand, the user must reach everything essential, but on the other hand, each option has mental user cost. The hard question is "what is important?", and if everything is important, nothing matters.
  • 1
    Go for functionality first. UI can come in later, and is useless without the back end fully built up. Do keep the UI in mind though, so you don't end up rewriting your entire back end code just to add the UI in.
  • 2
    I usually do it frontend first on personal projects. It helps me figure out what features will be present and how they will work.
  • 0
    @mahir-halani thank you for your suggestion 🤗
  • 0
    @24th-Dragon thank you for your suggestion 🤗
  • 2
    @C0D4 @Fast-Nop Thanks for the pictures.. Seeing this made me feel happy about our unintuitive fucked up GUIs.. o.O
Add Comment