All Posts in mobile
What do you do when you want to share specific information with your company, or solicit feedback on a certain project, or ask a question of your colleagues? You could email your entire company, but these days, people are pretty sensitive about extra emails cluttering their inboxes and interrupting productivity (and if you work with developers, you know that can be annoying and costly). Depending on the topic, it might even feel spammy.
We just launched the new Facing Disability mobile application under the design leadership of Ed Lafoy, our resident iOS wizard. This new app allows anyone to create and upload videos to Facing Disability's website.
Facing Disability is a nonprofit organization supporting and connecting individuals suffering with spinal cord injuries. The site aggregates more than 1,000 videos and shares answers to common questions about coping with spinal cord injuries. The videos are highly curated, edited, and are the culmination of more than a year of interviews.
The new mobile app makes it possible for even more people to contribute their voices and perspectives to FacingDisability.com. Now members can securely contribute videos anytime, anywhere, and enjoy a new flexibility and accessibility that’s particularly important to the Facing Disability community.
Earlier this month, our CEO and founder Josh Golden chatted with Art Norman and Charlie Wojciechowski of NBC Chicago's Weekend Web. On the docket: The great work we're doing as part of our technology partnership with Chicago Ideas Week (CIW) (October 14-20).
Check out the interview below, where Josh discusses the new platform and ticketing system we built for CIW, and be sure to check back on September 1, when tickets go on sale to the public.
Earlier this spring, we wrote an article about the 10 questions to ask when choosing between a responsive website or a native mobile app for your business. It's question a lot of people are asking these days, so we decided to turn it into a helpful infographic, which VentureBeat featured on its site last week.
Use the chart below to help you decide whether your company needs a responsive website or a native mobile app.
Special thanks to Kenton Quatman his infographic design.
TechWeek Chicago is just around the corner again and we'll be back (June 27-29, Merchandise Mart). As Chicago's tech scene continues to grow and thrive, we love getting the chance to listen, learn, and participate in this ever-evolving community.
This year we’ve got two Table XIers speaking at the conference, so be sure to register and get these talks on your calendar.
COO Mark Rickmeier — Mobile Prototyping: TechWeek Lab Coat Series
Fri, June 28 / Bing Stage / 3–3:30 pm
Mobile applications require massive amounts of usability testing and incremental design—nowhere is rapid prototyping more important. We'll explore the best tools for quickly creating functional prototypes that you can use for customer demos, as well as which tools to avoid. If you're still using whiteboards, powerpoint, .psd files, or balsamiq to convey your mobile app concepts, this talk is for you—you'll leave with options and ideas to put to work following your TechWeek experience.
Senior Developer + Agile Coach Noel Rappin — Welcome to Ember.js
Fri, June 28 / Technical Stage / 11–11:30 am
“Do I need a responsive website or a native mobile app for my business?”
We’re getting this question a lot these days.
Let’s back up. For those unfamiliar, “responsive design” refers to a design approach aimed at providing optimal viewing, reading, and navigation experiences on any size device, from desktop computer to mobile phone. Mashable called 2013 the year of responsive web design. We couldn’t agree more.
Even if you have a mobile app, your website should use responsive design to ensure that anyone visiting your site via mobile phones and tablets will have a good user experience. After all, despite the fact that you may have a beautiful app, a segment of your target audience will still visit your website from their phone's browser. And remember, just because you have an app, it doesn't mean it will be downloaded and used. (Just ask the makers of the thousands of undownloaded “zombie” apps about the competition out there.)
That said, there are times when having a mobile-optimized site and a native app makes great business sense. Wondering if this is you? Consider these 10 questions, which could help guide you to the answer.
1) Will your native mobile app take advantage of smart phone functionality?
Do you need to use the camera, GPS, scan feature, or other phone functions? If you intend to provide unique functionality or content not available on the mobile web, then an app is likely the way to go. When Sprout San Francisco came to us wanting to build a mobile app, we knew that we could provide a useful tool to soon-to-be parents by incorporating the scanning function into the app. This allows parents to easily create registries on-the-go straight from their phones, something they couldn’t do through a responsive design website.
2) Is personalization important?
One of the great features in a mobile app is the ability to craft personalized experiences for the device with fewer limitations. Since a native mobile application is always tied directly to a user’s device, it creates many more opportunities to target and craft the user experience. For example, within a native app a user can create and save a profile, which allows them to customize their interactions. UBER has an excellent native application which lets users scan and remember credit card details, making future purchases quick and simple.
3) Do you have complex design and UI?
At a certain level of complexity, HTML5 (responsive web) may not work to achieve your goals. HTML5 can indeed deliver customized user experiences, but native apps tend to provide the most tailored UX. Because responsive designs need to adapt to all possible environments, designers have to make compromises to find a solution that works in all scenarios, browsers, and screen sizes. Conversely, a native mobile application is a targeted experience and can take full advantage of the interaction expectations of the user and their device. Web apps still have a lot of room to grow (see forecast.io, for instance), and while they’ll eventually get close to native apps in feel and function, they can’t match them—yet.
4) Do you have a limited budget?
Generally speaking, responsive design is a less costly undertaking because it’s quicker to develop and deploy than native applications, typically requires fewer dedicated resources to bring an idea to market, and only needs one code base to ensure it works across all devices. That said, ideally, ROI justifies development costs. If mobile transactions and in-app purchases represent a significant portion of potential revenue, investing in app development could be the smart decision. But if you can’t afford the spend immediately, start with a responsive website and add the native app as part of a future iteration.
5) Are you trying to monetize content and encourage purchasing?
If you have a product that offers potential for ongoing micro-purchases, then a native application is the way to go. A shopping cart on your website can facilitate this, but the in-app purchasing system is so simple and tied into all the rest of a user’s purchases on the platform that it is second to none.
6) Is SEO an important consideration?
If part of your strategy is to increase visibility among search engines and drive traffic to your site, then stick with a responsive mobile website. Apps are closed environments and cannot be crawled by search engines—they won’t impact your organic search ranking.
7) Will you have difficulty getting App Store approval?
Apple asks developers to follow stringent guidelines when submitting to the App Store, and the approval process can take anywhere from a week to several months. There are certain areas that are regulated more strictly than others, such as in-app purchases and in-app subscriptions.
Moreover, other kinds of features easily achieved through HTML5 are banned in native iOS applications. For example, Apple regulations forbid iOS applications that take donations, a fairly commonplace transaction in responsive web designs. This is a serious drawback for nonprofits looking to reach potential customers and donors through mobile apps.
8) Are you sending and receiving massive amounts of data?
An app will generally work faster than a responsive website since it doesn’t rely as heavily on Internet and network speed to serve up information. However, responsive websites may be closing the gap—a recent article in Ars Technica discusses the ways that developers are trying to "speed up the web" to compare with native speeds.
Advantage: Native (for now)
9) Do you plan to make frequent updates?
Native applications make frequent updates rather painful. First, application updates need to go through the same lengthy approval process in the App Store. Next, native applications require consumers to manually download the updates before they can be used. If you expect to have frequent design updates, a responsive design may be the simplest way to ensure your users are accessing the most recent version.
10) Are you trying to create something that’s universally accessible?
If you want to appeal to everyone across multiple platforms and devices, responsive is the answer. It’s faster and easier to get your product in people’s hands, and it’s fairly straightforward to build a mobile-specific menu that gives mobile users what they need. Native apps, on the other hand, must be uniquely designed for Android, iOS, Blackberry Mobile, and Windows Phone 8, and present compatibility concerns for businesses that don't want to segment their user base.
So there you have it: 10 questions to help guide your decision-making process. Granted, these aren’t hard and fast rules, but thinking about these factors can get you started. Still stuck? Don’t hesitate to reach out with questions or comments. Email me at email@example.com. And if you do decide to build a native mobile app, make sure you’re familiar with the 5 mistakes to avoid when developing an app and the 5 things that annoy app users.
Special thanks to Table XI’s mobile development team for their contributions to this article: Ed Lafoy, Kate Garmey, Jon Buda, and Mike Gibson.
Mobile apps are all the rage these days, but it's easy to create something that just leaves your customers raging. Make sure your app isn't guilty of these sins that drive users nuts:
1. Forced registration. Unless you’re a service I trust and I’m accustomed to using, why do you make me register before I know what I’m getting into? Getting a download is hard enough. Don’t raise the bar even higher by forcing another action before a user can interact with—and find value in—your app.
2. Complicated navigation. Part of the advantage of using an app (versus a mobile site) is the ability to deliver targeted content at the touch of an icon. While we recommend everyone adhere to the “Three Click Rule” of usability, it’s even better if you can deliver in one or two. And it’s just as important to give your users an easy way to navigate back to previous pages—no one likes getting lost three pages deep.
3. Preference amnesia. Now that we’re a population of app-savvy users, our expectations have changed. If I’ve entered information about myself and my preferences, I expect my app to be “smart” about it. Leverage the data I’ve provided before to serve up relevant recommendations or information.
4. Long forms. Nothing is more annoying than trying to pick through registration forms with your thumbs. Limit forms to the minimum fields required, and use shorter alternatives where possible, such as a ZIP code instead of city and state. Wherever possible display default values, like today’s date or nearby locations.
5. Ratings prompts. Once is understandable (if tastefully done), twice is annoying, three times is desperate. Don’t constantly ask me to rate your app—it’s getting in the way of enjoying your app.
For more on mobile app best practices, check out Mashable for my 5 Mistakes to Avoid when Creating Branded Apps.
Each month we try to bring you a new technology or service that makes your life easier. The newest craze sweeping our office doesn't require an internet connection, or even a plug: Meet the collapsible, pocket whiteboard called the Noteboard.
"Durable, portable, and infinitely re-writeable," Noteboard consists of a grid of laminated index cards that fold up map-style from 35" x 15" to 5" x 3", and can be wiped clean with a dry-erase board eraser. Nothing fancy, but sometimes the best solution is the simplest one.
Already our team has found many uses:
1. Presentations. We've been sketching out our ideas for presentation slides on Noteboard's index cards; folding the grid in different ways then allows us to visualize alternative slide orders. The convenient portability means that if inspiration hits on the train or in the Starbucks line, we can capture thoughts on-the-go.
2. Interviews. Rather than make interviewees use the wall whiteboard to solve a problem, we spread the Noteboard out on the table for them. This way our group can observe their thought processes without all that pressure of standing up at the front of the room, like you had to do in math class.
3. Prototypes. Since each index card is roughly the size of an iPhone, our mobile devs use them to design app pages and flow. Then they take photos of each card and map out app prototypes on POP.
So there you have it: a low-tech tool for high-tech problems. And at $10 a board, it's a cost effective one, too.
Planning to pick up your own Noteboard? Let me know—I'm curious to know how you use them.
We’re always on the hunt for new technologies that will improve the process of developing and designing mobile apps for our clients. Recently we stumbled upon a great little app called POP—short for “Prototyping on Paper”—that animates your wireframes.
Normally, during our inception process with a client, we (the client included) break apart into groups to hash out what we think each chunk of the product will do, as well as what it will look like. Typically we use giant, 2 x 2.5 ft. sticky notes and a Sharpie to draw up basic wireframes. This serves us well since it allows us to brainstorm separately and then reconvene to talk through our thought process and ideas. But sometimes it can get complicated to try to show the flow of an app—i.e., where buttons will link to—using only pen and paper.
POP solves this. Take photos of your wireframes, then link your sketches together with “link spots” to create an interactive, automated storyboard. Designers and clients alike can then get a more accurate simulation of your app prototype’s user interface and flow. You can do this directly on your iPhone, or use Airplay and an Apple TV to project the prototype for a group.
As a bonus, POP also lets you share your prototype—it’s viewable on iPhones, iPads, and web browsers—so it’s easy to send off to others who may need to weigh in on your design.
This app is obviously helpful for developers, but we encourage our clients and other non-devs to check it out, too. If you’re looking to build a mobile app for your business and have thoughts about what it could look like or how it might work, POP is a great, user-friendly way to convey your ideas.
Plus, the kids love it.
Sign up for our monthly newsletter to stay up to date on the latest tech tips from Table XI and to receive exclusive invites to events