Just as the spread of COVID-19 was gaining momentum, Anthem launched a virtual care app, Sydney Care. Find out how Foxbox Digital collaborated with the Sydney Care team as the lead mobile app development partner.

How We Helped Anthem Launch a Mobile Telehealth Product During a Pandemic

On January 1st, 2020, just as the spread of COVID-19 was gaining momentum, Anthem, Inc., a leading health benefits company that serves over 110 million people through their affiliated companies, launched a virtual care app, 

Foxbox Digital collaborated with the Sydney Care team as the lead mobile app development partner, because of Foxbox’s experience and deep knowledge of 

Sydney Care, available on iOS and Android, utilizes AI-driven guidance to empower users to assess their symptoms and then choose the virtual care option that’s best for them. Additionally, through its COVID-19 Resource Center, Sydney Care provides an end-to-end solution that helps employees more safely return to the workplace.

“We built a solution that some of our customers have reviewed as being ‘life-changing.’ The ability to address health issues without physically going to a doctor, and in the comfort of their own home, is a rewarding experience to be part of, and we continue to see the growing impact of our telehealth platform.”
- Plamen Petrov, Ph.D., Vice President, Exponential Technologies, Anthem, Inc.

In 2020, Sydney Care was downloaded over 260,000 times, while thousands of users continue to utilize the application daily to diagnose symptoms and seek guidance for their health conditions from a device that lives in their pockets. Additionally, over 41,000 people have assessed their COVID-19 symptoms using Sydney Care.

The pandemic has forced many professionals to work from home and prevented critical care for many non-COVID patients. Sydney Care became a desired application for many people who needed preventative care, and also consumers with chronic illnesses.

“I was able to quickly chat with a doctor this afternoon about allergies and pick up my prescription within an hour. This beat taking 3-hours out of my workday, fighting traffic, and sitting in a waiting room (especially right now during a pandemic) to see a doctor. I found a new way to do health care,”
- jscrmil1, 04/14/2020 iOS App Store

A Delightful Mobile Experience (Built in React Native)

As the React Native mobile development experts, we interacted with Anthem’s Product, UX, Business, Integration, Authentication, Backend Development, and Security teams to build both iOS and Android native applications, using a single React Native codebase.

React Native allowed us to develop one app that works natively on iOS and Android instead of building two separate apps with disconnected codebases. Using React Native as the programming language enabled Anthem to streamline development and maintenance costs while still creating a stellar mobile consumer experience.

Through our collaboration and contributions, we delivered these core features and benefits:

Integrated Video and Chat for Virtual Doctor Visits

: Chat in real-time over video and text with healthcare providers.

:This triage functionality in the app allows a seamless experience for consumers to check their symptoms and get personalized guidance.

:A login-less experience for existing customers, as well as integration with other insurance providers.

: All of the technical enterprise security protocols needed without sacrificing the experience for the consumer.

: The ability to pay via credit, debit, or via insurance provider, all within the app.

A COVID-19 Return to Workplace Solution Built in 10 days

As Covid-19 started growing, we quickly pivoted along with Anthem’s product and design teams to develop an 

AI-powered Covid-19 daily-check in solution

 that helps protect workers by keeping potentially infected employees away from the workplace.

We developed the front-end and back-end of this new functionality and published on both app stores (iOS and Android) within 10 days—in addition to a previously-created COVID-19 assessment solution. This service is currently being used by many large organizations, some with 30,000+ employees, and more partnerships to come.

Better Healthcare Experiences Start with a Seamless Digital Experience

Together, with the partnership of Anthem’s robust global design, product, and integrated teams, we assisted in the development of an easy-to-use, direct-to-consumer mobile telehealth solution. With the added complexity of working within an enterprise environment, we continued to be flexible and agile in our approach of acting like a startup within an enterprise.

We’re honored to work alongside a leader in healthcare and innovation.

“They are professionals, talented, smart. They are committed, with a very strong core team. They owned the problem."
- Elliott Torres, Staff VP, AI and Architecture

Discover why more and more companies are choosing React Native to build innovative digital products.

Why CTOs Should Choose React Native as Mobile Platform

I’ll be honest, for the first eight years after iOS was released, building an application natively within iOS made sense and was the only proper decision to make. 

 had promise but lacked many core features and UX experiences that it didn’t make sense to switch over.

