Steps to upgrade whole UI or Revamp whole UI

Question

0.00/5 (No votes)

See more:

I have an old web application (in asp.net) of almost 100 pages which is compatible to IE 6 so I want to revamp it's UI because it gives browser compatibility issues and doesn't look cool either. Now I am confused what things should I use and in what order to save time and avoid any error/flaw. Here are some questions:

1) I am thinking of using HTML 5 and make it responsive

2) I also heard of Angular JS, should I use it, if yes then where ?In my project java script and jquery both are used.

3) Should I use MVC ? But I am afraid it will require change of code which will lead to wastage of time. But it will make website faster.

Posted 2-Nov-14 22:27pm

Muhammad Ashhar Hasan

Add a Solution

Comments

Kornfeld Eliyahu Peter 3-Nov-14 4:54am

As I see your question, you do not look for revamp the UI but rewrite the application...Why? Is the old app stopped serving you?

Muhammad Ashhar Hasan 3-Nov-14 11:54am

Thanks for replying, No the old app is working fine but it's UI is not beautiful. I just want to revamp UI.

Kornfeld Eliyahu Peter 3-Nov-14 12:49pm

In that case - your first step is to separate the old application's BL from its UI! Than you can attach to that BL an other UI...

Adrian Fatol 3-Nov-14 6:06am

You should ask yourself how much do you afford to invest in this and who will do the refactoring, what's the experience of the people involved in this.

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)