Often, yes. If your application is already web-based, its screens can usually be redesigned to adapt to phones and tablets while the database and business logic stay as they are. If it is a desktop program, it has to become a web application first. A separate app in the app stores is needed only when you want things a browser cannot do well, such as heavy offline use.

Responsive web screens. The same application rearranges itself to fit the screen it is on. One system to build and maintain, nothing to install, and it works on any device with a browser. This is the right answer for most business applications.
A mobile web front end for part of the system. Only the tasks people do away from a desk, such as approvals, lookups, time entry or job updates, are rebuilt for small screens. The full system stays as it is for office use.
A native or cross-platform app. Installed from the app stores. Worth it when staff must work for long periods with no signal, or when you need close use of the camera, GPS or scanner.
The database, the business rules and the reports normally stay. What changes is the screen layer. How much work that is depends on the age of the application: a fairly modern web application can often be adapted screen by screen, while an old one may need its screens rebuilt on current technology. Either way, you are not rebuilding the whole system.

The next step is a short, no-pressure conversation. Book a call with Lance Keene or use the form on this page.
Usually not. A responsive web application works on phones and tablets through the browser, with nothing to install and one system to maintain. A store app is worth it mainly for heavy offline use or deep use of device features.
Yes, where needed. Screens can be built to store entries on the device and send them when a connection returns.
Usually not. The database and business logic are normally kept. The screens are adapted or rebuilt.
Yes. A responsive web application works on both, and on tablets and PCs.
It can be. Each user signs in with their own account over an encrypted connection, and nothing sensitive needs to be stored on the device.
This page is part of Legacy system paralysis.
Keene Systems has built custom business software since 1987. We are veteran-owned, and our 50+ professionals have delivered systems for companies including Hormel, McCormick, IBM and Dartmouth-Hitchcock. See our client list.
Lance Keene takes the first call himself. Book a call with Lance Keene.
Tell us what your team needs on a phone