Native apps are considered the gold standard and offer the best overall performance, user experience, and access to hardware-related features such as support for multi-touch gestures, access to the camera, GPS, calendar, accelerometer, and much more.

But now the mobile world has moved on and React Native is the right decision for many companies.

React Native has transformed the whole dualistic notion of iOS vs. Android by creating beautiful apps for both platforms from one codebase—without compromising on the UX and UI. On a React Native app, everything you see and touch is native.

So unless you are Uber or Airbnb and can afford to spend money and time on exclusive native mobile development, your business really should be using React Native as its development platform of choice.

The reason is fairly straightforward. With React Native, you have a best-in-class framework that is optimal for 95% of all business use cases.

React Native is especially good news for CTOs and VPs of Engineering because instead of hiring two additional development teams for Android and iOS, you can leverage your existing web development team to build your mobile app. React Native represents the best organizational choice for CTOs and VPs today.

I didn’t want to start with this because I don’t think “

” is a valid excuse, but the maturity of React Native makes it an easier business case for your organization.

React Native was introduced in 2015 and underwent the initial stable release in July 2019. Over the past four years, it has become a robust worldwide open-source community with over 

 contributors on GitHub—and, of course, with the backing of Facebook. It’s also the 

 of contributors for any repository on GitHub in 2018.

React Native developers are continually building new libraries, updates, and projects. With cross-platform compatibility, shorter development cycles, faster releases, live code pushes and updates, and overall performance improvements, many have come to see React Native as the future of mobile development.

Facebook originally developed React Native as a hackathon to support its cross-platform needs. The beauty of React Native is that, unlike “hybrid” mobile app solutions, it uses native UI elements instead of rendering the entire application inside of a WebView. Your business logic is run in a separate JavaScript thread, which then controls the native UI elements. In the “old days,” companies had to develop native apps for both Android and iOS from scratch.

React Native allows developers to write code in just one language, JavaScript, then build binaries for Android and iOS. It eliminates the need to hire both iOS and Android developers to write dual applications, and this represents a huge benefit in terms of productivity, costs, and time to market. Not to mention the reduced hiring burden!

As a CTO, you’re most comfortable managing a company you understand. If you happen to be an Android “guy and need to hire an iOS developer, you’re not speaking the same language and have to work extra cycles to get everyone on the same page. This can easily lead to operations hang-ups and production slowdowns.

Being able to write once and port across each major platform means a considerable improvement in the operation of your organization. The ability to place resources on different projects and not have to worry about skillsets and whether a developer can write Swift, Objective-C, Kotlin, or Java is a huge relief.

Nearly 67% of all developers use JavaScript already, so it’s an easy sell for using React Native to improve operational efficiency across the enterprise.

There are many ways React Native saves organizations time and money. Obviously, the “one code for all” is a huge advantage as it cuts down on the learning curve and the number of hands on deck required for developing an application. It’s also open source and has a robust and growing community of ready-made components and support.

In fact, something like 95% of the React Native codebase is shared between iOS and Android. These are just some of the many reasons why React Native leads to significant improvements in ROI over hiring native developers.

As good as React Native is for all-around performance, cost savings, and portability, a few use cases will stand out that require a pure native look and feel. These are going to be the high-end enterprises, such as Airbnb and Uber that have money to spend on super-polishing their native application.

For the “rest of us,” which means 90%-95% of the business use cases, React Native will provide your organization with a highly engaging enterprise application. In other words, the reasons for not using React Native are going to be negligible.

In terms of cost-savings, increased efficiencies, and the overall native look and feel that users experience, React Native is a no-brainer!

Yes, not every app should be built with React Native. Here are some reasons to go full native:

You’re creating something with complex animations and interactions, like an interactive game.

You’re building something that’s CPU intensive, like editing photos. In that case, you could either go full native or write the complex logic in native and bridge it to React Native.

You’re creating something out-of-the-box with unconventional UI patterns. Native might be a better choice in that case.

For CTO’s, quickly getting the right products to market is all that matters. As a “learn once, write everywhere” framework, React Native cuts down enormously on the cycles required to develop and deploy user-friendly and engaging products to market. React Native is arguably one of the biggest breakthroughs in mobile application development in recent years.

