Product planning and prototypes
Define a useful first release and test important screens before full development.
Our services / 02
Give customers a better way to book, manage an account or get work done away from a desk. We develop iOS, Android and cross-platform apps from product planning through release and support.

Where we can help
Define a useful first release and test important screens before full development.
Choose an approach for your audience, requirements and long-term maintenance.
Make recurring tasks easier for customers and people working in the field.
Build the services, access controls and staff tools behind the app.
Use camera, location, notifications and offline behavior where they serve a purpose.
Work through beta feedback, store preparation and post-release care.
Make it easier to book a service, manage an account, submit a request or get work done away from a desk. Faith Forge Labs develops iOS, Android and cross-platform applications, from early product planning through design, development, testing and preparation for launch.
You may have an idea that needs a first working version. You may have a prototype that looks promising but needs the services and administration behind it. Or you may already have an app, with a growing list of problems between where it is today and where you need it to be.
We help you work out what the product needs, what belongs in the next release and what it will take to keep it running. You can start with the situation you are trying to improve. You do not need a finished technical brief to get started.
Discuss your app with Faith Forge Labs
Product planning and prototypes
Turn an idea into a defined first release. Explore the important screens and interactions, test the proposed experience and identify questions that need answering before full development.
iOS, Android and cross-platform development
Develop for the devices your audience uses. Choose an approach that suits the app's requirements, your budget and the people who will maintain it.
Customer experiences and business tools
Create useful ways for people to complete recurring tasks, whether they are customers managing a service or staff collecting information away from the office.
Data, accounts and administration
Connect the app to the services behind it, with the account access, staff tools and privacy controls needed to operate the product.
Device features and communication
Plan camera access, location, notifications and offline behaviour where they serve a clear purpose, with feasibility checks for specialist requirements.
Testing, launch preparation and support
Work through device testing, beta feedback and store preparation. Agree what happens after release, including maintenance and future development.
A customer sends a photograph to your office, calls to check that it arrived, then calls again because nobody has confirmed the appointment. Your team has the information somewhere. The customer cannot see what happens next.
An app could bring those steps together. But the value depends on the whole task working: the photograph reaches the right person, the booking appears in the right system, and the customer receives an accurate update. A new screen in front of the same disconnected process may leave the original problem intact.
That is where product planning begins. Who needs the app? What are they doing today? Which part is slow, confusing or dependent on someone else answering a call? We help establish a clear purpose before deciding how many features to include.
Frequency matters too. A customer who uses a service once a year may prefer a good mobile website. A person managing bookings, membership or field work every week may have a stronger reason to install an app. The investment should follow that use, including how people will discover the app and return to it.
A first release needs a complete experience, even if it serves a narrow purpose. If customers can make appointments but staff cannot change them, the product is unfinished in a way that matters immediately.
We help distinguish the work needed for that first useful experience from additions that can follow. For a booking product, that might mean availability, confirmation, changes and cancellation before referrals or a rewards scheme. It also means deciding what staff will handle manually and whether that workload is realistic.
A prototype lets you examine the proposed experience before every connection behind it exists. Put it in front of someone who has not been sitting in the planning meetings. Can they tell what to do? Do they understand what happened after submitting a request? What information do they look for next?
Some questions need working software rather than clickable screens. An uncertain device integration or offline requirement may deserve a small technical test first. Discovering a limitation at that stage is useful information for the budget and the design.
There is no useful answer to this question without knowing the product. The decision affects development, testing and maintenance, so it deserves more than a preference for one technology.
Native development uses the tools and conventions of a particular platform. It can be appropriate when the app depends closely on that platform's capabilities or needs a distinctly platform-specific experience. Supporting both iOS and Android then means planning for the work each requires.
A cross-platform approach can allow substantial parts of the app to be shared. It still needs testing on both platforms, and some features require platform-specific work. A promise to write everything once and forget those differences would be a poor basis for a project estimate.
Mobile web may be the better starting point when access through a link matters more than installation, or the product largely presents information and straightforward transactions. Device needs and browser constraints still have to be checked against the intended experience.
Faith Forge Labs supports iOS, Android and cross-platform implementation. We look at audience devices, existing software, required connections and long-term maintenance before recommending an approach. Tablets, specialist hardware or unusual background behaviour should be raised early so their requirements can be assessed.
An office review can make a form seem straightforward. Outside, the same person may be balancing a bag, holding the phone in one hand and trying to read the screen in bright light. They may switch to another app to find an address, then return expecting their work to remain.
Interaction design accounts for those moments. It includes the order of information, how much typing is necessary, what the keyboard covers and whether an error explains how to recover. A message saying something went wrong is of little help if the person cannot tell whether to try again.
Accessibility belongs in these decisions. Text needs room to grow. Controls need understandable labels and usable touch targets. Important meaning should not depend entirely on colour. A person using a screen reader needs to reach the same essential actions as someone using the touchscreen visually.
The accessibility requirements and testing appropriate to your audience should be agreed as part of the project. If you need a formal audit or a particular compliance assessment, that is a defined piece of work to arrange, rather than a promise attached to the word accessible.
Requiring an account is a decision, not an automatic opening screen. Someone browsing public information may have no reason to register. Someone viewing private records or managing an ongoing service needs an appropriate way to establish who they are.
Sign-in also brings recovery, expired sessions and changing devices. If a customer loses access to an email address, your support team needs an agreed route for handling that problem. An internal app may need to distinguish what a team member, supervisor and administrator can see or change.
We help define those roles alongside the account experience. Access restrictions must be enforced by the services holding the information; simply hiding a button does not settle who is allowed to perform the action.
Shared devices need particular attention. What remains visible when one employee signs out and another signs in? Can a former team member still access saved information? If your organisation uses an existing identity provider, its requirements and available connections need review before the sign-in approach is settled.
A camera can save a technician from typing a long description of damaged equipment. Location can help someone choose a nearby branch. These features become valuable when they shorten a task the person already understands.
They also need a workable alternative or explanation when access is unavailable. A user may refuse a permission, revoke it later or use a device without the expected capability. Asking for access in the context of the relevant action makes the reason easier to understand.
Background location, continuous recording and connections to external hardware raise further questions about device support, battery use, platform restrictions and user expectations. They need their own feasibility review. We check the hardware and platform requirements before including those connections in a proposal.
For your app, we establish which device features are necessary, what happens without them and what information is retained afterward. That keeps the feature connected to its purpose instead of becoming another permission requested at launch.
Offline support has several meanings. Displaying a previously downloaded job sheet is different from editing it offline. Taking a photograph and saving it for later upload is different again from confirming a booking against live availability.
Consider a technician completing an inspection in a basement. The app may need to keep answers and photographs on the device, show that they are waiting to send, and submit them when a connection returns. The person should be able to tell the difference between work saved on the phone and work received by the office.
Then consider what happens if someone at the office changes the same record in the meantime. The product needs a decision about those conflicting changes. Silently replacing one person's work with another's may be unacceptable.
We help define offline behaviour action by action, including saved drafts, retrying submissions and avoiding duplicate requests. Some actions may remain unavailable until the device reconnects. The aim is to give people an understandable experience under weak connectivity, with clear limits on what has and has not been completed.
A customer-facing app creates work for the organisation behind it. Someone needs to answer a request, correct a record, change availability or understand why a notification did not go out. Without suitable administration tools, those ordinary tasks can become requests to a developer.
Faith Forge Labs' mobile work can include the behind-the-scenes services and administration that support the app. We help determine which staff actions are needed for launch, who should be allowed to perform them and where a record of changes is important.
Connecting existing systems requires more than knowing their names. We need to establish what information each system holds, which one controls the current version and what access is available. Documentation, a test environment and cooperation from the system owner can all affect progress.
External services also have limits, charges and outages. If a booking provider stops responding, the app needs to explain whether a request is pending or has failed. Staff need a way to investigate and resolve it. These connections should be assessed early because their constraints can change both the user experience and the development work.
A useful notification answers a question the customer cares about: the appointment has changed, a submission needs attention, or an order is ready. Sending more messages does not automatically make an app more useful.
Notification planning includes who receives each message, what triggers it and where a tap should take the person. A message that opens a generic home screen can force them to search for the very information it promised. If the underlying situation changes, an older message must not leave them acting on stale instructions.
Preferences matter, as does the distinction between service updates and promotional communication. The app also needs a suitable way to show important information when notifications are disabled or a device does not receive a message promptly.
We can include notification services and controls in the engagement. Where timing is safety-critical or commercially essential, the communication requirements need a specific assessment; ordinary push notifications should not be assumed to provide guaranteed delivery.
If the app will take money, that requirement belongs in the first conversation. Selling a physical service, unlocking digital content and managing an ongoing subscription can involve different payment arrangements and store requirements. Those requirements need checking for the product, markets and distribution approach being proposed.
The customer experience extends beyond a successful payment. What happens when an attempt fails, a renewal does not go through or a person changes devices? Who handles a refund? When should access begin or end? If the transaction succeeds but the app loses its connection, how will the person find out what happened?
Payment and subscription work should be assessed and included explicitly where required. We would need to review the provider, account ownership, available integrations and operational responsibilities before confirming an approach. The aim is for the transaction, the customer's access and your team's records to agree, including when something needs to be corrected.
Every piece of information collected by an app creates a responsibility. Before asking for an address, photograph or precise location, establish why the product needs it and who will use it. Collecting information because it might become useful later makes the product harder to explain and administer.
Privacy controls can include what people choose to share, who can access it and what happens when an account closes. Retention, deletion and information passed to outside services also need decisions. Analytics and support tools should be considered alongside the app itself, since they may receive information about its use.
Security work should reflect the sensitivity of the information and the consequences of misuse. Account protection, access restrictions, safe storage and appropriate handling of credentials all belong in planning. Higher-risk products may need independent security testing or specialist advice beyond the development engagement.
We can help implement agreed controls. Legal requirements, regulated uses and formal compliance assessments should be reviewed with the appropriate advisers; a development proposal should make those responsibilities explicit.
A test plan should follow what people need to accomplish. Can a new customer register, complete the intended task and find the result later? Can staff see it and do their part? Can someone recover after entering the wrong information?
Device testing adds the conditions that are easy to overlook on a development machine: smaller screens, different operating-system versions, limited storage, interrupted uploads and a slow connection. Accessibility testing should include the important journeys, rather than stopping at a visual inspection of individual screens.
Beta distribution gives selected users an opportunity to try the product before wider release. Their questions can expose unclear wording or missing information as readily as a software fault. Your staff should participate too, using the administration tools to work through realistic requests.
No test plan establishes that software can never fail. What it can do is make the intended behaviour explicit, check the agreed range of devices and conditions, and leave you with a clear view of known issues before deciding to release.
A finished development build is one part of getting an app into people's hands. Distribution also needs the right accounts, access, descriptions, screenshots, support information and disclosures. Reviewers may need a way to access features that sit behind a sign-in.
We can help with beta distribution and store preparation, with responsibilities agreed for the materials and accounts involved. Store requirements should be checked early, particularly when the product includes payments, sensitive information or unusual device behaviour.
Submission and public availability are different milestones. Review can raise questions or require changes, and that dependency belongs in the launch schedule. Development work alone cannot guarantee an approval or a particular review date.
Launch planning should also cover the business response. Who watches for problems? How can customers ask for help? Is a limited initial audience appropriate? If a problem appears, who can make the decision to pause promotion or prepare a correction?
An existing app may have useful foundations even when its current experience is frustrating. Before proposing replacement, the code, design, service connections and reported problems need a proper look. The next step might be a targeted repair, a revised interaction or a larger change.
Access matters. Source code, build instructions, store accounts and information about third-party services help establish what can be changed. Missing access or unclear rights can delay work before development begins.
Changes also have to account for people already using the product. Their saved information and older app versions do not disappear when a new version is submitted. Any plan involving data changes or replacement services needs to consider how existing users move across.
If you have an app that needs attention, bring the current build and the problems you can describe. An initial assessment can help establish what is worth retaining and which changes need further investigation before a firm commitment.
The number of screens is only one part of an app's cost. Work also depends on account roles, administration, integrations, offline behaviour, device features, testing and the condition of anything being reused. Two apps with similar-looking screens can have very different requirements behind them.
An estimate should identify what is included, what remains uncertain and which decisions or access your team needs to provide. Where an important dependency is unproven, a focused investigation or prototype can make a later estimate more reliable.
Ongoing costs need their own view. Hosting, data storage, messaging, mapping or other vendors may charge separately from development. Distribution accounts, support and future updates also need provision. Usage assumptions matter when estimating those costs.
Ownership and handover should be written down. Agree who controls the source code, designs, store accounts, service accounts and credentials. Distinguish work created for the project from third-party software and licensed assets. The handover should cover the agreed access and information needed to run, maintain or transfer the product, with any continuing dependencies made clear.
After launch, the app operates alongside changing devices, operating systems and outside services. Bugs may emerge under conditions that were not encountered in testing. Customers will also ask for improvements, and those requests need to be separated from faults that affect existing functionality.
Support should define who receives reports, how issues are prioritised and what response arrangements have been agreed. Maintenance and new feature development may require different allowances. These are commercial decisions to settle before someone needs an urgent answer.
Analytics can help guide subsequent work when the measurements answer useful questions. Are people completing the main task? Where do they leave it? Which errors lead to support calls? That information is more actionable than a dashboard full of numbers with no decision attached.
Faith Forge Labs can include support and further development in the engagement. We will discuss what your team intends to manage and what help the product will need after its first release.
Tell us who it is for, what they need to do and what happens today. If you have designs, an existing build or systems the app must connect to, bring those too. A known budget, deadline or launch commitment helps us discuss realistic choices from the start.
We can help you decide whether the next useful step is a prototype, a focused first release or an assessment of the app you already have.
Discuss your mobile app project with Faith Forge Labs.
Let's begin
Tell us who it is for, what they need to do and what happens today. Bring designs, an existing build or systems it must connect to. A budget or deadline helps us discuss realistic choices.
Tell us about it ↗Email Faith Forge Labs ↗