10 Principles to Consider When Evolving Your Web Application’s Front End

It’s very easy, espe­cial­ly for an “evolv­ing” web appli­ca­tion, to end up with a user inter­face that is bug­gy and dif­fi­cult to main­tain, par­tic­u­lar­ly if you are incre­men­tal­ly mak­ing changes to an out­dat­ed app, with­out a full redesign. This is a chal­lenge that I’ve faced on many occa­sions, as I have often worked on appli­ca­tions that were built using an out­dat­ed soft­ware par­a­digm or have sub­se­quent­ly failed to keep up with the advances in soft­ware tech­nol­o­gy and method­ol­o­gy. This is not uncom­mon at all, in fact most, if not all, soft­ware engi­neers have had to deal with this on many occa­sions dur­ing their career.

Work­ing through the­se chal­lenges has taught me a great deal about the evo­lu­tion of soft­ware appli­ca­tions. It’s some­thing that I’ve had to learn, while bal­anc­ing the day-to-day demands for the support/upkeep of an exist­ing code­base. This process can teach a devel­op­er a great deal, as they research best prac­tices and gain expe­ri­ence; but most impor­tant­ly, it can teach devel­op­ers what not to do, as you see how the process unfolds over time. Con­tin­ue read­ing “10 Prin­ci­ples to Con­sid­er When Evolv­ing Your Web Application’s Front End”