, this cross-compatible platform has transformed the way companies develop enterprise-grade applications—with less learning curves, shorter development cycles, faster releases, and overall cost savings.

We’ve been using React Native since I founded the company and aren’t looking back anytime soon. You can learn more about our React Native development services 

P.S. If you’re trying to decide between React Native and other cross-platform mobile frameworks, 

Why CTOs Should Choose React Native as Their Mobile Development Platform

Nearly all business executives today believe that Agile is critical to business success. If you’re launching a digital product (or considering one) then you won’t want to miss this recent podcast on Enterprise Radio where our CEO Rob Volk discusses why more and more companies are choosing Agile and React Native to build innovative products. 

The Agile and Mobile Revolution with Rob Volk, Founder of Foxbox Digital

In July 2017, Forbes interviewed more than 500 senior executives from around the world, and 92% said they believe organizational agility is critical to business success. If you’re considering a digital product or roadmap, or are just curious about what Agile is and how it helps companies grow, then this podcast is a must-listen.

I sit down with Eric Dye of Enterprise Radio

 to talk about Agile and why more and more companies are adopting this transformative approach to mobile development.

Please listen to the podcast in the link above, and for those that like to browse ahead, check out our show notes.

1:49 — My goal in building Foxbox Digital was to help large companies build with the agility of a startup while using modern development practices.

2:15 — React Native is a really phenomenal cross-platform mobile framework and the reason I like it is because I think it's well-suited to 90% of the apps out there. It's something that gives you the benefits of cross-platform so you have one code base and one team building for both iOS and Android.

3:47 — Typically, the reason companies decide they need Agile is because they’re experiencing some symptoms, such as late project delivery or reliability issues that come up during the integration phase (or worse, when the product has gone live).

4:53 — In order for Agile to work for everyone, the entire organization has to be bought in. This means the UX folks, the product owners, the developers, DevOps, etc. must be brought out of their silos—so everyone is bought into Agile from the start.

5:36 — What doesn’t work with Agile is to just choose one group, say your UX team, to adopt this approach. It must be all or nothing.

6:10 — In order to do real work, you must have an extended period of time of uninterrupted focus. That's when you can really get your “deep work” done—things that matter.

6:40 — So Slack is a perfect avenue for people to interrupt you. It's become part of our culture for people to expect immediate responses. But that's unfair to you because that prevents you from doing actual work.

Many stakeholder ideas sound amazing in the moment, but deciding which ones move forward and which ones do not can give you a panic attack. Here are a few ways we keep quality ideation without being overwhelmed by quantity.

How I Prioritize Product Features From the CEO & Founder

A Simple Way to Prioritize Product Features

It was like clockwork. The CEO would message me daily, if not hourly, on new feature requests, slightly changing product direction each time. He messaged me on every communication channel you can think of: Slack, iMessage, WhatsApp, and email. Whenever it was the most convenient for him, regardless of time of day, he would send me these requests.

These emails contained not only vague future ideas, but small tweaks and non-critical bug fixes, etc. Essentially, anything that came up mid-sprint, he would send me a quick note with his ideas.

A big reason why I enjoyed working with him was his excitement about the product we were building, and he was constantly thinking of new ideas. However, that came at a cost. I was drowning in new things to build, and I didn’t know how to focus these requests.

I appreciated his willingness to share his ideas, but at the same time I had to make sure we were building the right things. I wasn’t necessarily in a position to say no to these new features, even when I was only halfway done with the features we started weeks prior. I actually did care about what he wanted to build, I just didn’t think many of these features were the right decision.

I needed to ruthlessly prioritize our feature requests.

 But, again, who was I to decide what feature was right or not? So, I thought of something to help me alleviate this pain.

After a few panic attacks, I created what I called the inbox system. This was a place in our project management board where I collected all of his, and the team’s, ideas. It gave me a chance to say, “Great idea! Let’s discuss later.” He knows that his idea isn’t lost, and I don’t feel the pressure to act immediately.

In the next sprint planning meeting, we would go through all of these ideas, weigh them against all of the other issues (i.e. features, bugs, cards) in the backlog, and prioritize the things that will have the biggest impact towards achieving our company’s objectives.

The inbox system aims to solve the problem of changing the plan mid-sprint and allows you to slow down and consider your next steps. You don't want a reactionary engineering team where the latest ideas from the stakeholders are implemented over things that have been planned for weeks.

