vh
85f8a3a072
The 2026-09-28 expansion grew the one-page design to nine pages by bolting a nav band under each hero. This makes the cluster one site: - One site header on every page: the wordmark (home link) and a single row of short, consistent labels (Applications, Systems, Hosting, AI, Engagement, Track record, Contact). The nav no longer wraps into two rows at desktop width or four on a phone. - A real <h1> on every page (the title was a <p>), a skip link, and one footer outside <main> on every page, home included. - The contact page was unreadable: its section borrowed the home page's dark contact-card id, so its copy was grey on near-black (2.3:1) and its headings measured 1.0:1. It is an ordinary section now. - Section numbers only where there is a sequence (home, engagement). - The spec bar names all four services; it stacks cleanly on a phone. - Contrast: --text-tertiary 4.3:1 -> 4.96:1, --accent-text 4.36:1 -> 4.74:1 on paper. Track-record labels drop tracked capitals. - The grid behind the hero and the contact card is its own layer; the contact card loses its left side-tab stripe. - The stylesheet link is versioned (style.css?v=2026-09-28): CSS is cached for an hour, and the new markup must not meet the old styles. - README: nine pages, the shared structure, the CSS-version rule, and the operator's anti-slop waivers (the hero's volt rule, Space Grotesk). Copy is unchanged apart from nav labels (the brief's legal constraints hold). Still zero JavaScript and zero external requests. Impeccable detector (controls 7/0, static + rendered at 1280 and 390, light and dark): 200 unwaived -> 54, all of them the two waived brand devices; two identical runs. Operator: "ship the site cleanup, keep the rule and the font".
90 lines
4.1 KiB
HTML
90 lines
4.1 KiB
HTML
<!DOCTYPE html>
|
|
<html lang="en">
|
|
<head>
|
|
<meta charset="utf-8">
|
|
<meta name="viewport" content="width=device-width, initial-scale=1">
|
|
<meta name="theme-color" content="#0f1318">
|
|
<title>Custom Application Development — Phase Final, Inc.</title>
|
|
<meta name="description" content="Custom application development for iOS, Android, web, and desktop: native apps, backend services, release pipelines, and long-term operation by the team that built them.">
|
|
<link rel="icon" href="/favicon.svg" type="image/svg+xml">
|
|
<link rel="stylesheet" href="/style.css?v=2026-09-28">
|
|
</head>
|
|
<body>
|
|
|
|
<a class="skip" href="#main">Skip to content</a>
|
|
<header class="site-header">
|
|
<div class="site-header-inner">
|
|
<a class="brand" href="/"><img src="/assets/pfi-wordmark-duotone-dark.svg" alt="Phase Final, Inc." width="98" height="28"></a>
|
|
<nav class="site-nav" aria-label="Site">
|
|
<ul>
|
|
<li><a aria-current="page" href="/services/software/">Applications</a></li>
|
|
<li><a href="/services/systems-engineering/">Systems</a></li>
|
|
<li><a href="/services/hosting/">Hosting</a></li>
|
|
<li><a href="/services/ai/">AI</a></li>
|
|
<li><a href="/engagement/">Engagement</a></li>
|
|
<li><a href="/track-record/">Track record</a></li>
|
|
<li><a href="/contact/">Contact</a></li>
|
|
</ul>
|
|
</nav>
|
|
</div>
|
|
</header>
|
|
|
|
<header class="page-header">
|
|
<div class="hero-inner">
|
|
<div class="hero-copy">
|
|
<h1 class="lede">Custom applications, built to spec.</h1>
|
|
<p class="sublede">We design, build, and operate applications: native iOS and Android, web and desktop clients, the backend services behind them, and the release pipeline that keeps them shipping. The team that builds an app stays accountable for it in production — no hand-off cliff.</p>
|
|
</div>
|
|
</div>
|
|
</header>
|
|
|
|
<main id="main">
|
|
|
|
<section id="scope">
|
|
<h2>Scope</h2>
|
|
<div class="section-body">
|
|
<p class="detail-lede">An application is never just the app. It is the client binary, the API behind it, the data model, the release train, and the operational story for what happens at 2 a.m. when something breaks. We take the whole problem.</p>
|
|
<ul class="detail-list">
|
|
<li>
|
|
<h3>Native mobile (iOS & Android)</h3>
|
|
<p>Native and cross-platform mobile applications, from first submission through App Store and Play submission, staged rollouts, and OTA updates. Device integration when the app talks to hardware the firm also designed.</p>
|
|
</li>
|
|
<li>
|
|
<h3>Web and desktop applications</h3>
|
|
<p>Internal tools, operator consoles, customer portals, and desktop utilities. Chosen for the job rather than for fashion — plain served HTML is a legitimate architecture.</p>
|
|
</li>
|
|
<li>
|
|
<h3>Backend and APIs</h3>
|
|
<p>Service design, data modeling, authentication, and integration with the systems a client already runs. Documented interfaces and versioned contracts so the application and its backend can move independently.</p>
|
|
</li>
|
|
<li>
|
|
<h3>Release engineering</h3>
|
|
<p>Build pipelines, signing, provisioning, store review handling, crash reporting, and telemetry. An app without a release pipeline is a prototype.</p>
|
|
</li>
|
|
<li>
|
|
<h3>Operation and maintenance</h3>
|
|
<p>Post-launch retainers cover OS-compatibility updates, store policy changes, dependency upkeep, and capacity. Applications decay quietly when nobody owns them; we keep the ownership explicit.</p>
|
|
</li>
|
|
</ul>
|
|
<p class="related"><a href="/services/hosting/">Hosting →</a> <a href="/services/ai/">AI services →</a> <a href="/engagement/">How we engage →</a></p>
|
|
</div>
|
|
</section>
|
|
|
|
</main>
|
|
|
|
<footer class="site-footer">
|
|
<span>Phase Final, Inc.</span>
|
|
<nav aria-label="Footer">
|
|
<a aria-current="page" href="/services/software/">Applications</a>
|
|
<a href="/services/systems-engineering/">Systems</a>
|
|
<a href="/services/hosting/">Hosting</a>
|
|
<a href="/services/ai/">AI</a>
|
|
<a href="/engagement/">Engagement</a>
|
|
<a href="/track-record/">Track record</a>
|
|
<a href="/contact/">Contact</a>
|
|
<a href="/privacy/">Privacy</a>
|
|
</nav>
|
|
</footer>
|
|
</body>
|
|
</html>
|