Make It Happen
My Tipsheets are chock full of ideas. They are all aimed at translating knowledge into a quick, action-oriented 60-second nugget.

First Name:
Last Name:
Tipsheet Archive
Randall's Resources
Whenever I speak or write, I often prepare extra "bonus" materials.
Enter the Resource Code to access this special content:
Resource Code:
Try this example Resource Code: eventplanning

Responsive design

If you use the web on a mobile device, do you ever get frustrated by a site that forces you to pinch-and-zoom to read the content?  Or a mobile website that seems to hide what you think is key information – like the street address and phone number?

If your organization is considering a new website, you likely already know that the site must be mobile-friendly; in developer-speak, this means that the site must be developed using responsive design: the site must be usable no matter what device is knocking at the web server’s door.

Unfortunately, not all responsive design is the same.

There are three major ways that responsive design can be implemented, with vastly different impacts on the organization – and the user.  Which one is used is a function of your budget… and the developer’s experience.

1) Plug-in approach.  There are plug-ins for many web content management systems that can “automatically convert” the site into a responsive site.  Usually, this means that the menu would no longer appear at the top of the screen, but instead be collapsed into a mobile-style hamburger menu in the top left corner.  All of the remaining content would be stacked, accessible by scrolling through a very long page, or by clicking to unhide certain content.  Most of these plug-ins will also solve the font size problem.  This approach is almost costless – but has some critical flaws.  Read on.

2) Desktop recast approach:  This approach takes the standard design, and during the development process creates special-for mobile layouts and CSS files.  If the top of the home page has a rotating graphic, with five buttons underneath, this approach would simply reduce the size of the rotating graphic, and perhaps move the five buttons to the right (on a tablet), or stacked below (on a mobile phone).  The idea is to code the page so that the design easily flows from one layout to the other, based on the window size of the device. While the design is custom, this approach evolves that design from the desktop.  It also has a critical flaw.  Read on.

3) Use-case approach: This approach is embedded within the strategy and design process, and starts with one question: what would the user want to do when using the mobile site?  Likely, it is to find the organization’s street address or phone number.  Or perhaps it would be to register their product, or access customer-support how-to videos.  If this is true, then fancy rotating graphics (which take a long time to download) and “welcome to company ABC” text make no sense on a mobile home page.  In a Use-case approach, most of the content will still be accessible to mobile users, but the design and prioritization of the content may be very different indeed.

This week’s action plan:  Who are your organization’s key stakeholders?  This week, walk in their shoes, but use your smartphone. When you go to your site, is it responsive?  And if the site is responsive, is what you (they) need front and center?  If not, it’s time to re-think your mobile strategy.

Note: The Make It Happen Tipsheet is also available by email. Go to to register.

Randall Craig

@RandallCraig (follow me)
:  Professional credentials site
.com: Web strategy, technology, and development
:  Interviews with the nation’s thought-leaders


Mobile site or Mobile App?

by Randall Craig on November 28, 2014

Filed in: Blog, Make It Happen Tipsheet, Mobile, Web

Tagged as: , , ,

At a certain point, every organization will ask the question about whether or not they need an App.  Putting aside whether there is a bona fide reason for investing in an app or not, there is a second related question that always gets asked: if we have a mobile (eg responsive) website, do we actually need a mobile app?

To help answer this question, we have assembled a brief summary of the advantages of each platform:

A mobile website:

  • Since the organization is investing in the website anyway, the marginal cost of a responsive mobile website is very low.
  • There is little or no “extra” maintenance, since anytime something is updated on the main website, the mobile site will automatically be updated.
  • Everyone has a browser on their smartphone: it’s just a matter of typing in the URL to bring up the mobile site.
  • There is no need for the user to go through the extra step of downloading the app.
  • No app development expense; no app support requirements.
  • No decision as to what platform to develop the app for:  iOS, Android, Windows, BlackBerry.  The mobile site works on all platforms.

A mobile app:

  • Easier to discover: billions of webpages, only several million apps.
  • Once downloaded, it has a coveted spot on the user’s device.
  • A dedicated user interface that isn’t constrained by the browser’s technical limits.
  • The ability to monetize through in-app purchases.
  • A closed system: Less user distraction from websites or third-party ads.
  • Most apps are not dependent on a data connection, and can run in a subway, remote mountaintop, or airplane.

This week’s action plan:  This week, we are making an offer: ask us, and we will provide three ideas for how mobile can be used by your organization strategically, and for balance, three reasons why you should give mobile a pass.  The goal is to start an open conversation about the could be.

Note: The Make It Happen Tipsheet is also available by email. Go to to register.

Randall Craig

@RandallCraig (follow me)
:  Professional credentials site
.com: Web strategy, technology, and development
:  Interviews with the nation’s thought-leaders