CEO sends feature request (and wants it built ASAP).

Acknowledge her feature idea and document the request in your project management board (AKA, the “inbox”) before committing to building the idea.

During the sprint review meeting, instead of asking the validity of the idea ad nauseum, discuss the priority of this request compared to everything else that needs to be built or fixed.

It was a small tweak, but it made a substantial impact. I was heard. He was heard. And together, we made the best decision for the product and the company.

Some Features Just Aren't Worth Building, Regardless of How Genius It Is

Every feature can certainly not be a winner.

This isn’t 3rd grade where everyone gets a participation trophy and feels like a winner at the end of the soccer match.

Implementing the wrong feature can significantly impact the trajectory and traction of your app. Not just because users don’t like it, but for simply how much effort and time it took to complete.

As a Product Manager or Project Manager, you’ll get a lot of input from your stakeholders. For us, it’s our clients. For businesses, it could be your CEO or boss. It used to give me anxiety when I heard all these lofty feature requests: I felt like I needed to implement all of the ideas my CEO threw at me over email, text, or Slack.

Many ideas sound amazing in the moment, but the luster wears off quickly. If it’s still a great idea during the next sprint planning, then consider implementing it. If not, then discard it—that’s okay to do, it’s part of innovation. All ideas can’t be winners!

Home Chef partnered with Foxbox Digital to rebuild their mobile app with React Native and help them increase ratings and conversions.

How We Increased HomeChef's App Ratings

Home Chef, a subsidiary of Kroger, is the third largest meal kit company in the U.S. As Home Chef was scaling their business, and providing new offerings to their growing customer base, they were looking for a modern framework with extensibility to support their new service offerings. They brought in Foxbox Digital to rebuild their mobile app with 

, a modern cross-platform app framework, to help them achieve their ambitious goals.

Through our engagement with Home Chef, we developed and published iOS and Android apps using React Native. This helped them significantly increase app store ratings, meal kit conversions, and user engagement rates.

We focused on building a great experience from the ground-up

We knew that re-platforming to React Native was only one part of the solution. We worked closely with the CTO & Head of Product to deliver an experience that delighted their customers.

Here are three of the core activities we focused on:

 - We provided early architectural recommendations based on their future technical and business goals. This included a revised roadmap that better fit their goals to maximize customer impact.

 - We seamlessly collaborated with the UX team to ensure the app was instantly responsive to the end user.

 - Customers added their first item to the shopping cart 20% faster than with the previous app.

Foxbox Digital’s deep technical knowledge of React Native helped us move quickly through technical roadblocks.

 In early stages of the development, they guided us through architecture decision and foresaw many of the issues we would run into with our current development setup. If you’re looking for React Native developers, I can’t recommend them enough. 

With thousands of paying customers on the platform already, and owned by a large subsidiary, speed-to-market is often not feasible. Our deep knowledge of React Native and our philosophy of tight product and engineering coordination allowed us to build the new iOS and Android application 

Here’s a breakdown of how we were able to move so fast.

 - Our engineering team is focused on the React Native platform. This allows us to provide deeper recommendations and build a modern architecture best suited for React Native.

Strong Relationships and Coordination With Engineering, Product, and Design

 - We know that developing an application isn’t just a list of requirements. We start every project by determining the specific goals of each team and work closely with each stakeholder to build the best product possible.

- We were instrumental through the beta testing phase ensuring a fast feedback loop from their most valuable customers, prior to launch. We quickly iterated to implement the feedback, which led to a successful launch.

I think the app is easy to use as well as navigate.

 I’ve tried other meal services and this was the best! 

We enabled them to build better features based on data

Prior to engaging with us, Home Chef was having a difficult time experimenting with mobile features. Here’s how we resolved that.

Embedded Customer Behavior Data Analytics

 - We knew that to improve the experience of the app, we had to collect data at every major customer interaction. We worked directly with their executive marketing team to implement Amplitude to track key user data points and define the events they needed to track.

 - We implemented A/B Multivariate testing functionality. Now, instead of guessing which functionality makes the customer happier, it is simple to deploy A/B Testing for both iOS and Android.

 - With React Native and Expo, they're able to publish weekly updates with the push of a button. Allows them to collect fast feedback from customers.

