Mobile app development
We build the product itself. That includes the screens a
person uses, the logic behind those screens, and the data
the app has to store or fetch. We write for phones and
tablets and we test on the kinds of devices people actually
own.
A typical build starts with a short list of jobs the app
must complete. We implement those jobs first. Extra features
wait until the core path works.
Publishing
Publishing is the work of getting a finished build into
people’s hands and keeping the listing accurate. We prepare
the release, write the store-facing copy that belongs to
that app, and handle the steps required to submit and update
it.
We do not treat “published” as a one-time event. If a build
is rejected, broken, or outdated, that is still our work.
Product and interface design
Before we write a lot of code, we decide what the app is
for. We sketch the main paths: open the app, finish the
task, leave. Labels, empty states, and errors are part of
that design, not decoration added later.
The goal is a product a stranger can use without a manual.
If a step needs a paragraph of explanation, we try to remove
the step.
Updates and support after launch
After an app is live, we keep a list of defects, small
improvements, and the next slice of product work. We ship
those as updates. We also answer product questions that
arrive at our work email.
Support for a given app is described in that app and on its
store listing. Company contact for this site remains
david@inbusinessinc.com.