Maildesk — public portfolio showcase
Multi-platform mail workspace — web plus mobile client references
Curated by Jelvan R. · Public documentation, not the original source repository.
[!IMPORTANT]
Independent public portfolio adaptation — confidentiality and attribution
This repository is a revised, selectively documented portfolio presentation independently prepared and maintained by Jelvan R. Certain past projects or engagements may be subject to confidentiality, nondisclosure, contractual, intellectual-property, or client-security obligations. To respect those obligations, this public presentation may anonymize, simplify, recreate, omit, or update parts of the original work. It is not an exact copy, complete implementation, production configuration, or authoritative description of any client system.
This showcase is not an official publication of, sponsored by, endorsed by, or affiliated with any current or former client, employer, company, or other development organization. References to third-party products, technologies, or historical project terminology are for identification only. This notice does not claim exclusive ownership of client deliverables, third-party components, trademarks, or intellectual property.
No confidential source code, credentials, client data, internal hostnames, or production access are provided. Features and deployment claims must be read with the project-specific verification notes below.
Overview
A private mailbox and communication workspace presented publicly as a sanitized UI/architecture case study; no real messages, contacts, login credentials or deployed mail systems are provided.
Current evidence and status
Web source implementation documented; Android production API compatibility gap noted in source; iOS remains scaffold/API client.
This repository is documentation-only: it does not include an application build, genuine account access, production dependencies or a deployment artifact.
What the source documentation supports
- Operava-Mail web README documents authentication, mail folders, admin features, AI writing, and Cloudflare backend.
- Operava-Mail package.json confirms Next.js 15, React 19, OpenNext/Cloudflare, Supabase client.
- MailDesk-Android is Flutter; its own October 17, 2026 audit warns the Android client contract is incompatible with the live API.
- MailDesk-iOS describes scaffold plus API client, not a complete signed iOS release.
- operava-maildesk-api is an OpenAPI template repository; do not misidentify it as the complete production service.
Technology context
- Next.js 15, React 19, Tailwind / DaisyUI (web)
- Cloudflare Workers via OpenNext
- Supabase persistence; email transport integrations
- Flutter (Android client)
- Swift package and native iOS client scaffold
Capabilities described or proposed
- Mailbox navigation: inbox, sent, outbox and trash
- Authenticated multi-user account handling in web source
- Drafting/composing and server-side mail transport integrations
- Mobile client implementations at different maturity levels
Accuracy rule: Any item identified as illustrative, proposed, unverified, or source-documented must not be marketed as a live, completed feature.
Architecture at a glance
Portfolio frame → Sanitized Maildesk preview (separate demo) → demo services only; production mail platform stays isolated
For component boundaries, implementation caveats and verification: Architecture and Implementation Notes.
Device previews
The portfolio can offer macOS, Desktop Web, iOS and Android presentation modes. That does not imply a native build exists on every platform.
Read the device preview policy before enabling live framing. Public demo assets are intentionally absent until permission and sanitization checks are passed.
Known limitations
- No production mailbox, message contents, email addresses, authentication secrets, or internal access are published.
- Do not assert Android release compatibility, iOS App Store acceptance, or production feature parity.
- The viewer must hide the Maildesk address and external-open control; iframe controls do not provide secrecy.
Repository contents
README.md Project overview and verification status
DISCLAIMER.md Public-view / NDA and attribution notice
SECURITY.md Safe disclosure and content-handling policy
CONTRIBUTING.md Public contribution boundaries
portfolio.json Sanitized metadata for portfolio integration
docs/ARCHITECTURE.md Architecture and boundaries
docs/IMPLEMENTATION.md Evidence, components and non-goals
docs/DEVICE_PREVIEW.md Frame behavior and security policy
docs/DEPLOYMENT.md Safe showcase publication workflow
docs/TESTING.md QA and release gate checklist
docs/SOURCE_VERIFICATION.md Evidence status without private repo details
docs/CHANGELOG.md Public documentation changelog
assets/README.md Sanitized images/screenshot instructions
Start here
- Review the disclaimer and implementation notes.
- Replace placeholder screenshots only with approved, anonymized visuals.
- Confirm platform support, and enable approved public demo links only after independent testing.
- Publish as a distinct public repository; never mirror, fork or reveal original private projects.
- Add the public showcase URL to the Projects section of portfolio.jelvan.pro without making production URLs visible in the viewer.
Licensing and use
This repository provides public-facing explanatory materials only. Public visibility is not an open-source license or a grant of rights to confidential or third-party works. Written permission and applicable rights are needed before reuse. No rights in third-party products, names, interfaces, libraries, or client materials are asserted.
Contact
For portfolio discussion, use the contact route on portfolio.jelvan.pro. Do not post confidential information in public issues.