Simply put, Foxbox Digital was amazing from start to finish.

 Their maturity in understanding our product, engineering, design, and business needs was exactly what we needed. They were proactive and intentional in every decision they brought forward. This product is core to our experience and we couldn’t have imagined a better partner than Foxbox Digital. 

- Julian Rockwood, Head of Consumer Product, Home Chef.

If you enjoyed this case study and you’re looking for a React Native development agency that can help you the same way we helped Home Chef, feel free to 

How We Helped Home Chef, the Kroger-Owned Meal Kit Delivery Service, Increase App Store Ratings and Meal Kit Conversions

When you set out to build a product, there's a disconnect between what you think people need and what they actually need.

How to Define your Minimum Viable Product (MVP)

When you set out to build a product, whether it's a mobile app, website, or a physical product, you'll envision how people will use your product and what qualities they need of your product. What often happens when building products is 

If you take the Lean Startup approach to designing and building your first product, 

, you're more likely to build exactly what your users need, and eliminate waste from building features they don't need.

), and when you're building a startup company, you have real constraints with how much money and time you have to build something. These constraints force you to be smart about what you spend time building; any wasted effort could put you out of business.

The classic model to create a product is called Waterfall, and it doesn't work. With Waterfall, you start by defining all requirements, then design the product, then build it then launch it. This sounds completely logical, but problems arise if requirements change at any point in the process. 

 When this happens, your project goes way over budget and you blow past the deadline.

With a lean approach to building a product, the idea is you take the steps in Waterfall and repeat them many times over. You divide up the problem into several product phases, where each phase fully delivers on a set of objectives.

 objectives of your project. People start using your product early on in the development cycle, 

 People tell you what's working and what isn't, and you can respond by altering the product roadmap.

Think of it this way: if you set out to build a car to get people from here to there, you don't start by building a wheel. That doesn't get you to where you need to go. You could start by building a bike. From there you could build a scooter, then finally a car. At each phase of the project, people are able to use your product to achieve the main objective: transportation. They'll give you feedback along the way ("it's too slow!"), and you'll incorporate that feedback and iterate the product.

This process allows for changes in your product roadmap during active development. Changing requirements doesn't mean pushing back your delivery date - because the process accounts for change. After people use your MVP, you might decide to cut entire features, and improve other features that they actually use.

After the MVP, you'll continue iterating the product in mini releases - every week or so. The product takes shape, change by change, until you've achieved all of your objectives. The product is tested in realtime during active development, so at the end, 

you'll have confidence that you hit the mark.

At Foxbox Digital, we take a lean approach to building mobile apps. We tap into our entrepreneurial experience of building startup companies, and apply that experience to how we build products. We'll help you 

build your product with a lean, agile approach

At the end, you'll have a product that meets your objectives, has the features you need, and eliminates the features you don't actually need. 

This is how you build a product that hits the mark and deliver it on time.

After you've designed and built your mobile app, you have to monitor, maintain and support it for the life of the app.  What's involved?

The Total Cost of Running & Maintaining a Mobile App

After you've designed and built your mobile app, you have to monitor, maintain and support it for the life of the app. What's involved? There's a lot more effort than you might think.

Mobile apps usually need a server in order to operate, called an API. The API is responsible for storing and retrieving data. For example, when you create a new account as a user, the mobile app talks to the API to create that user.

At Foxbox Digital, we host our client's APIs on 

. This is a server farm that has redundancy built in on every level, so that if any single component fails, your app still runs. If the API server goes down, there are more just like it that continue to operate. If the database server goes down, there's a failover server that takes over automatically. Even if the power goes out, there's a backup generator to keep the servers running!

This type of hosting is called high availability, because your app is available as close to 100% of the time as possible. Building and configuring this type of high availability infrastructure is not a trivial task, but it's critical to ensure your app always works.

If your app goes down for any reason, the engineering team needs to know about it. At Foxbox Digital, we have a monitoring system that constantly checks to ensure the servers and the API is running 24x7. If anything happens, 

it immediately notifies our engineering team

. When this happens, we respond to the problem and take action.

It's common for errors to happen when users interact with your app in a way that you didn't anticipate. We call these bugs, and usually they are small, but sometimes they are serious.

Both the mobile app and the API needs error monitoring to ensure that when an error happens, an alert is triggered and the tech team is notified. At Foxbox Digital, 

