Since its rise in popularity over the past couple years, Responsive Web Design (RWD) has helped many web sites deliver content tailored to fit its visitors’ browsers whether they be desktop, tablet or smart phone. Frameworks such as Foundation and Bootstrap have gained fame as great starting points delivering both responsive grid systems and numerous widgets. Both frameworks are offered not only as raw source but also as assets linkable from content delivery networks (CDNs).
In 2007 Apple unveiled the first release of iOS, the mobile operating system deployed on Apple mobile devices. Since its introduction, iOS has implemented a Model-View-Controller (MVC) development design pattern. This design pattern is a common way to organize code so that it is reusable and more easily extensible, and is the default way Xcode (Apple’s IDE for iOS developers) organizes code.
As a soccer referee, I have officiated games played by nine year-olds to “Over 40” and from barely skilled to very skilled. As a Data Analyst I work with both large and small databases. Each has its own different levels of “by the book” rule enforcement, if you will, and I think the analogy between the two provides sound commonsense guidance to data modelers.
On November 18th Apple released the much anticipated Apple Watch software development kit, called WatchKit. Few in the iOS development community knew what to expect or what capabilities would be available. With this information we now know what constraints are imposed by the SDK which leads to a better understanding of some of the problems that need to be solved before enterprises can build and deploy watch apps. These problems are present whether you’re writing an app for internal use or an app for consumer use.
When writing web applications it is always a good idea to minify and combine your scripts and stylesheets to limit the quantity and size of requests to the server from the browser. There are some occasions where you may want to add a particular script file or stylesheet when a given Sitecore rendering is on a page. A good example of why you might want to do this is if you have a client heavy rendering that has a large amount of JSON data that is only used by that rendering. This is probably something you wouldn’t want to include on every page.
When you're building a new house, you find yourself buying a lot of stuff. You find yourself shopping even more. The most critical challenge for marketers is to maximize the likelihood that prospective customers transition from the latter of those two activities to the former; more simply, marketers strive to turn those who shop at their stores (whether brick and mortar or online) into buyers. Two of my recent home building-related shopping experiences highlighted how smart experience management can do just that... kudos to TimberTech/Azek Building Products and Crutchfield.
In a recent Smart Data Collective post, Bernard Marr cites creativity as a top big data skill, but what is creativity? His point is, since big data applications are often off the beaten IT path, big data professionals must solve "problems that companies don’t even know they have – as their insights highlight bottlenecks or inefficiencies in the production, marketing or delivery processes," often with "data which does not fit comfortably into tables and charts, such as human speech and writing."
Yesterday Google was very generous in dropping a little more than 750 icons (available on their GITHUB page) for the world to use in their mobile and web designs. One small problem is that I regularly use Axure as my prototyping tool of choice and not Illustrator or photoshop. As such, we've made available an Axure 7.0 RP library file for you all to use. Note: this library is constructed off the mobile icon set at the 144x144 resolution.
A few things observed while creating this library file:
This post walks through a simple introduction to how to deploy a website to Amazon Web Services from Visual Studio that includes a simple database.
This is the second post in a series intended to give .NET developers a quick start for using AWS. Part 1 of the series showed how to get a basic MVC website from Visual Studio into AWS. In Part 2, we’ll add a database. This post will also explain some of the database options available to you in AWS.