How is Blue Label Labs different from its competitors?

First, we live and breathe cutting-edge/bleeding-edge technology, so your app will similarly be cutting-edge/bleeding edge with a long “shelf-life”. Second, with a perfect mix of local, domestic and international talent you are guaranteed to get the optimal mix of a high-quality product and a fair price. Third, you will be assigned a dedicated Program Manager (PM) after we’ve established a contract who will be your single point-person for all of your needs and questions. This PM will stay with you for the duration of your relationship with Blue Label Labs and is your conduit to all of the resources we have to offer, thus streamlining your communication and preventing you from having to repeat your message to multiple resources or play air traffic control. Our PMs are the best in the business and we’d be happy to introduce you to a projected PM (and project team) once we’ve got an estimate on the table to discuss. Fourth, the size of Blue Label Labs team (now 64 people strong) means you don’t have to worry about the “single point of failure” issue that exists at smaller shops of just one or two developers, nor the burden paying for the high overhead cost associated with larger shops. Fifth, we have a stronger focus on design than most other shops. We split our design team into two specific functions—Product/User Experience and User Interface. It’s a rare unicorn designer that is good at both thinking through flow and product decisions, as well as branding, colors, logos and overall User Interface. To that end, each project team has both a UX Designer and UI Designer staffed to ensure top notch design. Sixth, with over 7 years of operation and over 250 apps completed, we have both the experience and extensive re-usable code base to ensure your app is built as efficiently and as inexpensively as possible. Seventh, our QA and Testing methodology is rigorous and as important to us as the actual development—meaning your app will be as bug free as is possible. We have a dedicated QA Engineer staffed on every project. This engineer is not the original author of the code ensuring the highest quality results from the QA process. Please see the below sections for more details.

How does Blue Label Labs work with clients?

Blue Label Labs Labs begins most projects with a Discovery, Planning & Design Phase (Phase One). First, we determine the proper technologies and development schedule. Second, the Design teams inherit the User Stories that were drafted during the sales process. User Stories are simple one-liners that outline the activities your users will need to be able to accomplish within the app. These User Stories then get grouped together into meaningful features and feature sets. The Design teams work with the client to finalize the User Stories. Third, our design team sets out creating greyscale wireframes to illustrate how a user will move through the app (i.e., the user experience, UX). Fourth, we transition to full color illustrations/designs that have the final look and feel of the app (i.e., the user interface, UI). Fifth, the app designs are then uploaded into a prototyping platform called Invision that allows our team to create tappable and swipeable “hotspots” so that you can show the app on your phone or via a mocked-up phone in a web browser. At the same time, we draft a Functional Specification document that details the technical hows and whys of the project for the development team. Once that work is complete, we them move on to the Development Phase (Phase Two). The Agile development/engineering team works hand-in-hand with the Program Manager and follows the wireframes and the Functional Specifications to build the app. Our first development goal is the First Deliverable milestone—we call this D1; this is a highly functional build of the app that contains a subset of features agreed upon by Blue Label Labs and the client. We then begin an iterative process of finalizing the remaining features. At the same time, a QA Team builds a full test plan for the app. The QA Team continually performs functional and regression testing on the app, reporting issues to the Project Manager. Learn more about our process here.

How long does it take to complete the average app?

Typically, for our average 4 to 5-month project, the Phase One: Discovery & Planning and Design lasts for approximately 4 to 6 weeks, with Phase Two: Development and Testing Phase occupying the remaining 3 to 4 months. At the end of the Phase Two, the final app is prepared for Deployment. Deployment involves moving any web services and server side components to a production environment and submitting the app to the relevant app store(s).

How much does the average app cost?

