BHW Group Blog

Mobile is no longer the future. Mobile is here and it has arrived with a ring. Mobile is so here, in fact, that even the most entrenched old-age companies are clamoring for Android and iPhone apps. And that is fantastic! But, it is very important that companies consider all of their options before investing a moderate amount of effort and capital into a native mobile app.

This is the second part in a two-part series on mobile engagement. The first part can be found here. This second article will expand on the first by describing how you can utilize social features to create mobile engagement.

Businesses who have developed, promoted, or designed a mobile app know just how difficult it is to get downloads. Some companies have spent countless hours and thousands of dollars for a small number of installs in hopes of their app “going viral” and becoming popular.

One of our clients provides an information-rich website for their customers, containing business data from multiple sources.  Like all companies, our client wants to make their content easily accessible for their website users; however, without a unified search for business data strategy our client could only provide search for a small portion of their data.

Geofencing is a popular option for modern mobile applications.  The concept of a geofence is simple; draw a virtual boundary around a point on a map, like a fence around a yard, which can then monitor when a mobile device crosses the boundary.

In our last article we described the Service and Presentation layer choices in our ASP.Net MVC application template.  In our fourth and final article on ASP.Net MVC Principles, we discuss BHW's Visual Studio project template and how it helps us quickly start projects with a great foundation.  We also discuss when to apply the template and some of the value the template brings to our projects.

Often when beginning a new project, a developer must choose between starting a new project from scratch or copying an existing project. Neither of these options is ideal.

In parts one and two of our four part series on ASP.Net MVC Principles we discussed the object oriented design concepts behind our application template.  We also discussed Dependency Injection and how our application template is divided into three layers, Data Access Layer, Services Layer, and Presentation Layer. We described the Data Access Layer in the last article.  In this article we will describe our services and presentation layers.