Design or develop first?

Discussion in 'Programming' started by Wolf2, Jul 10, 2008.

Remove these ads by signing in
Remove these ads by signing in
Thread Status:
Not open for further replies.
  1. Wolf2 New Member

    Member Since:
    May 28, 2008
    Message Count:
    37
    Likes Received:
    0
    I was wondering if I should go about designing my site first before implementing any back end capabilities.
    I like to keep things organized and plan ahead so it would seem to make sense to create the static site first but i am somewhat unsure if I were to design first and end up redesigning to fit everything I plan on adding later, in terms of dynamic content.
    Any tips on this would be great thanks.
  2. midlandi Can you smell that?

    Member Since:
    Jan 22, 2007
    Message Count:
    4,758
    Likes Received:
    33
    Location:
    Uk
    Depends on the method of your design I would say, mostly you should be able to plan that all you want to add can be integrated into the design you have.
  3. iPhone Fan New Member

    Member Since:
    Jul 18, 2009
    Message Count:
    17
    Likes Received:
    1
    You should have an idia of your site in your mind. Then you choose how to start to realize you idea.
    1 people like this.
  4. SeoKungFu Active Member

    Member Since:
    Jul 10, 2009
    Message Count:
    597
    Likes Received:
    76
    Occupation:
    SEO Ninja
    Actually and ideally, the process should be :
    - gather requirements and analyze them
    - plan / schedule your timing estimates
    - develop
    - test / bugfix
    - implement in production
    This is not my own invention, it's briefly how normally, and professionally, it goes.
    And well, design and development come after the gathering of requirements, of course.
    It's much more efficient to do it that way, rather than changing the course of action somewhere on the run...
    2 people like this.
  5. a4hire New Member

    Member Since:
    May 1, 2009
    Message Count:
    109
    Likes Received:
    10
    Occupation:
    technician
    Location:
    Arizona
    I would agree that you should have some idea of what functions will be available at the site first. This will help to guide your design process.
  6. Lolito New Member

    Member Since:
    Jul 22, 2009
    Message Count:
    31
    Likes Received:
    0

    I agree, this is called System Development Life Cycle. We assume you gathered all information and you analyze them. Of course we should design first before developing a prototype or design a database first before developing a prototype. In my own term I will call it "Blue Print" because we base the design before develop a system or prototype.
  7. joomladev New Member

    Member Since:
    Aug 9, 2009
    Message Count:
    20
    Likes Received:
    1
    Hi,

    Actually you should go for design first and then mock up which will give you a complete idea of how your site will look a like and than you can start from backend as this is normal procedure we follow.

    Thanks
  8. goldyweb New Member

    Member Since:
    May 6, 2009
    Message Count:
    530
    Likes Received:
    9
    Things go side by side... Put a first plan on.. then go on developing it..
Thread Status:
Not open for further replies.

Share This Page