If we were in full-swing on a new project, a client can estimate a cost of between $10,000 and $30,000 per two-week sprint ($20,000 to $60,000 per month) for the effort—typically billed bi-weekly. If Blue Label Labs is handling everything from Discovery, Planning & Design through to Deployment in an app store, total app costs average about $120,000 for one “platform”–iOS, Android, Web, etc. That said, it very much depends on the complexity of the design and development required for each individual app, we’ve completed full apps at costs of between $50,000 (a bare-bones, simple MVP/prototype) and $2,000,000 (a full featured, enterprise apps). We provide free, no commitment estimates to clients. After the app is submitted to an app store(s) or pushed live on the web, the Blue Label Labs team monitors the app store and customer reviews and deals with any issues, questions, delays or approvals that arise. We have a great track record with app submissions and make sure that the app submitted is highly likely to be approved without issue. Post approval, a maintenance agreement can be put into place to cover and small issues, minor app edits (e.g., color, image or text changes) and any bugs that might linger. At the end of the project, we will transfer all source code and project files to you and you will remain the sole owner of all IP in the app. After that time, we provide our services at an hourly rate of $120/hour for ad-hoc updates or at an hourly rate of $100/hour for a mutually agreed upon set number of hours in a 6-month retainer. The monthly maintenance cost for the average app is $2,000/month: in other words, a retainer of 20 hours per month at $100 per hour equals $2,000/month and guarantees expedited service vs. ad-hoc requests.

What is the difference between a Native App, a Hybrid App and an HTML5 App?

Native App: A Native App is an app written for a specific platform like iOS or Android—in other words, the app is written in the coding language used for development on that specific platform (Objective-C or Swift for iOS and Java for Android). When you build a Native App, you get access to all the hardware features exposed by the native code APIs and SDKs. For example, Apple iOS Push Notifications are one example of a feature that cannot be supported by an HTML5 App. The graphics and user interface of a Native App are far superior to any Hybrid or HTML5 app. You would choose this option, if you want to use the user interface components from Apple’s proprietary user interface libraries (i.e., the usability is better); you want full device hardware access—cameras, microphone, and geo-location; you want peak performance with no lag; you want users to be able to access the app off-line (i.e., without Internet access); you want access to push notifications and in-app purchase; and you want your app to de discoverable in the app store. On the downside, your code is less portable across operating systems and it is often the most expensive development option. It is our recommendation that if you plan to start a true, revenue generating, app-based business, this is the only viable option. Hybrid App: A Hybrid App is a form of web app that is deployed to a native platform like an iPhone or Android phone inside a native shell. This shell is usually little more than a web browser view (to display the HTML5 content) and some other hooks to allow your web app to potentially access some more hardware features that are not available inside a typical mobile web browser—e.g., push notification and in-app purchases. It improves code portability because if you want to port your app to another platform, you only need a native shell on that other platform to run it, the HTML5 content of the app is directly portable. These shells can be hand written, but can also be generated automatically by tools in the marketplace like React Native, PhoneGap, Cordova or Xamarin. These tools allow a developer to push the app out to multiple platforms (e.g., iOS, Android, Windows Mobile) quickly by generating the shell and packages required to do so automatically. This sounds powerful, and it is, but clearly creators of these third-party platforms have a lot of configurations and hardware to support, and thus, the solutions do not always work the same across all devices, and in practice, testing and hacking of special cases will be required by the developer to get proper functionality. You would choose this option if you want a balance between cost and usability; you want access to some (but not all) of the phone’s native APIs/SDKs and hardware; you want to be able to quickly deploy across multiple device types; and you’re not worried about high-end graphics. On the downside, because these third-party hybrid platforms (e.g., React Native, PhoneGap and Xamarin) need to support so many device types there are always implementation and usability issues to workout. In addition, you will only have access to the features of a new operating system 6+ months AFTER it is released by Apple, Google or Microsoft. In this way, your app will never be able to cutting-edge technology. While we are fully capable of building Hybrid Apps, it is our recommendation that this option is only viable for simple, lo-fi apps that are heavy on text and images, but don’t need much in the way of functionality or user interface. An HTML5 Web App: An HTML5 app is essentially a website with JavaScript code written to allow the app to perform dynamically, as opposed to a static website that you need to refresh to see the changes. It works interactively to make it feel like an app, but it is actually running in a web browser. It is essentially a website, which will support multiple viewports or screen sizes so that it works well on mobile. Because it is running in a browser, it is confined to what is possible within a mobile web browser. You would choose this option if you want to support multiple platforms with the same app/codebase; you want to deploy it on the web; you want the widest possible support across multiple device operating systems and manufacturers; and you want to be able to update your source files on your server and have them immediately deployed to all devices (i.e., removing the need for the app approval process). On the downside, your app is not discoverable in the app stores; it will never look and feel like a true mobile app; and you will have limited access to some of the software and hardware functionality of the phone (e.g., push notifications and cameras). It is our recommendation, that this option is only viable for view-only content where users are not expected to interact in any meaningful way.

