Census looks like the Web, but feels like Windows.
Unlike other Web-based issue tracking systems, Census is not a static HTML page that is constantly refreshed everytime the user views another record, submits a new issue, or performs some other action such as generating a report or attaching a file.
Most Web-based issue tracking systems allow the user to view an HTML document and enter data into a form, but any further processing requires a round trip between the Web server and the user's browser. The HTML form must be submitted to the server, another HTML page constructed, and the page sent back to the browser and rendered. This constant reloading of pages (and the blank browser windows that appears while a new page is rendered) is known as the hard refresh problem.
Constant hard refreshes make the application difficult to work with, because the application doesn't behave the way users expect an application to behave—like a Windows application.
Census works the way users expect. For example, when a user submits a new issue or browses records, there is no refresh of the entire browser window. Census dynamically writes to and queries the back-end database and populates the interface—with no hard refresh.
And like a Windows application, Census uses pop-up dialogs for things like generating reports, setting options, or attaching files. Other Web applications simply load another HTML page, replacing the main application page and confusing users... Where am I now? How do I get back?
Conclusion? Census is easier to use, because it works the way users expect. Like a Windows application. So Census is easier to adopt into your development process. There's less learning curve, and less resistance to change.