Mobile work wins on
publicly checkable scale
— not framework proficiency.
Mobile, iOS, and Android engineers are endorsed on the UK Global Talent visa's digital technology route via Tech Nation, the same body that assesses software engineers. The cohort is distinct in one structural way that decides most applications: the strongest evidence is publicly verifiable — apps you led on the App Store or Google Play with download or MAU figures anyone can look up, App Store / Play editorial features, Apple Design Awards or Google Play Best-of recognition, accepted Swift Evolution proposals, authorship of a widely-installed mobile library — while the work many mobile engineers are proudest of (a company's internal enterprise app, an unreleased rewrite, a high-quality codebase only colleagues see) is invisible to the panel. The applicants who clear the bar lead with a public, attributable app and its real scale numbers. Proficiency in Swift, Kotlin, SwiftUI, Jetpack Compose, Flutter, or React Native is competence, not external standing — treating a framework you are good at as recognition is the single most common mistake in this field.
Exceptional Promise fits senior mobile ICs (roughly 5–8 years) who led a high-scale shipped app and are building an external footprint — a first conference talk, a growing open-source library, a Play / App Store feature. Exceptional Talent fits principal and staff mobile engineers behind very-high-scale apps (tens of millions of users), authors of widely-installed mobile libraries, engineers with accepted framework proposals (Swift Evolution, Kotlin, Jetpack Compose), and named-conference speakers (droidcon, try! Swift, SwiftConf, KotlinConf, App.js, Chain React). Applying for Talent on an internal-only app the panel cannot find on a store is the dominant refusal pattern for this role.
Last updated ·
For a mobile engineer, the answer is usually clear.
For mobile, iOS, and Android engineers the route is almost always Tech Nation under the digital technology pillar — the body designated to assess product-engineering and platform work. The tier choice is the substantive decision. The defining failure mode for this role is presenting framework proficiency or an unverifiable internal app as recognition. Being excellent at Swift, Kotlin, or Flutter, or maintaining your employer's internal app, is real work, but the panel cannot verify it and it is not external recognition. Convert your work into a public, attributable artefact — an app on a store with checkable scale, an accepted framework proposal, a widely-installed library, a named-conference talk — or apply for Promise.
Tech Nation's digital technology route is purpose-built for product-engineering work. Both tiers see volume; the choice depends on whether your record shows current external recognition (Talent) or trajectory toward it (Promise).
Which criteria mobile / iOS / Android engineers actually win.
Innovation
Mobile engineers win on innovation with a concrete, externally-visible artefact: a shipped app you led that introduced a new capability or pattern at scale, a novel on-device technique (an offline-sync architecture, an on-device ML feature, a performance or battery breakthrough) that the app demonstrably ships, or an open-source mobile library you authored that others install — a networking, image-loading, dependency-injection, or UI library on CocoaPods / Swift Package Manager / Maven Central / npm. Internal-only apps are hard to evidence unless they are on a public store and attributable to you — the panel needs an external object to verify the claim.
Recognition
This is the criterion this cohort most often mis-evidences. The patterns that win: App Store / Google Play editorial features (App of the Day, an Editors' Choice slot), Apple Design Awards or Google Play 'Best of' recognition, accepted talks at named mobile conferences (droidcon, try! Swift, SwiftConf, KotlinConf, App.js, Chain React, FlutterConf), accepted framework proposals (a merged Swift Evolution proposal, a credited Kotlin / Jetpack Compose / React Native / Flutter contribution), and authorship of a widely-installed open-source library with real install counts. Being proficient in a framework, holding a vendor certification, or shipping a polished internal app are not external recognition — proficiency corroborates competence, not standing among peers outside your employer.
Significant contribution to UK digital economy
The mandatory criterion — every applicant must satisfy it. For mobile engineers this is usually evidenced by a coherent narrative across your other criteria plus your personal statement: 'I lead mobile engineering in Y sub-sector, here is the app and its publicly checkable scale, and the third-party attestation that confirms my role'. The panel assesses this holistically — a single coherent story about mobile impact in a named UK sub-sector (fintech apps, healthtech, gaming, consumer), not a list of frameworks you know or apps you have touched.
Technical contribution to the digital technology sector
This is where framework and ecosystem work pays off. Accepted framework proposals (a merged Swift Evolution proposal, a credited Kotlin / Jetpack Compose / SwiftUI / React Native / Flutter contribution), authorship of a widely-installed open-source mobile library, and published technical writing the community builds on are all strong evidence. The bar is 'this is publicly attributable to you and others rely on it', not 'I wrote clean code in our internal app'. Accepted framework proposals are gold-standard and badly under-claimed by engineers who could legitimately point at a merged commit or proposal.
The specific evidence the panel rewards.
- 01An app you led with publicly checkable scale
An app on the App Store or Google Play that you led or built, with scale anyone can verify — millions of downloads or monthly active users, a store ranking in its category, sustained ratings volume. The bar is 'a public, attributable app with real numbers', not 'I built an app'. Include the store listing, the download / MAU figure and its source, the category ranking, and your specific role (lead, architecture owner, the engineer credited in release notes or press).
- 02App Store / Google Play editorial features and design awards
App of the Day, an Editors' Choice or featured slot, an Apple Design Award, or a Google Play 'Best of' / Best-of-Year award for an app you led. These are publicly checkable and read as platform-vendor recognition. Include the feature date or award, the store listing, and evidence of your role on the app that earned it.
- 03Accepted framework / ecosystem proposals (Swift Evolution, Kotlin, Compose, RN, Flutter)
A merged Swift Evolution proposal, a credited contribution to Kotlin, Jetpack Compose, SwiftUI, React Native, or Flutter, or accepted commits to a major mobile framework. Verifiable in the public proposal repo or the framework's commit history with your name attached. This is among the strongest available evidence for the technical-contribution criterion and is badly under-claimed.
- 04Authorship of a widely-installed open-source mobile library
You authored or are a top-N maintainer of a mobile library others install — a networking, image-loading, dependency-injection, persistence, or UI library on CocoaPods, Swift Package Manager, Maven Central, or npm. Include the project, the install / download count (CocoaPods stats, Maven / npm downloads, GitHub stars), named users, your specific area, and the maintainer evidence (OWNERS / MAINTAINERS file, release history).
- 05Accepted talks at named mobile conferences
Accepted-track or invited talks at droidcon, try! Swift, SwiftConf, KotlinConf, App.js, Chain React, FlutterConf, or comparable named venues. A local meetup talk corroborates but doesn't clear the bar on its own. Include the CFP acceptance or invitation, venue, attendance, and the recording or published slides.
- 06Quantified product impact tied to the app
Metrics that show the mobile work moved the business — a crash-rate or cold-start reduction at scale, a conversion or retention lift from a feature you owned, a migration (UIKit→SwiftUI, Views→Compose, native→cross-platform) that shipped to millions. Pair the number with its source and your attributable role. A metric tied to a publicly checkable app is far stronger than an internal figure the panel cannot verify.
- 07Three independent recommendation letters
Three letters from senior figures who can speak to your work — ideally from outside your current employer (a conference programme chair, a framework maintainer who merged your proposal, a co-maintainer of your library, a platform partner). Letters from your direct manager about an internal app are weaker than letters from external collaborators who can attest to a public, checkable contribution.
Common failure modes, and the fix.
FixThis is the cardinal mistake for this field. Being excellent at a framework corroborates competence, not external standing among peers outside your employer. It supports a wider narrative but never clears the recognition criterion. Replace it as recognition evidence with a store feature or design award, an accepted framework proposal, a widely-installed library, or a named-conference talk.
FixMaintaining or building one company's internal app is real work, but it is invisible to the panel — there is no store listing, no public download count, no third party who can confirm scale. If your strongest material is an internal app, either externalise a component (open-source a library you extracted, publish a technical writeup, give a talk), apply for Promise, or lead with a different public artefact.
FixA bare claim of authorship carries little weight. The panel wants publicly checkable scale (downloads, MAU, store ranking) and evidence that the work is attributable to you (release-note credit, press, a referee). Lead with the store listing, the numbers and their source, and your specific role — architecture owner, mobile lead, the named engineer.
FixA collection of personal apps with a few hundred downloads each demonstrates initiative but not the scale or recognition the panel weights. One app with millions of users that you demonstrably led beats ten personal apps nobody installs. Lead with the highest-scale, most attributable app; treat the rest as supporting colour at most.
FixIf your strongest material is an internal app or framework proficiency, apply for Promise, which has a meaningfully lower bar for senior ICs. If you're confident the Talent bar is met, lead with the strongest external signal — a high-scale public app with checkable numbers, a store feature, an accepted framework proposal, or a widely-installed library — in your personal statement.
FixThe personal statement is your one chance to argue the holistic case for the mandatory criterion. Use it to articulate a single coherent narrative — what mobile impact you delivered, the numbers (downloads, MAU, ranking, the metric a feature moved), the public artefact that verifies them, and why it benefits a named UK digital sub-sector. A framework-and-SDK inventory is not an argument.
The specifics that decide outcomes.
Concrete achievement and reference-letter templates (mobile)
Reference letter from a platform partner or conference chair: 'I chair the programme committee for [droidcon / try! Swift]. [Engineer]'s talk on [topic — e.g. a Compose migration at scale / an offline-first sync architecture] was accepted to our [Year] main track from a competitive CFP, and they presented to [attendance] attendees. Their app [App], which they lead, is among the higher-scale apps in [category] on Google Play / the App Store, and the talk drew directly on that production work. In my assessment they rank among the stronger mobile engineers presenting externally in this ecosystem.'
Quantified-impact narrative for the personal statement: 'I led mobile engineering on [App] ([category — e.g. a consumer fintech app]), which reached [M]+ downloads and [N]M monthly active users and ranked #[K] in [category] on [store]. I owned the [iOS / Android] architecture and the migration from [UIKit → SwiftUI / Views → Jetpack Compose], which cut cold-start time by [X]% and crash-free sessions to [Y]%. The app was featured as [App of the Day / Editors' Choice] in [Year].'
Library-authorship narrative example: 'Authored [open-source mobile library] ([category — e.g. an image-loading library for iOS]), [N]k GitHub stars, [install / download figure on CocoaPods / Maven / npm], depended on by apps at [named users]. Top maintainer by commit and review count; presented at [named conference] [Year].'
Recognition / framework narrative example: 'Authored [SE-NNNN], a merged Swift Evolution proposal adopted in Swift [version]. Apple Design Award finalist / Google Play Best of [Year] for [App]. Accepted main-track talk at droidcon [City] [Year]. Credited contributor to [Jetpack Compose / React Native] with [N] merged PRs.'
Letter ask you can send to a conference chair or framework maintainer: 'Hi [Name], I'm applying for the UK Global Talent visa under Tech Nation. The panel weights letters from people outside my employer who can attest to a specific external contribution. Would you write a 1-page letter on [my accepted talk at X / my merged proposal SE-NNNN / my library Y] — what it is, how it's used, and your assessment of its standing? I can share a short brief on what the panel's technical-contribution and recognition criteria look for.'
What 'externally-recognised' actually looks like for mobile engineers
Tech Nation's guidance distinguishes internal achievement (built a polished internal app, knows Swift / Kotlin / Flutter deeply, holds a vendor certification) from externally-recognised contribution (work attested by people or systems outside your employer). For this cohort the gap is structural: app stores make scale publicly checkable, which is a gift — but only if your app is actually on a public store and attributable to you. The applicants who clear the bar are the ones with a public, attributable artefact and real numbers.
External recognition here means: (a) artefacts others verify or rely on — an app with publicly checkable downloads / MAU / ranking, a widely-installed open-source library, an accepted framework proposal; (b) third-party attestation — App Store / Google Play editorial features, Apple Design Awards or Google Play Best-of recognition, accepted CFPs at named mobile conferences, a merged Swift Evolution proposal; (c) a verifiable footprint — store stats, install counts, GitHub stars, conference attendance figures.
'Led a high-scale public app + a store feature or named-conference talk' is the canonical strong pattern for this role. The panel rewards: the store listing + the download / MAU figure and its source + the category ranking + your specific role + the feature, award, or talk that presented the work. Framework proficiency, by contrast, proves you can build well — it is corroboration of baseline competence and never clears the recognition or technical-contribution criterion.
Framework and ecosystem work — a merged Swift Evolution proposal, a credited Kotlin / Jetpack Compose / SwiftUI / React Native / Flutter contribution, authorship of a widely-installed library — is gold-standard and badly under-claimed. If you have a merged proposal or a library real apps install, lead with it; it's verifiable in public repos and reads as peer recognition by definition.
Common evidence patterns for senior mobile engineers
Pattern 1 — high-scale app lead: an app on the App Store / Google Play that you led, with publicly checkable scale (millions of downloads / MAU, a category ranking) + a store feature or design award + a letter from a senior collaborator or platform partner. This is the strongest single pattern and often supports a Talent application on its own.
Pattern 2 — library author: authorship or top-N maintainership of a widely-installed open-source mobile library (networking, image-loading, DI, UI) with named users + a named-conference talk. Strong for both tiers; pairs well with the apps that depend on the library.
Pattern 3 — framework / ecosystem contributor: a merged Swift Evolution proposal, or credited Kotlin / Jetpack Compose / SwiftUI / React Native / Flutter contributions + the talks or writeups that follow. Verifiable in public proposal repos and commit history — extremely strong and under-used.
Pattern 4 — recognised speaker: accepted main-track talks at droidcon, try! Swift, SwiftConf, KotlinConf, App.js, or Chain React + the production app or library the talks draw on. Strong recognition evidence when paired with a checkable artefact.
Pattern 5 — high-scale platform migration: leading a migration that shipped to millions (UIKit→SwiftUI, Views→Jetpack Compose, native→cross-platform) with the before/after metrics (cold-start, crash-free rate, binary size). Strong technical-contribution evidence when the app's scale is publicly checkable.
Common rejection patterns and how to fix them
Rejection 1 — framework proficiency presented as recognition. Fix: this is the cardinal error for mobile applicants. Being excellent at Swift / Kotlin / Flutter corroborates competence, not standing. Replace as recognition evidence with a store feature or design award, an accepted framework proposal, a widely-installed library, or a named-conference talk. Keep proficiency in a supporting role only.
Rejection 2 — an internal enterprise app the panel can't find on a store. Fix: externalise a component (open-source an extracted library, publish a technical writeup, give a talk), apply for Promise, or lead with a different public artefact. An unverifiable internal app can't carry a Talent case.
Rejection 3 — 'I built the app' with no scale numbers and no attributable credit. Fix: lead with the store listing, the publicly checkable scale (downloads, MAU, ranking) and its source, and your specific role — release-note credit, press, or a referee. A bare authorship claim carries little weight.
Rejection 4 — a portfolio of low-install personal apps. Fix: one high-scale app you demonstrably led beats ten personal apps nobody installs. Lead with the highest-scale, most attributable app; treat the rest as supporting colour at most.
Rejection 5 — personal statement that inventories frameworks, SDKs, and platforms. Fix: argue the holistic mandatory case instead — what mobile impact you delivered, the numbers (downloads, MAU, ranking, the metric a feature moved), the public artefact that verifies them, and why it benefits a named UK digital sub-sector (fintech apps, healthtech, gaming, consumer).
Career path on the visa — what changes day one
Day one of Global Talent grant: you can work for any UK employer, multiple employers simultaneously, your own UK or non-UK company, contract, freelance, or advise. There's no SOC code, no salary floor (vs Skilled Worker), no employer-tied amendment process — useful for mobile engineers who maintain an open-source library, ship indie apps, or do fractional consulting alongside a main role.
Compensation context: senior mobile-engineering salaries in London run roughly £80–150k for senior ICs, with principal / staff mobile engineers at name-brand consumer, fintech, and gaming firms reaching £170–250k base. Specialist iOS / Android leads at scaled tech and fintech firms sit at the top of that band; add equity at high-growth companies and total comp at UK arms of US public companies can approach mid-tier Bay Area packages.
Founder optionality: Global Talent permits founding companies — relevant for engineers building a consumer app, a mobile-developer-tooling startup, or a cross-platform SDK. The SEIS / EIS investor-incentive schemes are structurally favourable to early-stage equity, and the UK has a dense early-stage VC base across consumer, fintech, and gaming (Index, Accel London, Notion, LocalGlobe, Seedcamp, EF), alongside a strong mobile-first investor scene.
ILR clock: 3 years for Talent, 5 years for Promise. Time spent outside the UK over 180 days in any rolling 12-month period can break the clock — track it meticulously, especially if you travel for conferences. After ILR the route's conditions fall away; British citizenship is reachable 12 months after ILR.
From today to the visa decision.
- 01Pre-application: triage your evidence
Use the Rate-my-application grader. Decide tier (Talent vs Promise). Identify three referees — at least two outside your current employer (a conference programme chair, a framework maintainer who merged your proposal, a library co-maintainer, a platform partner).
- 02Week 0-2: Stage 1 endorsement application
Submit endorsement online via Tech Nation portal. PDF evidence + statements of personal achievement and contribution. £561 fee.
- 03Week 5-8: Endorsement decision
Tech Nation: 8 weeks standard, 3 weeks fast-track (+£500). Decision via email; endorsement letter uploaded to your account.
- 04Week 8-10: Stage 2 visa application + biometrics
File at gov.uk within 3 months of endorsement. £205 visa + IHS (£3,105 for Talent / £5,175 for Promise per adult). Biometrics at local UK VAC.
- 05Week 10-13: Visa decision
Standard 3 weeks. Priority 5 working days (+£500). Super-priority next-day (+£1,000).
- 06Week 13-16: UK arrival + onboarding
Collect Biometric Residence Permit within 10 days. Register with a GP, get NI number, open UK bank account. Start applying for roles or transition to UK arm of current employer.
- 07Year 3 or 5: ILR
Apply for Indefinite Leave to Remain. Life in the UK test, English language proof. Citizenship eligible 12 months later.
Practical tips for this role.
Lead with 'I led [App], [M]+ downloads and [N]M MAU, ranked #[K] in [category]' — that framing addresses the contribution and recognition criteria with publicly checkable numbers.
Apply for Promise if your evidence is an internal app plus framework depth and a modest external footprint — the bar is lower and aligned with senior IC profiles.
Cite App Store / Google Play features, Apple Design Awards, and Google Play Best-of recognition — they're publicly checkable platform-vendor recognition.
Highlight an accepted Swift Evolution proposal or credited Kotlin / Compose / RN / Flutter contribution — it's gold-standard and under-claimed.
Use accepted talks at droidcon, try! Swift, SwiftConf, KotlinConf, App.js, or Chain React as recognition evidence.
Lead with one high-scale app you demonstrably led, with numbers and their source.
Tie your mobile impact to a named UK digital sub-sector (fintech apps, healthtech, gaming, consumer) for the mandatory criterion.
Don't lead with framework proficiency — being excellent at Swift / Kotlin / Flutter proves competence, not external standing, and reads as the wrong evidence to the panel.
Don't apply for Talent on internal-only or proficiency-led evidence — rejected Talent applications don't auto-roll-down to Promise; you'd reapply from scratch.
Don't present a polished internal app the panel can't find on a store as recognition — without a public listing and scale it can't carry the case.
Don't list the frameworks and SDKs you've used in the personal statement — the panel reads the CV separately.
Don't use a local mobile meetup talk as primary recognition evidence — named venues clear the criterion; a local meetup corroborates.
Don't pad with a portfolio of low-install personal apps — one app with millions of users beats ten nobody installs.
Don't claim scale the panel can't verify — pair every download / MAU figure with a public source (store stat, press, investor deck).
Verify at the source.
Authoritative UK Home Office landing page.
Endorsing body for digital technology — primary route for mobile / iOS / Android engineers.
Official Tech Nation application guide — required reading before applying.
What the Tech Nation 10-year report shows about who actually gets endorsed — internal site research.
Step-by-step practitioner's guide for the Tech Nation route.
Where the panel checks an iOS app's listing, ratings, and featured status — the canonical source for App Store scale evidence.
Where the panel checks an Android app's install count, ratings, and Editors' Choice / Best-of status.
The public repository of Swift Evolution proposals — where a merged proposal credited to you is verified.
Named platform-vendor recognition — an award or finalist slot is strong recognition evidence.
Flagship Android conference — accepted main-track talks are strong recognition evidence.
Named iOS / Swift conference — accepted talks are decisive recognition evidence.
Active iOS-development community on Reddit — App Store experiences and occasional UK Global Talent threads.
One-click LinkedIn search to find mobile engineers who hold the UK Global Talent Visa — useful for peer references and benchmarking.
Common questions.
Do I need a UK job offer before applying?+
No. Global Talent is self-petition — there's no requirement for a UK employer, sponsor, or job offer at any stage. Once endorsed and granted the visa, you can work for any UK employer, multiple employers, your own company, or self-employ. Many endorsed mobile engineers arrive without a UK role lined up and find one in their first 4–8 weeks.
Does being highly skilled at Swift, Kotlin, or Flutter count as evidence?+
It corroborates competence, not external recognition — and over-relying on framework proficiency is the single most common mistake mobile engineers make. Tech Nation's recognition criterion is about standing among peers outside your employer: a store feature or design award, an accepted framework proposal, a widely-installed library, a named-conference talk. Being excellent at a framework can support a wider narrative but never clears the recognition or technical-contribution criterion on its own.
Which tier should a mobile engineer apply for?+
Talent ('Exceptional Talent') fits principal and staff mobile engineers behind very-high-scale apps, authors of widely-installed mobile libraries, contributors of accepted framework proposals (Swift Evolution, Kotlin, Jetpack Compose), and named-conference speakers (droidcon, try! Swift, KotlinConf). It leads to ILR in 3 years. Promise ('Exceptional Promise') fits senior mobile ICs under roughly 5–8 years who led a high-scale shipped app and are building an external footprint — a first talk, a growing library, a store feature. It leads to ILR in 5 years. Most engineers whose record is internal-only or proficiency-led fit Promise, not Talent.
My best app is an internal enterprise app that isn't on a public store. How do I evidence it?+
An internal app is real work but the panel can't verify it — there's no store listing, no public download count, no third party who can confirm scale. Where you can, externalise a component: open-source a library you extracted from it, publish a technical writeup on the architecture, or give a named-conference talk. If you can't externalise it, treat it as Promise-tier evidence and lead with a different public, checkable artefact rather than applying for Talent on it.
How does app scale need to be evidenced?+
With publicly checkable numbers — downloads or monthly active users in the millions, a store category ranking, sustained ratings volume — and evidence the work is attributable to you. Lead with the store listing, the figure and its source (a public store stat, a press release, an investor deck), the ranking, and your specific role. A publicly checkable app with real scale is the strongest single artefact for this cohort; an internal app or a bare 'I built it' claim the panel can't check carries little weight.
Do App Store or Google Play features and design awards count?+
Yes — strongly. An App of the Day or Editors' Choice feature, an Apple Design Award, or a Google Play 'Best of' award is publicly checkable and reads as platform-vendor recognition. Pair the feature or award with evidence of your role on the app that earned it. These are among the cleanest recognition artefacts available to mobile engineers.
Do open-source mobile libraries count?+
A widely-installed library you authored or co-maintain is strong evidence for both the technical-contribution and recognition criteria. The panel can verify install counts on CocoaPods, Maven Central, or npm, GitHub stars, and your maintainer status. A networking, image-loading, DI, or UI library that real apps install reads far better than a polished internal codebase nobody outside your company sees.
Does an accepted Swift Evolution proposal or framework contribution help?+
It's gold-standard for the technical-contribution criterion and badly under-claimed. A merged Swift Evolution proposal, or a credited contribution to Kotlin, Jetpack Compose, SwiftUI, React Native, or Flutter, is verifiable in the public proposal repo or commit history with your name attached. If you have one, lead with it — it reads as peer recognition by definition.
Will my US H-1B / O-1 / L-1 status affect the UK application?+
No. Your current US visa status has no bearing on the UK endorsement or visa. Many Tech Nation-endorsed engineers apply from the US while still on H-1B; some keep both options open during the transition.
Does a local mobile meetup talk count as named-conference recognition?+
It corroborates but doesn't clear the criterion on its own. Tech Nation distinguishes named mobile conferences (droidcon, try! Swift, SwiftConf, KotlinConf, App.js, Chain React, FlutterConf) from a local meetup. An accepted talk at a named venue is decisive recognition evidence; a local-meetup talk is supporting material.
What's the typical end-to-end timeline?+
Tech Nation 8 weeks standard (3 weeks fast-track for +£500). Stage 2 visa 3 weeks standard, 5-day priority. End-to-end under 4 months is typical.
Related pages
The sibling role page — same Tech Nation route, generic-SWE evidence patterns.
Adjacent product cohort — same store-feature and design-award signals, different artefacts.
The full step-by-step practitioner's guide for the Tech Nation route.
Tech Nation criteria, tier-by-tier breakdown.
What the 10-year report shows about who actually gets endorsed.
If you have a UK job offer in hand, here's the trade.
Free AI grader against the four Tech Nation criteria.