Has Blue Label Labs ever transitioned an app the firm has built to a client’s internal development team? What is the typical process and how long does it usually take? Is there a fee for this?

Quite often Blue Label Labs transitions an app to a client’s in-house development team. As part of our regular transition for any client, we transfer all functional specs, wireframes, UI design resources, screen flow maps, passwords/certificates/credentials and source code to the client. We also have extensive experience working in tandem with a client’s existing engineering team. For example, Blue Label Labs will build the front-end experience of an app on top of a client’s existing backend web service and databases. These transitions are the quickest, averaging only a few days, since the Blue Label Labs team and the client team have already been working hand-in-hand for months. If we are handing over a complete project with no prior engagement with the client’s development team, then the transition can take a little longer depending on the support needed. This can range from a few days to a couple weeks. The transition is typically free of charge unless engineering resources are needed to facilitate the transition or the Program Manager is required to spend more than a week on the transition and training. We’ve even helped companies to interview potential new technical team members—e.g., developers and CTOs.

How does Blue Label Labs provide training to a client’s development team so that they could make app enhancements and how much would that training cost?

Along with all the project documentation and support outlined in the answer to the question above, we are happy to provide hands-on training to in-house developers/team members as part of the transition. There is typically no extra charge for this if only a few hours are required. If ongoing training is necessary, for example an in-house developer is not familiar with app development and requires a crash course, then we can offer our services at our hourly rate of $120/hour for training. We’ve even aided our partners in their hiring of their own technical/development team if/when the time is right.

How many designers and developers does Blue Label Labs have on staff? How many work on each client project? Where is the team located? Can the client talk directly to whomever will work on the app?

The Blue Label Labs team is comprised of 64 individuals across its UX Design/Product, UI Design, Development, Program Management, Quality Assurance, Sales, Marketing and Leadership teams. We have 6 Designers, 10 Program Managers, 35 Developers, 3 App Marketers—the remainder of the team is comprised of the Sales, Marketing, Operations & Leadership Teams. Depending on the size of the project, a team of at least 7 Blue Label Labs staffers will work on your project: 1 Program Manager, 1 UX Designer, 1 UI Designer, 1 Technical Architect, 1 Front-End Developer, 1 Back-End Developer, and 1 Quality Assurance Engineer—in addition to the technical and strategic oversight provided by Blue Label Labs leadership. The majority of our Design and Program Manager teams is based in New York City, Seattle and San Francisco areas. The Developers and Quality Assurance Testers are also based in the aforementioned cities, in addition to India-based team members. The Development, Design and QA Teams are managed directly by the Program Manager. The Program Manager is your primary point of contact and the liaison across all other Blue Label Labs team members associated with your project. That said, clients are welcome to speak directly with any individual team member as is needed.

Are projects priced based on “time-and-material” (i.e., hourly) estimate or a “fixed-price” quote?

Projects are priced on a “time-and-material” basis. With 7 years and 250+ apps of experience to our credit, we are able to produce very accurate estimates. We do our best to stay within budget or provide you ample warning if we think we may exceed our initial estimate so we can coordinate how to move forward together with you. Prior client references can vouch for the accuracy of our estimates and can be provided to you upon request.

Is Blue Label Labs able to guarantee that our app will be published in an app store?

Unfortunately, no application can be guaranteed for app store approval. However, Blue Label Labs has successfully built and deployed over 250 apps for the Google Play and Apple iTunes stores. We have a solid understanding and insight into what these stores will typically approve or disapprove of. We will warn you well in advance if any particular aspect of you project poses an approval risk. We have had a handful of instances where an app store has rejected an app for publication; not due to technical issues, but due to legal/business/terms of use issues; however, we successfully appealed ALL of these rejections and these very same apps are now in the app store for download today. We led these appeals on behalf of our clients at no extra charge. If your app is rejected due to technical reasons, we will make all necessary corrections needed to get approval at no extra charge. We are happy to connect you with some of our clients who did face some app store pushback to tell you about the rejection and our successful appeal.

