I suggest you go to the SimpleX github and read the SimpleX MQ whitepaper that details the messaging system. I know it sounds easy to you, but that's just not how it works. There's no reasonable way to integrate the two systems because they are fundamentally based on two mutually exclusive philosophies and design architectures. But it's all open source so you're certainly free to try!
Discussion
You're the only one talking about integrating the protocols. I'm talking about display options in a client.
If I have an Outlook app, that sends email, HTTP, and OATH, they don't have the mesh the three protocols together. Protocols can work in parallel. That is the standard way software is developed: multiprotocol.
I am not a Nostr dev. I am a dev. I develop products for customers.
I don't know why you're getting defensive. I am also a dev and I've spent a lot of time studying SimpleX and communicating with the lead SxC dev. I'm not saying it's impossible because that would be ridiculous. But what you're talking about is not even close to as easy as you're making it out to be. And understanding the underlying protocol and methodology is essential to understanding what you can do and how you'd have to do it. Knock yourself out.
And, like, I have an e-mail identical to my NIP-05 and a nostr:nprofile1qqsggm4l0xs23qfjwnkfwf6fqcs66s3lz637gaxhl4nwd2vtle8rnfqprdmhxue69uhhg6r9vehhyetnwshxummnw3erztnrdakj7qfqwaehxw309ahx7um5wghx26tww4hxg7nhv9h856t89eehqctrv5hsz8rhwden5te0w35x2cmfw3skgetv9ehx7um5wgcjucm0d5hsjmvd7t support e-mail. Why do I need an extra client, to look at it? Give me an e-mail plug-in, too. 😂
Like why not?
I've read the whitepaper, BTW.
I am not new to computers.