@jeeshanmdphd Yes, we have an iOS app in Swift internally that we're preparing to release. We want to eventually build in React Native. We spoke to the React team and their recommended approach is to build outside of React at first and then gradually swap in components as React matures. Android, Mac and Windows natives apps are planned as well.

Thanks @cprins_! Would love to hear any feedback you have via any of our community channels at http://mattermost.org. Install guides here: http://www.mattermost.org/instal... Forum here for any questions or troubleshooting: https://forum.mattermost.org/ You can vote for and contribute new feature ideas here: http://mattermost.uservoice.com/... So glad you're taking a look, PS: If you use Docker, you can install Mattermost in one line: `docker run --name mattermost-dev -d --publish 8065:80 mattermost/platform`, and if you don't, there are step-by-step instructions here: https://github.com/mattermost/pl...

@iantien @cprins_ thats what looks more complicated the installation for day to day "normal" people. Great work improve the installation :P

@deambulando @cprins_ docker working great and within 1 minute, maybe a 1 click install for digital ocean or similar?

Hi @noahtovares Thank you for sharing about us!! We built Mattermost after getting burned by a proprietary SaaS app--and we open sourced it because we think other organizations want a self-host option: http://www.mattermost.org/why-we... Here's what's all new in Mattermost 1.0: http://www.mattermost.org/open-s... We're very glad to share it with the community, Looking forward to any questions, comments, and ideas,

@ryanjamurphy Personally I use Slack and love it, but at times you get that one paranoid client that wants total control (hmm... "placebo response"? haha) over their project data... which is where Mattermost seems like a perfect fit (as far as I can tell)

@ryanjamurphy Great question. And great "punage". I remember thinking the same thing with an Open Source Buffer App (can't recall the name). Without taking privacy and openness into account, my gut reaction is that it signifies a lot of misused talent and time going into cloning things that are already being done well and are sustained by paying customers. Are there no other problems that this time and effort could be solving instead of building an open source version of Slack....? Again, it's a simplified view, though.

@cprins_ @ryanjamurphy To add on to this, when working for large companies with a lot of private data, (like where I work now), we can't use cloud systems, so we need to be able to have a self-hosted solution.

@ryanjamurphy this happen all the time and it sparks innovation. Everybody copies being inspired by something. Slack is closed (api doesn't mean to be open anymore), they are open. Both have pros and cons and hopefully innovate faster. The time when there are patents on every single smallest button are (or should be) over. Good luck mm and slack. Both rock!