What is Blue Label Labs’ policy regarding correcting defects and publishing an update in the app store?

We provide our services at a blended hourly rate of $120/hour for ad-hoc updates or at blended hourly rate of $100/hour at a mutually agreed upon set number of hours over a 6-month retainer. For example, a retainer of 20 hours a month for $2,000/month guarantees expedited service vs. ad-hoc requests. Ad-hoc requests are handled on a first come, first serve basis across all of our clients and development is based on our team’s earliest availability. The monthly retainer of hours functions much like an extension of the warranty period; issues are addressed within 24-48 hours and development will start as soon as the scope of the issue is defined. For those clients wanting a guaranteed 24 to 48-hour turnaround time on maintenance issues, a 6-month retainer is suggested.

What level of Quality Assurance is included and provided by you in your proposal?

A Quality Assurance (QA) Engineer is assigned to every project and builds a custom test plan for every project during the Discovery, Planning & Design Phase. During the Development & Testing Phase the QA Engineer continually tests the app using functional and regression testing. We test on a wide array of physical devices as needed for a given project. If we are building a backend web service and databases as part of the project, we will also have a set of automated unit tests that are run regularly to verify functionality.

What is Blue Label Labs’ quality assurance (QA) and testing methodology?

We believe that Blue Label Labs’ QA and testing methodology is part of our competitive differentiation. The fact that we dedicate resources to solely this function is something that sets us apart from other development shops for whom testing is simply an afterthought. At Blue Label Labs, QA is handled at all levels of development. There are generally 3 layers of QA/testing that happens for every project: 1.) Internal Development Team Testing Each Development Team has an internal QA Tester along with the Developer Lead who perform basic validation on bug fixes prior to builds being released to the broader Project Manager and QA team. Their validation is to ensure that items within JIRA, which we use alongside Trello, to coordinate team efforts and communicate with clients—are properly remedied according to their descriptions prior to “checking-in” or committing code. When items are resolved by the Development Team they are pulled into the “Testing Done by Dev Team” stack of Trello cards and/or within JIRA. When developing new projects, the Blue Label Labs Development Team will also be responsible for creating “unit tests” for our code so that we can quickly run a basic set of verifications. The dev team does the majority of their testing using iOS and Android app simulators. 2.) Dedicated QA Engineer Each project has a dedicated QA Engineer who sits independently from the Development Team who is responsible for: a.) Drafting a milestone based test plan which outlines a list of black box scenarios to verify and the expected results; b.) Performing smoke and full test pass runs against weekly and milestone builds; c.) Verifying and closing bugs that the Development Team has marked as complete; d.) Working with the Development Team to report issues and regressions; and d.) The QA Engineer takes items from the “Testing Done by Dev Team” Trello stack and verifies whether it is actually fixed. If it is, the Trello card is moved to the “Done (Verified)” pile, or sent back to the “Weekly Priorities” or “Product Backlog” stacks, as appropriate. The QA Engineer will generally perform their tests on 2-3 devices, depending on project requirements. 3.) Project Manager (PM) Testing The final QA gate is the PM who is responsible for quality of the entire product. They will also work with the QA Engineer to verify items have been fixed properly in addition to triaging new issues coming in from the client and the QA Engineer. The PM will appropriately schedule issues to be resolved based on their severity and importance. The PM’s testing is done on actual devices.

Can Blue Label Labs help me with Marketing and PR?

Absolutely. We aim to be your full-service app partner. Our Marketing & PR Offering is designed to help you launch your app and gain marketing exposure. Learn more about our Marketing & PR Offering here.

App Design & Development

9 Essential Tips For UX Design In Healthcare

Across industries, good UX design is a foundation for creating a functional, modern application. Consider these statistics that illustrate the power of good UX design:

A Forrester study concluded that better UX design could improve conversion rates up to 400 percent
52 percent of survey respondents said poor mobile UX makes them less likely to engage with a website
Toptal found a 53 percent bounce rate for mobile users when a page takes more than three seconds to load

Healthcare is no exception to the trend of focusing on user-centric experiences. The implications of UX design in healthcare are significant, with doctors, support staff, and patients benefiting from consistent and user-friendly healthcare apps. Here are nine essential tips to consider when incorporating user experience design into healthcare software and websites.

