mattermost-mobile VS Sandstorm

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

Sandstorm really had this kind of feeling. Not that it presented as a desktop environment visually - but it offered a much more integrated “computer” of documents versus silod web site apps where you need to open each site to see the files in the app. https://sandstorm.io/

RemoteStorage https://remotestorage.io/ seems to be trying to do this too

I also really like the https://sandstorm.io approach which goes a little farther beyond

They tried, it was called sandstorm https://sandstorm.io/

I did read from somewhere, that with Wordpress SEO plugins etc some website got to top of search results.

Those that did website with other tech did not get same results, and thinked how to compete or survive.

For security, I use Sandstorm https://sandstorm.io fork of WordPress that generates static websites. But that does not work with some interactive plugins.

Urbit made the choice to use a bunch of silly new words for familiar concepts, not because they were inventing something so new that there were no words to describe it, but because they wanted to fool people into thinking that's what they were doing. Actually they just spent 10 years trying to do https://sandstorm.io/, but made it 10 times harder than it needed to be by coming up with a wacky new set of programming languages with silly names for everything.

That's funny, and it is OK to make fun of it.

I don't work at Cloudflare but follow their work and occasionally work on performance sensitive projects.

If I had to guess, they looked at the landscape a bit like I do and regarded Cap'n Proto, flatbuffers, SBE, etc. as being in one category apart from other data formats like Avro, protobuf, and the like.

So once you're committed to record'ish shaped (rather than columnar like Parquet) data that has an upfront parse time of zero (nominally, there could be marshalling if you transmogrify the field values on read), the list gets pretty short.

https://capnproto.org/news/2014-06-17-capnproto-flatbuffers-... goes into some of the trade-offs here.

Cap'n Proto was originally made for https://sandstorm.io/. That work (which Kenton has presumably done at Cloudflare since he's been employed there) eventually turned into Cloudflare workers.

Another consideration: https://github.com/google/flatbuffers/issues/2#issuecomment-...