More and more health care providers are using web and mobile applications to communicate with their patients. In 2016, for example, the American Hospital Association reported that 92% of their hospitals provided patients with access to their health data via patient portal applications. These portals offer significant benefits to patients, providers, and administrative teams.
So you want to build a mobile app. Should you choose native or hybrid mobile application development? Each choice has advantages depending on your projected use and time to market.
What is a hybrid mobile application?
Mobile apps generally fall into two categories, native and cross-platform or "hybrid". A native mobile application is just what it sounds like: it uses the SDK (Software Development Kit) and hardware features specific to a particular mobile operating system. Hybrid mobile applications also fall into two general categories, hybrid HTML5 apps and native cross-platform apps.
Salesforce User Adoption, Part II: Improving Salesforce User Adoption
Creating a great Salesforce app for your team is only part of the solution; the other part is getting your team to use the app. The best tool in the world is useless if it's not used! You've seen plenty of tips about signs your team has bought into using Salesforce. Your next step is improving Salesforce user adoption, and communication, training, and continuous refinement are the keys.
In a fast-paced, connected world, how can companies keep their clients engaged and satisfied? Even if your business model is selling fungible, disposable widgets, customers look for two-way conversations about their experiences. This is even more true for companies that provide professional services. Clients need to know you'll provide support when needed, yet live support can cause its own problems when resources are stretched thin. Creating a client portal creates a win-win situation for you and your clients.
People resist change, even when it's good. This is especially true when working routines and tools change. Field staffers are no exception; they're constantly on the go, so they need for their productivity tools to be seamless and easy. This is where well-designed mobile workforce apps can really help.
Writing software requirements should be easy, right? Right? Of course we know exactly what we need and can tell you exactly what the software should do.
Unfortunately, it's not always so easy. Writing software requirements well takes detailed, deep thought about business requirements. It also takes clear communication between the people who will use the software and the people who will write it.
It isn't always easy to translate between business-speak or industry-speak and developer-speak. This can cause costly confusion. Fortunately, there is a language called Gherkin to help bridge the gap.
So what makes a good set of software requirements, and how can we develop those requirements?
Is your software development team listening to you? Good project communication helps prevent costly rework and ensures that product owners and development teams understand each other.
We don't speak the same language, even if we're both speaking English.
We all know that feeling of frustration when we're trying to communicate and just not getting through. I spelled it all out in careful detail, and all I see are blank looks. Were they even paying attention? This is an important project! Is my software development team listening to me at all?
You may have heard software developers and project managers talk about "technical debt". This term has been around since the 1990s and is growing in popularity. But what is technical debt and why do people keep talking about it?
Now that your company has rolled out its shiny new CRM system, you’ll want to make sure your team is fully on board. How can you track Salesforce user adoption? What are the signs you don’t have full buy-in from your organization on using Salesforce?
Of course, there are many useful reports available in the Salesforce Adoption Dashboards. To get the most benefit from those dashboards and reports, you'll need to quantify your expectations. How should your team use the system?