1. Apply the UX Design Thinking Framework to healthcare

The UX Design Thinking Framework is a helpful starting point for implementing good healthcare UX design. It focuses on design thinking, which is a problem-solving approach wherein teams try to come up with solutions that meet users’ needs while being economically and technically feasible.

The process has five components:

Learn: Observe the needs of the patients and clinicians
Define: Formally identify the needs and informing stakeholders
Ideate: Develop ideas relating to design and functionality
Build: Create a prototype that highlights all of your data
Iterate: Repeat the process to create a better final product

Overall, the goal of the UX Design Thinking Framework is to correctly implement an app that provides benefits to patients and clinicians while highlighting the needs of the patients in particular. When following the framework for healthcare implementation, the plan is to be solution-oriented, iterate frequently, test often, and continue implementing feedback to move the product towards its best version.

2. Use HIPAA updates and mHealth

When implementing an app into your healthcare facility, don’t forget to comply with HIPAA regulations regarding app development. Though this can present some UX challenges initially, keep in mind that the major factors required in a HIPAA-compliant app are technical safeguards to protect patient information, physical safeguards to control access to work sites, and administrative safeguards to guarantee compliance among staff members.

When it comes to mHealth apps, major HIPAA-compliant features may include:

User identification software (username/password, fingerprint identification, etc.)
Audit controls to track patient usage
Data encryption to validate and protect patient health information

The focus of the HIPAA regulations is to protect the user and their personal health information. When users are required to insert their username and password when logging into an app, it provides a sense of relief and trust that their information is protected by the app and not visible to other people or users. In the end, complying with HIPAA requirements is both legally necessary and beneficial to good healthcare UX design.

3. Don’t be afraid to use different types of media in your healthcare UX

Building an app that keeps users’ attention and promotes continuous usership is one of the greatest UX challenges, but including different types of media can help keep your users engaged. Don’t be afraid to branch out and try something new. Here are some media types to consider leveraging in your healthcare UX:

Images to help break up text
Animations for things like clicking buttons or marking off items on a checklist. These small interactions provide immediate feedback to users and help create a more personalized experience.
Video content for those who are more visual-oriented. Videos can also help capture attention longer than text alone.

The best way to utilize media in your healthcare UX design is to do so subtly. These features should garner attention from the user without distracting them from important information included in the app. For example, flashy images, autoplay videos, and constant moving features in an app can be seen as annoying or invasive and may turn a user away from the app or cause them to miss some of the more important features of the app.

4. Offer plenty of support

One of the most significant features of UX design for healthcare apps is the ability to gain information on one’s own time without necessarily communicating with another individual. Essentially, users want content that is easily found and highly informative.

If the content of your app often results in users requiring further explanation, you should implement a menu that allows users to easily navigate and ask for help. To provide more valuable assistance to your users, here are some user experience design tips for your healthcare app:

Clearly label menu items and page headers to allow users to always know their location on the app (i.e. which section they are in).
Provide a help button that leads users to a page of commonly asked questions. To make this more effective, record the thoughts and questions users have when testing the app. If you notice that a considerable portion of app testers are unable to locate a specific section of your app, revise your content.
Provide a live chat function on your app. With a 24/7 staffed chat feature, users can find the answers to their questions quickly and without added frustration. Additionally, some chat functions allow users to type out a question and then a chatbot or representative leads them to a relevant answer on the app.

5. Have an escape mechanism

When using smartphones, it is extremely common to find yourself in the wrong section or page of an app. When this occurs, users want an easy way to return to where they were without resetting their progress.

The most important feature you can include in your app is a “back” button. Oftentimes, a “cancel” button is associated with closing a window or exiting an app, which, in the case of accidentally clicking on a specific section of an app, is not what the user is looking to do. Providing a “back” button allows users to return to their previous location without starting over.

If your app includes features that allow users to fill out forms, provide a “save” option in case the app is closed or the user clicks the “back” function. Allow the user the option to save their data indefinitely to reduce the time necessary to fill out the same or a similar form on the next occasion.

