mattermost-mobile VS mattermost-webapp

Mattermost, Inc. | Senior React Native Engineer | REMOTE (US Only) | Full-Time

At Mattermost we build an open core, chat and collaboration platform focused on making users with mission critical work more productive while also allowing our customers to self-deploy and have full control over their own data.

We’re looking for a Senior React Native Engineer who has the depth to significantly move the performance needle of our app while also having the breadth to contribute across our stack.

Check out our open source mobile codebase: https://github.com/mattermost/mattermost-mobile. Meta uses the Mattermost RN app as the benchmark for performance testing of their Hermes JS engine: https://mattermost.com/blog/hermes-mattermost/. Want to set the bar for what a complex, high performing React Native app can do? Want to do it open source? Join our team!

Apply here: https://jobs.lever.co/mattermost/a38ea8f0-6c27-4178-a988-801...

I've got as far as downloading the mattermost apps: https://github.com/mattermost/mattermost-mobile/releases/tag/v2.3.0 and have been using fastlane/match but i haven't been able to build it or run it in xcode.

Mattermost has a few products/versions, i used the selfhosted enterprise version because its also MIT licensed, so free of charge and also very well documented. It may not well suited for business projects, features are build for technical teams/projects. - Features: https://mattermost.com/pricing - Deployment Options: https://mattermost.com/download/#server - Mobile Apps for both worlds: https://github.com/mattermost/mattermost-mobile An other very special app, focused on productmanagement, https://www.documize.com . Never had a scope for to use it in productive, but may match!? :)

Mattermost Beta (version 1.55.1): Secure, self-hosted workplace messaging

This was the first commit on a clean, orphaned branch on our mattermost-mobile repo. This commit kicked off the work on mobile v2. At that time — some of you may not have been born yet (or not yet born into Mattermost — which would include yours truly) — it had become clear a bit of a reset was required. Mobile v1 had grown organically, as many products have, out of a proof-of-concept. Some fundamental design decisions (like only supporting a single server, or how state management works) were foundational limitations and effectively impossible to fix iteratively. A more hard cut had to be made. Not a full rewrite per se, but close. This work kicked off inside of the mobile team, but after about a year also started to include a whole slew of engineers across the organization, as well as product and UX.

On the mobile platform end, as we’re getting closer to the mobile v2 GA we’re trying to pull our weight to shipping this thing on time. Hardcore style. We’ve now added support for announcement banners (allowing us to broadcast our new levels of extreme hardcoreness), and we will soon allow you to share how extremely hardcore fans you are of v2, with an in-app review dialog. We have also integrated Sentry, so we will have more insight into how the app is performing and when it crashes, hardcore. And last but not least, the work on a nice piece of share sheet is heading toward Android (previously only implemented on iOS).

Notes from the latest multi-product architecture sync-up. On the mobile platform end, an early look at how we’re trying to measure performance and performance regressions in the future (video). We’re closer to integrating Sentry. Search just got merged and should go out with the next (internal) beta (which should release today) — the platform team is covering this functionality with end-to-end tests.

On the mobile platform end, we’re going to try something new: a weekly mobile hangout (in the public ~Developers: Mobile channel of course, using Calls) on Mondays. The goal is to have a casual “drop in and out as you like” type of environment. Some of our mobile engineers will be there, if you like to talk about mobile development, are stuck somewhere, or would like to share your love of dynamic islands — this will be the opportunity. We’re also pushing three initiatives forward: automated performance testing (channel: ~Client Performance Automation) in collaboration with the web platform team, Sentry Integration and the “single command” installer for development environments. On the latter topic, we polled people last week. We’ll create a prototype of the “single binary” (written in Go) option.

Mattermost Beta: Open source platform for developer collaboration

I don't know about the quality, but Mattermost is in TS: https://github.com/mattermost/mattermost-webapp

On the web platform end, we merged the upgrade to React 17 (again) into master, and performed a bunch of (more minor) dependency updates while at it. We also continue our journey towards using MUI-based menus.

On the web platform end, we continue the work on menu components, found and fixed the issue that marked a whole lot of channels as unread last week (with GarphQL enabled). We’ve also been working on performance regression tests. And we’re upgrading moar dependencies.

On the web platform end, the team has been working on unifying post components (and cleaning up afterwards), more fighting with Webpack and friends in the context of the front-end part of the multi-product architecture, testing out a prototype of menus based on Material UI, and the regular cycle of dependency updates.

mattermost : https://github.com/mattermost/mattermost-webapp

On the web platform end, beside being overwhelmed by anticipation of the upcoming new joiners, we’re making good progress in getting webpack federation ready to be merged. This will be a solid step towards the multi-product architecture on the front-end. The upgrade to React 17 is also almost there. Beyond that, as mentioned, we’re fixing a few issues in GraphQL before we enable it again on community.

On the web platform end, we are experimenting with “theme weeks” as a budgeting hack to work on important but not urgent stuff. This first theme week (and this will likely be a recurring one) is focused on 🥁 performance! We’re pulling in a whole bunch of tickets accumulated over time of smaller things we can optimize for performance. Some of these improvements are already landing.

Platform involves work in many of our “highest traffic” repositories. I’m still figuring out reasonable ways how to keep up with what’s happening in the webapp, server, mobile repos as well as everything related to QA.

Most projects on GitHub have CONTRIBUTING.md file which describes how you can contribute, so you can start from there. Generally I'd say getting to meaningful contributions is very difficult for someone without real-world development experience, so if you choose to do this it won't be easy. On the other hand, this is precisely why employers prefer people who already have this experience -- it takes time and effort and not everyone makes it even with support from senior collegues.

Mattermost was the closest I was able to find and until their cloud beta finishes you have to setup a server to run them. With a Github or Google identity you are one click away from running Uclusion (and with any email several clicks) - no credit card required.