Separate noisy chat from writing down facts and stuff you would like to be able to access later on (try this in a WhatsApp-Chat or Slack-channel).
51 karma · joined September 10, 2015
Separate noisy chat from writing down facts and stuff you would like to be able to access later on (try this in a WhatsApp-Chat or Slack-channel).
- Profitability: We have plans for paid features which are not yet available at this point (kind of micro transactions per jaypad).
- Digital Sustainability (Guaranteeing that the user can use it in the future): To be honest, none. This product is still in beta and as long as it has no sustainable funding it will not have the other one too.
- Interop with other platforms: None at the moment, but we have plans that users can write their own modules for the clipboard side of the jaypad which will open a whole new universe of interop with other things (kind of like Slack-Bots with GUI).
- Privacy: You have the link you have access. It's that simple. But one of the planed paid features is privacy related (no access without invitation, read/write restrictions, private areas, etc.).
Spoiler: The state is stored in a GenServer.
- your next side project - a weekend trip - a bachelor party - a startup - …
We just ended our closed beta phase and we are looking forward to your feedback and thoughts.
The whole thing is still very early and I would be glad to hear some thoughts on this or what use cases you come up with.
Btw the backend is written in Elixir/Phoenix which is just a blast and you should try it out if you're a web developer :-)
We have actually talked not only to potential users (a lot) but potential customers (a lot as well) to validate the basic need of enhanced website communication possibilities before we went on the build Talk About Jack. The need for chat communication especially in eCommerce (as well as general customer support) is growing and continually demanded by online customers (of our potential customers).
And yes you're right: people are mean on the internet. We have some (not yet implemented) ideas to handle this issue as well, but we wanted to give people a chance first.
Thank you for sharing your advice and experience with us. We will keep it at heart and greatly appreciate you taking the time to look into our product and the idea behind it.
Even if you do not know Rails you should give it a shot. But if it somehow does not fit your needs please come back and let me know. I'm sure there's something out there.