All apps have a home screen and your app is likely no different. Sometimes users find themselves in an unknown section of the app, and requiring the users to click the “back” button as their only way to return to the app’s home screen can be tedious. With that said, your healthcare app’s UX design can include a toolbar at the top or bottom of the screen that allows users to return to the home section of the app.

6. Know which UX design tools to leverage for healthcare apps

When designing an app, the most important aspect from the perspective of a developer is knowing how to work your design and prototyping tools. Using design tools that you know will work effectively together leads to the development of a more user-friendly and engaging app.

There are a lot of tools out there that can be used for UX design in healthcare, but selecting the newest tool is not always the best option. For professionals, some of the best tools are the old standbys that many new developers have begun moving past. In the end, you need to select a tool that your team knows how to use in-depth and at maximum potential.

7. Do realistic research into the healthcare industry

Though you may have the perfect healthcare UX design in your head, this is not the most effective approach for app development. Creating a useful and user-friendly app requires extensive research. Sometimes, it may be important to research the right healthcare app development company.

You can start by looking at previous studies, statistics, interviews, or surveys that provide relevant insight for your design. However, the main portion of UX research for a healthcare app should focus on your users themselves. This process may include observing individuals as they interact with the prototype or interviewing users to determine their needs and questions related to the current version. When selecting the subjects for your app’s testing, you should select members of your target population (those you anticipate using the app, whether that’s patients, doctors, HR professions, etc.).

Before conducting the actual research, you should develop a hypothesis that relates to what your app does and who it helps. When interviewing or surveying users, you will be able to determine if your hypothesis is correct (i.e. the users confirmed the purpose or helpfulness of the app).

8. Test often to determine the quality of your healthcare UX

When developing prototypes for your app, test often, and with real people. Some things you should think about when testing include:

Who do you want to use this app?
What audience will use the app most?
Who will benefit the most?

The best thing you can do when testing your app is testing it in an audience that is (or is very similar to) your intended app audience. This will allow you to get the most relevant feedback on the current version of the app and adjust the features and settings to better meet the needs of this population.

9. Know how the app will help

The best way to help your users and create high-quality healthcare UX design is to understand how your app will help them. Keep these questions in mind:

What does this app do and why?
What does the patient gain?
Does it help monitor and/or simplify treatment?
Does it help educate the user?
What are the positive outcomes we want to create?

If you are unsure of the answer to any of these questions, head back to the drawing board. If you as a developer do not know the purpose of your app, whether it can result in something positive, or if it can be used as an informational tool, it is highly likely that your users will also be unable to answer these questions.

Working With Healthcare UX Experts

The need for UX in healthcare is rapidly increasing, and facilities that implement these nine strategies are likely to find that they improve both patient and staff satisfaction. We understand that implementing good UX is a complex process, and that’s why we have dedicated UX professionals on our team to help implement an innovative design process.

If you are ready to improve UX for your healthcare system, send us a message to discuss your project; we’d be happy to help.

Natasha Singh

+ posts

Senior iOS Developer at Blue Label Labs

9 Essential Tips For UX Design In Healthcare

1. Apply the UX Design Thinking Framework to healthcare

2. Use HIPAA updates and mHealth

3. Don’t be afraid to use different types of media in your healthcare UX

4. Offer plenty of support

5. Have an escape mechanism

6. Know which UX design tools to leverage for healthcare apps

7. Do realistic research into the healthcare industry

8. Test often to determine the quality of your healthcare UX

9. Know how the app will help

Working With Healthcare UX Experts

Natasha Singh

Get the latest from the Blue Label Labs’ blog in your inbox

You might also like

Are You Using AI In Your Job?

9 Essential Tips For UX Design In Healthcare

Natasha Singh | February 3, 2020

1. Apply the UX Design Thinking Framework to healthcare

2. Use HIPAA updates and mHealth

3. Don’t be afraid to use different types of media in your healthcare UX

4. Offer plenty of support

5. Have an escape mechanism

6. Know which UX design tools to leverage for healthcare apps

7. Do realistic research into the healthcare industry

8. Test often to determine the quality of your healthcare UX

9. Know how the app will help

Working With Healthcare UX Experts

Natasha Singh

Get the latest from the Blue Label Labs’ blog in your inbox

Subscribe

You might also like