The problem Chat App solves

The current problem we feel is that most of the chat applications are either e2e encrypted like WhatsApp or either can be accessed on multiple devices concurrently like Slack, Discord. The reason being, Private Key is stored on the device it was created and hence it is impossible to perform e2e encryption while sending message from other device if the device with Private Key is offline.

But there are usually instance when the device with our WhatsApp is offline or inaccessible for us at the moment, and we want to text something important. What we currently do in such situation is try changing the mode of communication, maybe call the person, email him, etc.

Challenges we ran into

Honestly there were and there are many problems we are stuck with. For instance:

• The IPFS HTTP Client allows adding file but the data may get deleted after 10-15 min from its cache.
• IPFS-JS allows just one node creating at a point of time.
• We don't know much about the Frontend part, and hence couldn't design a decent UI for Chat Application.
• We are naive around some of the concepts of IPFS, and hence took longer to debug.
• JavaScript in general is sometimes a pain, especially if this is your 1st time using JS after 7-8 months.