we actively monitor our clients' apps and the API and trigger alerts when an error occurs

. We respond quickly to fix the bugs in order of urgency.

Here's a view of the error dashboard of one of our apps. The tool is called Sentry and it notifies the team on Slack, our internal chat tool. The first one is happening frequently, and the engineering team is working on a fix as we speak.

You need your API to be fast so that when users interact with your app, the experience is as fast as possible. This is why we actively monitor the performance of your API. We're able to identify performance issues in any part of the app and we use tools to give us detailed insights into what's happening.

For example, if you have a surge of users, we'll scale out your servers to support the added usage. Or if just one component, like searching, is really slow, we'll dive in and figure out why so we can fix it.

We don't compromise on application performance.

Upgrade App to Support Latest iOS & Android

Every time Apple and Google releases a new operating system, apps need to make changes to support the latest specifications. If you don't, you risk Apple or Google pulling your app from the App Store or Google Play. These upgrades can take a lot of time and are sometimes complicated.

Apps are built by using a set of frameworks, tools, and reusable components. On occasion a security update is released for one of these components, and the application developer needs to upgrade the app and apply the security fixes. Without regularly patching your app and API, the security of your app and data are compromised, and that is unacceptable.

At Foxbox Digital we regularly upgrade all of our clients' apps to apply the latest security upgrades and bug fixes. This keeps our apps running fast, smooth, and secure. As soon as we patch each app, we release it to the App Store and Google Play.

It's normal for an app to have some bugs - even the most well-tested apps do. When a bug is identified from our error alerting system, we respond quickly to fix it.

At Foxbox Digital, you have a direct line to reach out to our support team. If you need to make changes to your app, or if you just need help with something, we're here for you, when you need us. Our clients have 

At Foxbox Digital, we handle the hosting, monitoring, maintenance, bug fixes for you. We also specialize in 

. You'll also have unlimited access to our premium support. You'll have the 

 of knowing that your app is running smoothly, forever. And if anything happens, you know that someone is actively monitoring it and working on a fix.

We're your trusted partner, for the life of your app. 

Let's compare the best cross-platform app frameworks (React Native, Ionic, Cordova, PhoneGap) to develop for iOS and Android at the same time.

Comparing Ionic vs Cordova vs PhoneGap vs React Native

I set out to build an app for myself called 

 (it’s the insider’s guide to the city).

I looked into the cross-platform frameworks available so I could build it for both iOS 

 — Apps created with these frameworks are basically websites created with HTML, CSS, & Javascript, smushed into app form. It 

 like an app. When you interact with the app, it feels slightly sluggish and not responsive.

 — This framework take an entirely different approach to hybrid cross-platform apps, and uses native UI elements, powered by Javascript. You write your app in Javascript, then 

 works some magic and turns the user interface into 

. This means that when you touch & feel your app, it 

React Native apps are snappy, responsive, and a joy to use.

. I argue that it takes less than half the time to build an app compared to full native apps, because not only do you have to build an app once instead of twice, it’s just faster to build the first app period.

Under the hood, React Native uses Javascript to run the business logic, for example handling a button click or fetching data from a server.

Technically it does this with a headless browser. Because of this if you don’t program the app right, you may see some slowness.

There are ways in which to program the app however that eliminate this problem and the user will never know the difference between a pure native app and a React Native app.

Companies including Instagram, Facebook (parts of their app), Bloomberg, & Skype (

From a technical perspective, it wins some points because it uses technology many developers already know: Javascript and React. Web developers don’t have to learn an entirely new language (Objective C, Swift, or Java); they just apply the skills they already have to a new form factor, mobile.

So how did the app come out? Speakeasy is snappy, responsive, and I bet you couldn’t tell it’s a React Native app.

React Native strikes the perfect balance in creating cross-platform apps because it’s super fast to build them and the apps look 

 feel like native mobile apps. The end result is a polished, snappy and responsive mobile app.

You write the apps in Javascript, which is one of the most popular programming languages and use the React framework which is a revolutionary and brilliant framework.

React Native isn’t great for games or anything with complex animations. But for most apps that simply display and let you edit data, it’s a great choice.

React Native is a great choice for 80% of the apps out there.

I envisioned a mobile app development company that takes a radically different approach to building apps.

mobile app development

9 posts tagged with “mobile app development”