MOBILE APPS
Mobile Apps Built Around the Real User Journey
Custom iOS, Android and cross-platform mobile applications for products, customer experiences, field workflows and business services that need to live on the devices people use every day.
Mobile apps are quoted by scope. Platform choice, backend requirements, user accounts, integrations, device features and release responsibilities are confirmed before development begins.
Mobile App Projects
- iOS applications
- Android applications
- Cross-platform apps
- Customer apps
- Service & booking apps
- Field / staff apps
- Companion apps
- Apps connected to existing web systems
Choose the Right Mobile Approach
The platform should follow the users, product requirements and long-term maintenance needs — not a preference for one technology before the project is understood.
iOS Apps
Applications designed for Apple devices when an iPhone/iPad-focused experience is appropriate.
Android Apps
Applications for Android users and device ecosystems where Android support is required.
Cross-Platform Apps
A shared mobile codebase may be appropriate when the product needs both major platforms with aligned functionality.
Companion Apps
Mobile experiences connected to an existing web app, SaaS product, service platform or business system.
What Can a Mobile App Be Used For?
A mobile app is most useful when the phone itself adds real value — frequent access, notifications, device features, field use or a dedicated product experience.
Customer Experience Apps
Give customers a dedicated mobile way to access services, accounts, requests, content or purchases.
Booking & Service Apps
Mobile flows for booking, intake, service requests, scheduling or customer coordination.
Field & Staff Apps
Tools for teams working away from a desk, including checklists, records, photos, tasks or status updates.
Marketplace / Commerce Apps
Mobile purchasing or marketplace experiences when the business model genuinely needs an app.
Content & Membership Apps
Mobile access to member content, communities, subscriptions or controlled resources.
Connected Business Apps
Mobile interfaces that connect to an existing API, SaaS, portal, database or business platform.
Common Mobile App Capabilities
Not every app needs every feature. The right feature set comes from the product workflow and user needs.
User Accounts
Login, profiles and account-specific experiences where the product requires them.
Push Notifications
Notification flows when they support the product rather than becoming unnecessary noise.
Camera & Media
Photo capture, uploads, media handling or document capture where required.
Location Features
Maps, addresses or location-aware workflows where appropriate and permitted.
Payments
Payment or purchase flows where the project and platform rules support them.
Offline / Sync Logic
Limited offline workflows or syncing where the use case genuinely needs it.
Backend & APIs
Connections to databases, web services, SaaS products or custom backends.
Analytics
Basic product analytics or event tracking where included in the agreed scope.
Admin Tools
A web-based admin or operations interface may be required to manage app users, content or records.
The App Is Only One Part of the Product
Many mobile apps also need backend services, APIs, databases, authentication, admin tools or integrations. These are included in the scope when the app depends on them.
- Mobile interface
- Backend / API
- Database
- User accounts
- Admin interface
- Notifications
- Third-party integrations
- Deployment and release responsibilities
A Focused First Release Can Be Smarter
If the product idea contains many future features, the first version can focus on the core user journey and must-have functionality.
This can be a practical way to validate a new app before investing in every possible feature, integration and edge case.
What We Pay Attention To
Mobile-First UX
Controls, spacing and flows should feel natural on smaller touch screens.
Clear Navigation
Users should always understand where they are and how to complete the main task.
State & Error Handling
Loading, empty, offline and error states need sensible behavior, not just happy-path screens.
Permission Awareness
Camera, location, notifications and device permissions should be requested only when relevant.
Backend Reliability
Accounts, data and syncing depend on predictable APIs and data handling.
Release Testing
Core flows are checked on the relevant devices/platforms before store submission or distribution.
What Determines the Mobile App Quote?
Two apps with the same number of screens can still be completely different projects. The quote follows the real workflows, platform requirements and technical scope.
Platforms
iOS only, Android only, both platforms or cross-platform requirements affect the project.
Screens & User Flows
The number and complexity of meaningful app journeys influence design and development effort.
Backend Requirements
APIs, databases, authentication and admin systems may be substantial parts of the app.
Device Features
Camera, location, notifications, files, sensors or other native capabilities can add complexity.
Integrations
Payments, maps, email, AI, CRM and other external services can change the scope.
Existing Systems & Data
Connecting to or replacing current web apps, APIs, databases or legacy systems may require additional work.
Scope First, Price Second
Before development begins, the written scope should define the supported platforms, core flows, agreed features, integrations, delivery responsibilities and quoted cost.
App Store & Google Play Accounts
For public mobile apps, the business normally needs its own Apple Developer and/or Google Play developer account so the app can ultimately be owned and managed under the correct organisation.
Account fees, identity checks, store policies and approval decisions are controlled by Apple and Google, not SiteLumo.
Submission Support
Where included in the project scope, SiteLumo can prepare the technical build and assist with normal submission steps, store assets or release configuration.
Store approval can never be guaranteed because review decisions remain with the platform operator.
Building a New App?
We can help define the core user journey, decide what belongs in the first release and build the product around a clear initial scope.
Already Have a Mobile App?
Existing apps may need fixes, interface improvements, new features, backend work, integrations, upgrades or a broader rebuild. We review the current app before recommending the right route.
A Written-First Mobile App Workflow
Requirements, screenshots, prototype views, progress updates, test builds, feedback and approvals can be handled asynchronously in writing. Meetings are optional.
01
Share the App Idea
Explain the users, core problem, platforms and what the app should help them accomplish.
02
Scope the Product
We define core flows, features, backend needs, integrations and release responsibilities.
03
Build in Stages
The agreed app and supporting systems are implemented with written progress updates.
04
Review & Test
Core flows, device behavior, permissions and integrations are checked before release.
05
Release & Improve
The agreed build is prepared for distribution or store submission, with later improvements handled separately.
Delivery Is Defined in the Scope
Repository access, build files, backend deployment, developer accounts, third-party services and handover expectations are confirmed according to the project.
Ongoing Mobile App Support
After release, SiteLumo can continue with fixes, maintenance, platform updates, new features, integrations and iterative improvements.
Mobile App Questions
How much does a mobile app cost?
Pricing depends on platforms, user flows, backend requirements, device features, integrations, data and release scope. We quote after clarifying the actual project.
Can you build for both iPhone and Android?
Yes. The right approach may be separate native apps or a cross-platform implementation depending on the product requirements.
Can you build the backend too?
Yes, where required. APIs, databases, authentication, admin tools and other backend services can be included in the project scope.
Can the app send push notifications?
Yes, where notifications are appropriate to the product and supported by the chosen platform setup.
Can you add payments or subscriptions?
Potentially. Payment and subscription flows must follow the relevant app-store and payment-provider rules, so they are scoped according to the business model.
Will you publish the app to the App Store or Google Play?
Submission assistance can be included in the scope. The business normally needs its own developer accounts, and final approval is controlled by Apple or Google.
Can you improve an existing app?
Yes, after reviewing the current codebase, backend, dependencies and existing issues. The right path may be targeted improvements or a broader rebuild.
Do I need a complete technical specification before contacting you?
No. Start with the users, problem, core journey, target platforms and must-have features. We can identify the missing questions before the scope is confirmed.
Do we need meetings?
No. SiteLumo uses a written-first workflow. Meetings are optional.
What should I send for a quote?
Describe the users, core app journey, target platforms, must-have features, any existing backend or software, required integrations and examples or screenshots that help explain the idea.
Have a Mobile App Idea?
Tell us who will use it, what they need to accomplish, which platforms matter and what systems already exist. We’ll reply in writing with the next questions needed to define the scope.