Edinburgh asks for two kinds of app: finance products that survive infosec review, and festival builds that survive August. We develop both from our Manchester studio — secure, deadline-honest, remotely delivered.
Edinburgh's app briefs come from its two economies. The first is finance: banks, wealth managers and insurers headquartered in the city, plus the fintech cluster that grew up around them. These briefs are the most scrutinised we see anywhere — infosec questionnaires, procurement gates, accessibility requirements, and stakeholders who've been burned by vendors before. They reward process and punish shortcuts, which suits how we work.
The second economy is August. The Fringe, the International Festival, the Tattoo — a month when the city's population effectively doubles and every venue, promoter and tourism body wants an app. Festival briefs are the opposite of finance briefs: immovable deadlines, content that arrives late, and users who download the app standing outside a venue. We've learned to scope festival builds backwards from opening night and cut without sentimentality. Both economies get the same honesty: finance gets security architecture documented before code, festivals get a date we'll actually hit.
The briefs behind Edinburgh's two economies:
All of it through our custom mobile app development service — finance-grade process for finance briefs, festival-grade pragmatism for August briefs.
For finance briefs, the deliverable isn't just the app — it's the evidence. We document the security architecture before development: what data lives where, how it's encrypted, how authentication works, what happens on a rooted device. Your infosec team reviews the document, not a finished app they can only reject. That single process change saves more finance projects than any technology choice.
On the stack question: Flutter handles finance apps well — biometric authentication, secure storage and certificate pinning are mature, and we've shipped them. The honest deciding factor is usually maintenance: if your in-house team is native iOS and Android engineers who'll own the app after us, native avoids a handover tax. We ask who maintains it in year two at scoping, because that answer shapes year one. And for the August economy: start in spring. A Fringe app scoped in April ships in July; a Fringe app scoped in July ships never.
Apple reviews finance apps with extra attention, and the rejections are specific: vague privacy labels on apps that handle financial data, missing account-deletion paths (a regulatory requirement now), and onboarding flows that collect personal data before explaining why. We write the privacy labels, store copy and in-app disclosures as one truthful set before submission — because inconsistencies between them are what reviewers flag.
For festival apps the risk isn't scrutiny, it's timing: submit early, because a rejection two days before opening night has no recovery path. Our festival timeline builds in a two-week review buffer as standard, and we've never missed an August yet. Either way, the twice-yearly OS update cycle goes into the maintenance plan from day one — a banking app that breaks on a new iOS release is a trust event, not a bug. Our areas we cover hub lists every city we serve.
Indicative Edinburgh ranges — security documentation and deadline pressure shape the numbers:
Finance builds cost more because the evidence costs more: security documentation, accessibility testing, procurement support. We itemise every pound in the proposal, so your buying committee can see what each line defends.
Straight answers to what Edinburgh finance and festival teams ask us most.
Work backwards: the app should be in the stores by mid-July for an August Fringe, which means content freeze by late June and development starting no later than April for a focused build. Starting in July for an August launch is how festival apps die. Talk to us in spring and we will scope honestly against the date.
Certificate pinning, biometric authentication, no sensitive data in device storage or logs, jailbreak and root detection, and a backend that treats the app as untrusted. We document the security architecture so your infosec team can review it before a line of production code is written — not after.
Flutter handles finance apps well — biometric login, secure storage plugins and certificate pinning are all mature. We recommend native only when you need platform-specific security features or your in-house team is already native and will maintain the app. The honest driver is usually who maintains it after us, not the technology itself.
No — Google warns against ranking guarantees and we agree with Google. What we do guarantee: senior developers, a written scope and timeline, and reporting tied to downloads, activation and the outcomes the app was built for.
Remote-first with structure: scheduled standups, demo builds every one to two weeks, and a shared board with full visibility. Edinburgh is a short flight or a four-hour train when a kickoff in person matters. Most clients meet us once; the delivery rhythm carries the rest.
Dig deeper into the services and locations that pair with an Edinburgh build.
A scoping call covering security, procurement and your immovable dates — then a fixed, itemised proposal.
Talk to Visuosofts