tmail flutter mobile application

this project aims at providing a multi-plateform mobile email application, running the jmap protocol and will also deliver additional
features to the tmail back-end.

here is how tmail looks like on a phone:

here is how tmail looks like on a tablet:

faq

why did you choose jmap?

that is a good question! imap is the ubiquitous protocol people use to read their emails, the norm.

yet imap had been designed in another age, which resulted in a chatty patchwork of extensions. imap lacks decent synchronisation primitives to address real-time challenges modern mobile fleet requires, it consumes a lot of bandwith, requires a lot of roundtrips which means high latency.

we are not alone to say this! big players of the field started their own proprietary protocols to address imap flaws, and inter-operable standard was yet to be found…

this, is where jmap comes to play! jmap builds on decades of experience, and beautifully addresses these challenges using http and json standards. not only does it make applications easier to develop, we also strongly believes it results in an improved experience for the end user.

can i use tmail with any jmap server?

yes, you can use the tmail application with any jmap server and benefits from tmail ergonomy and ease of use.

i don’t understand your app… i need help using it! help meeeeee…

don’t worry, we are here!

we plan on writing a user documentation, helping you navigating around the application, and detailing the few configurations you have to perform.

if what you are looking for is not in the user guide then ask us directly in the issues first, we would be glad to help. but also glad to improve our documentation and maybe tweak slightly our ui (user interface).

what plateforms do you (plan to) target?

first, we target android, ios mobiles. we also take care of tablets and large rendering space early on in the development process.

then, we plan on introducing a desktop application.

this versatility is enabled by the use of the flutter framework.

what would your roadmap look like?

first, we plan to write a simple, multi-plateform jmap email client. this includes reading your mails and mailboxes, managing them, sending emails, searching your emails. this will likely keep us busy by the end of 2021.

then, we have plan for multiple features including:

• support for tmail encrypted mailbox (gpg)
• support for tmail shared mailboxes
• support for tmail filters
• interactions with some other software from linagora including:
  • sending attachments via linshare file sharing platform.
  • transfering some attachments you received to linshare file sharing platform.
  • discussing some emails you received via twake chat.

any chance to support jmap extension for calendar, contacts?

no we do not plan to support such extensions, that are currently not standardized as rfcs, nor implemented on the tmail backend.

your work is awesome! i would like to help you. what can i do?

thanks for the enthousiasm!

there are many ways to help us, and amongst them:

• spread the word: tell people you like tmail, on social medias, via blog posts etc…
• give us feedbacks… it’s hard to make all good decisions from the first time. it is very likely we can benefit from your experience. did you encountered annoying bugs? do you think we can better arrange the layout? do you think we are missing some features critical to you? tell us in the issues.
• i can code! i wanna help 😉. wow thanks! let’s discuss your project together in the issues to get you on track!

cool. i also want to write my own email application for jmap. can you help me?

you would be pleased to know we contributes a jmap dart client that you can reuse to write your own applications. feels free to open pull requests and enrich it!