What we build

01

Privacy & VPN

Connectivity tools built around user-controlled, legible protection. Traffic routing is explained in plain terms. Kill-switch behaviour is clearly indicated in the interface. No background analytics that would undermine the tool's stated purpose.

Swift NetworkExtension CryptoKit SwiftUI Combine StoreKit 2

02

Storage Cleaner

Deep scan across app containers, download folders, caches, and orphaned install files. Results are grouped, categorised, and totalled before the user touches anything. No silent deletions, no surprise behaviour. Scheduled reminders supported.

Swift FileManager SwiftUI BackgroundTasks UserNotifications Adapty

03

File Converter

On-device format conversion for documents, images, audio, and data files. Batch queuing available. Nothing leaves the device — no upload, no third-party call in the conversion path. Output format and destination are always user-specified.

Swift PDFKit AVFoundation CoreImage UniformTypeIdentifiers SwiftUI

04

Document Scanner

Camera-based scanning with automatic edge detection, perspective correction, and clean PDF output. Optional on-device OCR for structured documents — receipts, forms, IDs. The core scan function is free. Works in standard lighting without extra hardware.

Swift VisionKit Vision PDFKit CoreML Amplitude

05

Battery & Performance

Continuous monitoring of battery health, thermal state, memory pressure, and CPU load — reported in plain language. Trend history for comparison over time. Designed to measure without contributing: the tool's own resource footprint is minimal by requirement.

Swift MetricKit os.log SwiftUI Charts Instruments

06

Safety Utility

Permission audit across installed apps: camera, microphone, location, contacts, health access — all in one readable view. Flags changes since the last scan and links directly to system settings for remediation. No dashboard of amber icons with no path forward.

Swift SwiftUI Contacts HealthKit CoreMotion AppsFlyer

Common questions

What platforms do you build for?

iOS and Android, native SDKs for each. We avoid cross-platform runtimes where they limit access to platform-level APIs — which, for tools that touch permissions, file systems, and encryption, is essentially always.

Do you take contracts or only build your own products?

Both, selectively. Contract engagements work when the scope is clear, the function is well-defined, and the approach aligns with how we work. The best way to find out is to send the brief and let us assess it honestly.

What does post-launch support look like?

Store compliance, OS compatibility updates, and bug fixes are standard. Most engagements include a structured post-launch window, with longer-term maintenance available where the codebase warrants it.

Can you take over an existing app?

Occasionally. We'd review the codebase before committing. If the foundation is sound and the scope is clear, we're open to it — and we'd handle compliance and SDK updates as part of that.

How do you handle monetisation and subscription flows?

We implement whatever model the client specifies, with one non-negotiable: no dark patterns in the purchase or cancellation flow. Clear pricing, clear confirmation, clear cancellation path. The subscription works because the product earns it.

Get in touch

$ connect --studio nofools.info

$ reach --email k.else@nofools.info