.NET Zone is brought to you in partnership with:

Tim Murphy is a Solutions Architect at PSC Group, LLC (www.psclistens.com). He has been an IT Consultant since 1999 specializing in Microsoft technologies and Software Architecture. Tim is a co-founder of the Chicago Information Technology Architects Group as well as a contributing author of the book The Definitive Guide to the Microsoft Enterprise Library and part of the Influceners program on the geekswithblogs.net site. He has also spoken at the nPlus1 ArcSummit in Chicago, the Chicago Code Camp and has appeared on the Thirsty Developer podcast. Tim is a DZone MVB and is not an employee of DZone and has posted 56 posts at DZone. You can read more from them at their website. View Full User Profile

Why You Shouldn’t Build An App In 1 Page

  • submit to reddit

Originally posted on: http://geekswithblogs.net/tmurphy/archive/2013/02/06/why-you-shouldnrsquot-build-an-app-in-1-page.aspx

I have seen a number of people boast that they have a 1 page web application design.  Congratulations.  Now ask yourself why you did that and what the impact that design has.  There are reasons that we modularize applications.  One reason is to give the user logical separation of functionality.  The fact that the application transition from one screen to another give the user a visual queue that something significant has changed and they should take notice. 

From a development standpoint all-in-on design usually bring with them maintainability issues.  Back in the days of ASP 2.0 we used to work with a lot of hidden panels and have all of our code in one file.  Where did that get us?  It brought with us increasing amounts of time to find and fix bugs.  I have worked with solutions where other developers have put dozens of UI elements on a page in the name of getting rid of the evil post back flicker.  The result is a nearly unreadable file especially if there are custom templates for data bound elements.

I understand the attraction of this design from a UI perspective but I believe that only the simplest apps can pull this off effectively.  Be practical instead of trying to be superman just to prove that you know every trick of a technology.  In the end both the user and the developer who comes after you with thank you for an application that is clearly broken into functional area.

Published at DZone with permission of Tim Murphy, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)