You think that's air you're breathing?
It's difficult to remember what life was like before HTTP arrived. Sure, there were advanced computer networks, email, bulletin boards, and more before then. But the advent of HTTP, the web browser, and the growth of ubiquitous internet access sparked a permanent change in the way individuals and organizations share and engage with one another. Over the course of just a couple of decades the web has gone from being a mere novelty to a nearly necessary aspect of life for both families and businesses alike, and during that same time period the explosion of related technologies has been unprecedented. Here at Moxie Group, we live and breathe in this sea of technology, and love to bring that experience to bear on the interesting and complex problems that our clients engage us in.
Ignoring users of mobile phones and tablets these days is more than just naive, it's quite foolish. The statistics are proving out that nearly 60% of users interacting with individual web sites these days are using both mobile devices and desktop PCs, and another 15% are using mobile devices exclusively. Tailoring a site to best serve different device types though is not a one-size-fits-all question. For some sites, taking a responsive approach is the most logical solution, but for many sites the responsive approach brings with it both excessive page weight and functional limitations that can kill the mobile experience. For sites that decide a more mobile tailored solution is worth the investment, then several key questions need to be answered such as how to best detect the device type (WURFL, DeviceAtlas, etc.) and how to dynamically react to the incoming URL requests (single canonical URL for all devices types, separate mobile domain, unique page paths, etc.) We're very familiar with these challenges, and have a successful track record implementing multiple kinds of mobile site solutions.
One of the taken-for-granted things that HTTP also helped bring about was in providing a universal and simple standard for computers to interact with each other. Even with HTTP as the protocol backbone though, choosing the right SOA and integration technique can be tricky. We've learned how to help choose and implement the right strategy for the task at hand. When we're working on a service whose data can be nicely isolated from the rest of the enterprise, you'll find us recommending IaaS models like Google App Engine or AWS BeanStalk. If the service needs to be accessible directly to an end user in a web browser, we'll bring in JSONP techniques. When the service is going to be exposed to the world to use, we'll setup the appropriate request signing OAuth techniques to guarantee the identity of the person or system attempting to access the service. The list of strategies like this goes on and on, and we'd love a chance to help you enable the right kinds of services for your business challenges.