Who we are
MVEII builds, holds, and licenses its own intellectual property. This engagement architects and ships the Enterprise’s first mobile application.
Who you are
You have shipped at least two applications to both the App Store and Google Play. You have implemented client-side encryption yourself and can explain key management tradeoffs without looking them up. You work independently against a fixed date and say plainly what you would cut when a timeline compresses.
Scope of work
- Entry. Your best artistic expression of an animated entry sequence that resolves on tap. Black background, gold accents. MV on one side, EII on the other; the two slide in from opposite sides, meet at center, and close as a gate or double doors. Corporate or literal, a building or a gate — your call. Fully animated and fully transitional; the transition to the next screen is part of the work. Beneath it, a consent statement and one button. Consent captured on button press with IP and device token, never on page load. The gate does not open until credentials are cleared — unrecognized devices are prompted for login or serial registration; returning devices bypass consent and preload login unseen. Full art direction is provided to invited candidates.
- Registration. Access requires a registered physical product. QR scan plus printed serial. One serial registers once, permanently, non-transferable. Every account carries a permanent identification number. Gifted units are attributed to the sending serial.
- First run. What a holder sees the first time the gate opens. Orientation to the record, the entry allotment, and how an entry is submitted.
- Analysis engine. Users photograph handwritten pages, edit the transcription, and receive in-depth analysis across their accumulated record. Entries draw against a fixed allotment.
- Account recovery. Password reset and device change, designed against the encryption architecture below. State plainly what can and cannot be recovered.
- Support paths. Failed scan, serial already registered, misread page identifier, failed upload. Each needs a defined path for the holder and a corresponding view in the console.
- Operations console. Internal, separately authenticated. Issue and place serials, look up holders, void and reissue, resolve support cases, audit log. Staff can never reach user content.
- Store approval. Apple and Google, through to approval. Approval is a condition of completion, not submission.
- Handover. At completion: full source, repository ownership transferred to the Enterprise, all credentials and environment configuration, and documentation sufficient for another developer to maintain and extend the build.
Security — non-negotiable
End-to-end encryption. Key derives from user credentials, never leaves the device. The Enterprise must be structurally unable to read user content.
Compensation
Contract value paid in four equal draws at 25%, 50%, 75%, 100% completion. Deliverables per quarter defined in the SOW upon offer.
Plus one share of the Royalty Bond attached to the analysis engine, held as “Architect” — not less than one percent of the engine’s quarterly gross licensing revenue, in perpetuity. Vests on completion of the SOW. A developer who does not finish does not vest.
The share is in the engine, not the products it runs inside. Not equity. No governance or voting rights.
Ownership
Work for hire. The contracting entity is Montévion Valentine Enterprises. Present assignment clause; all right, title, and interest assigned on creation.
How to apply
This requisition is filled in two stages.
Stage one — open
Submit to ops@mveii.com by 2026.09.18:
- Fixed bid for the full scope above
- Hourly rate, stated separately
Include: two shipped apps you architected; your encryption approach and how you handle key management when a user forgets their password; availability September 29 – December 10; and what you would cut if the timeline compressed.
Stack: React Native, Supabase, Anthropic API. Alternatives welcome with reasoning.
Candidates advancing to stage two are notified by 2026.09.22.
Stage two — by invitation
Selected candidates execute a non-disclosure agreement and receive full art direction. They then build a working animated entry sequence — code, not a mockup — submitted as a screen recording and a repository link or build file.
Stage two is unpaid. If MVEII builds with your work, a flat $500 is paid and all rights in the design transfer to MVEII, whether or not you hold the development contract. The entry sequence is scope; stage two is where you demonstrate it.
Submit a bid