initialising xulorybenq…

loading: Swift · SwiftUI · StoreKit · RevenueCat · Adapty

status: building · testing · shipping

XULORYBENQ

Mobile utility tools built around a single purpose — solved completely, shipped cleanly, then kept honest after launch.

See what we build →

What we build

Swift SwiftUI StoreKit 2 CloudKit Firebase Adapty AppsFlyer Amplitude TestFlight

Privacy & VPN

Traffic control with visible, legible protection. Kill switches, protocol selection, and connection status surfaced plainly — not buried three taps deep. Protection that's legible, not just present.

Storage Cleaners

Cache, duplicates, and residual data surfaced and removed with a confirmation step before anything is touched. Users stay in control. The tool reports; the user decides.

File Converters

On-device format bridges — documents, images, media. Files never leave the device. No upload queue, no third-party dependency, no server round-trip. Output lands in share sheet immediately.

Document Scanners

Edge detection, perspective correction, clean PDF export. Core scanning is free on the first tap. Works in ordinary indoor light on ordinary hardware. No first-run subscription screen.

Battery & Performance

Identify what's draining the device without contributing to the problem. Diagnostics that are honest about what they find and lightweight about how they find it. No inflated threat scores.

Safety Utilities

Permission access patterns, configuration anomalies, and network irregularities — surfaced in plain language. Actionable output. No manufactured urgency. No alarm-style dashboards designed to upsell.

How we work

From gap to shipped, honestly.

Three phases, one standard — every decision justified by the problem it solves, not the feature list it adds to.

Research — App Store reviews, user forums, and what the competing tools consistently get wrong before a single wireframe exists. The narrow problem definition is what keeps scope from drifting. We read the complaints so we know exactly where the gap is.

Design — Tap paths mapped before visual work begins. Native platform conventions because users have already learned them — we build on that, not against it. Accessibility baked in from the first wireframe. We don't bolt it on at the end when it's expensive and easy to skip.

Ship — TestFlight, staged rollout, live monitoring. The 1.0 release is the beginning of a tool's life. iOS updates shift APIs; user patterns evolve. We stay close after launch because that's when the real signal arrives.

What we believe

01

Less, on purpose

Narrow scope is the constraint that produces reliability. A tool that does one thing completely is worth more than one that does five things adequately. Every addition is a trade — and the costs compound invisibly over time.

02

No borrowed growth

Distribution earned through product quality compounds. We build things that get recommended because they're genuinely worth recommending — not because we paid for placement or gamed a review system.


03

Invisible craft

The decisions that define a well-built tool are invisible when they're right. Users notice only when they're wrong. We aim for the absence — the experience of something that just works, without asking for attention.

04

The first tap is free

The function that justifies downloading the app must work without a subscription. Premium depth is legitimate. Gating the core task is not. We don't build apps where the first-run experience is a paywall.

Questions

//

Where are the apps available?

Apple App Store — iOS and iPadOS, native only. No cross-platform wrappers, no Android version. Native-first because the tools behave the way the platform was designed to work and update in step with iOS releases rather than months behind them.

//

Do you take external development work?

No agency work — all products are internally conceived and built. If you have a specific partnership or licensing enquiry, write to us directly. We consider each case, but the default is working on the internal roadmap.

//

How is user data handled?

On-device wherever the architecture allows it. When server components are genuinely needed — subscription validation, aggregated crash logging — we collect the minimum required and never sell it. Each app's App Store privacy label reflects the actual implementation.

//

Are core features always free?

Yes. The function that justifies downloading the app works without a subscription. Premium unlocks depth — batch processing, extended history, advanced configurations. We don't build apps where the first experience is a prompt asking you to subscribe before you've seen what the tool does.

Contact