8

making a messaging app, can you guys name a feature that would be cool that you would like to have, one you must have and/or one that you would like to see in the messaging app you use?

Comments
  • 5
    Steganography
  • 6
    Single and triple backticks to enclose code.
  • 6
    Hmm, being able to see the messages on PC perhaps.. to be able to reply to messages from those oddballs who still text me over SMS without actually having to leave the comfort of my PC and its various terminal windows.. maybe an API so that it can be used to develop our own clients for other platforms 🤔
  • 7
    @Condor

    Yes yes yes. 100% internet, please. Please no SMS.
  • 7
    - e2e encryption
    - open source
    - no data collection (behavioral & meta)
  • 4
    @PonySlaystation i'm planning on making the client open source but not the server
  • 2
    Nicknames, changing chat colours and chat emojis
  • 3
    Encryption p2p
  • 3
    Markdown for sure
  • 2
    Stickers
  • 3
    Regarding what's missing from my two most used messangers - telegram and skype4business - feature of grouping people/groups/channels to separate nested folders, proper handling of long messages (skype sucks at it), basic markdown formatting, possibly to disable the markdown formatting, nice presentation of attachments, having single conversation across multiple devices (skype sucks at it, two laptops, two different chats but the other party sees one), forwarding and replying to certain messages...

    But, being honest, why do you want to make another IM and not join any already existing? Telegram already has great client app and most of the requested features. Diaspora is nice and open source and actually needs developers. You can set your own hub and make it commercial if you wish to.
  • 0
    @mt3o grouping - thank you!
    markdown i don't have any intention of supporting, the rest of the features you stated i plan to/have implementd
  • 0
    @calmyourtities markdown is useful if you plan on using it professionally. Try using any bullet list or just simple bold/pre.
    If you want to provide source code formatting, it's worth to consider being markdown-compliant. For example JIRA is not, and working with the formatting is a pain.
    Pasting anything that has formatting into s4b is a nightmare (think of using wysiwyg in ie6 in the old days).
    Do i have to mention that closing yourself on developers (and they eventually want to share source code) is a bad idea? :D
  • 0
    Disabling sending messages when u drunk xd
Add Comment