BHW Group Blog

In our first article on Single Page Applications we presented a REST JSON API running on Clojure with CouchDB. In this article we build on the previous article by introducing our client-side application.

MongoDB is now the fifth most commonly used database in the world. Frequently clients approach MongoDB and NoSQL from an all or nothing position. They chose to completely adopt NoSQL or stay entirely with an RDBMS. Imagine a scenario where your company or your client’s company is heavily invested in the "Microsoft Stack" and has a mature on-line software product that has grown over many years.

In my previous 2 articles, I provided an overview of both mobile websites and native mobile apps, as well as discussing the benefits and drawbacks of each. These are the two main pieces of a mobile strategy and understanding them individually is crucial to crafting an effective mobile app development plan. But, knowing how and when to combine these technologies is what sets the top mobile players apart.

When starting a Business Intelligence (BI) project the first challenge technical teams face is often the most difficult, "how do we shape our data to meet our needs?". Why is this difficult?

Welcome back! In this series, we are exploring how to design HTML forms with AngularJS, with the best user experience in mind. If you missed part 1, you can find that here. In part 2, we will take a deeper look at a couple more complicated validation scenarios.

In my previous article, I discussed the benefits and shortfalls of creating a native mobile application. This installment will cover the pros and cons of making a mobile website. A mobile website differs from a native mobile application in that it is not installed directly to a phone or tablet, but is viewed in a mobile web browser. These websites also differ from websites seen when browsing on a computer, in that they are visually redesigned or reorganized to better fit a smaller screen. Given that users spend more time browsing on mobile devices than traditional computers, we need to be creating websites with this in mind.

One of the greatest benefits we have seen when creating single page applications with AngularJS is how much faster and easier it is to design forms, even those with complex validation.

The single page application (SPA) approach has revolutionized our approach to development.  Fantastic client-side Javascript frameworks like AngularJS, Knockout, and React have made the transition easy and fun.  As we’ve written more and more SPAs an unexpected trend has emerged.  We’ve moved to a thin server architecture for delivering our back-end solutions on SPA projects.  We increasingly think of the application tier as plumbing, only responsible for data storage with a little authentication, authorization, and validation thrown in.