Entity
OMWSD LTD
Company no.
17452769
Registered
England and Wales
Based
Wolverhampton, UK
(Software development studio · West Midlands, UK)
OMWSD LTD designs, builds and releases software — native applications for iPhone and iPad, platforms for the web, and the infrastructure underneath them. Anything we put our name to, we also keep running. Our own product, Vizione, is built to the same standard we hold client work to.
OMWSD LTD
Registered in England & Wales
17452769
Company number
iOS · Web · Infra
Where we work
Wolverhampton
Built in the West Midlands
Most software problems are not coding problems. They are decisions taken too late, releases treated as paperwork, and nobody named as responsible once the thing is live. We work in four movements so none of those three can happen quietly.
Decide what it is before writing it.
Scope, screens and data model first, in that order. Most software fails because the second version of the idea arrives after the first one is already built — so we argue it out on paper, where changing your mind is free.
Native where it matters, boring where it doesn't.
Swift and SwiftUI for iPhone and iPad. TypeScript, React and Next.js on the web. Python or Node behind it. No framework chosen because it was interesting — chosen because it will still be maintainable in three years.
Release is a discipline, not an afterthought.
Signing, provisioning, store metadata, age ratings, privacy declarations, subscription configuration, review notes. The part of app development that sinks first-time submitters is the part we treat as a checklist with a name against every line.
Shipping is the easy half.
Deployment, TLS, monitoring, secrets encrypted at rest, nightly off-site backups and a restore path that has actually been run. Software that nobody is responsible for on a Sunday night is not finished software.
Plenty of people will write you an app. Far fewer will sign it, submit it, answer the review questions honestly, and still be the ones you call in eighteen months.
A short list on purpose. Each of these is something we have built, released and then operated — not a line added because a client once asked for it.
Native applications built with Swift and SwiftUI, taken from an empty project through to a signed build and a completed App Store Connect record — including the parts most builds get wrong: entitlements, privacy manifests, age rating, and subscriptions that restore.
Fig. 03 — How a build is put together
In development — preparing for App Store reviewA media player you bring your own library to. Vizione ships with no content, no catalogue and no way to search for places to find media. You provide the address — your own media server, a NAS, a free-to-air stream, or a service you already hold an account with — and Vizione plays what is there.
The line we do not blur
“It contains no content. It comes with nothing pre-loaded, has no catalogue, and no way to search for places to find media. You provide the address; it plays what is there.”
That is the product definition, the App Store description and the acceptable-use policy, word for word. Vizione must not be used to reach anything the user does not have the right to watch — a condition of use, not a disclaimer.
Fig. 02 — From the build. Every frame uses the app's own demo library: invented titles, generated artwork.
Seven days of schedule, with catch-up behind you and what's coming ahead, laid out for a touch screen rather than shrunk down from a set-top box.
Live, films and series from more than one playlist at a time, kept side by side instead of merged into one unnavigable list.
Resume positions and favourites that follow you across your devices — stored as references we cannot resolve back into titles.
A PIN, per-category locks, and a profile that shows only what an adult has allowed. Set up by the adult, on the adult's device.
Portrait and landscape are designed separately rather than stretched from one another — including a full-width landscape guide.
Two playback engines, chosen per file and swapped silently on failure, so a container another player refuses simply opens.
Privacy, plainly
Playlist sign-in details are held in the iOS Keychain and are never transmitted to us in any form.
Favourites and viewing positions sync as opaque references. We can see that an account has 43 favourites and nothing whatsoever about what they are.
That is a deliberate trade: it makes viewing analytics impossible for us to build, and it is the reason the design is worth having.
For anyone reviewing this
Vizione is a neutral player, in the same category as VLC. It ships with no content, no servers and no directory, names no provider anywhere in the app or its metadata, and offers no way to search for a source. It is empty until a user enters details they already hold. Digital unlocks are sold through Apple in-app purchase.
Vizione is published by OMWSD LTD. It is in development and has not yet been released; the screenshots above are from internal builds. Availability, pricing and subscription terms will be stated on the product's own site at release.
None of these are aspirations. They are the reasons a build either clears review and keeps running, or doesn't — and every one of them is something you can ask us to show you.
Credentials belong in the Keychain, not on our servers. Where a product can be built so that we are incapable of holding sensitive data, it is built that way — which also means there is nothing to leak, and nothing to hand over.
Every dependency is checked for licence compatibility before it ships. A GPL-3.0 component cannot be distributed on the App Store; discovering that after the app is built costs weeks. We check first, and record the decision.
App Store Review Guidelines, the Developer Program Licence Agreement and the Human Interface Guidelines are read as specification, not as obstacles. Age ratings, subscription disclosure and data declarations are answered honestly, because a mismatch found later costs far more than the honest answer does.
Dynamic Type, VoiceOver labels, sufficient contrast and respect for reduced-motion settings are part of the build, not a later pass that never happens. This site follows the same rule.
Off-site backups every night, with a restore that has been performed rather than assumed. A backup nobody has restored from is a hope, not a backup.
Architecture decisions, runbooks and deployment steps are documented in the repository. If a client needs to move the work elsewhere, everything required to do that goes with it.
OMWSD LTD is a private limited company registered in England and Wales. The initials are the founder's — Oliver Michael Westwood — and the SD is what the company does.
It is a small studio, and we would rather say so than imply a floor of engineers. The work is led by Oliver Michael Westwood, who writes the code, signs the builds and answers the email. Specialists are brought in by name when a piece of work needs them, and you are told who they are.
Everything the company publishes — its own applications included — is released under this name, at this address, with this number against it.
Nature of business (SIC)
Statutory details
These details can be checked on the public register at Companies House. OMWSD LTD is not registered for VAT; no VAT is charged and none appears on our invoices.
View the register entryAn app for iPhone and iPad, a web platform, the infrastructure behind either — or an existing build that needs someone to take ownership of it. We reply within one business day.
