d70a57a7c9
it's not used, and so params haven't been standardized trying to unify it, it messes up overriding update in RoomView that extends it to set the timelineViewModel upon update. |
||
|---|---|---|
| doc | ||
| prototypes | ||
| scripts | ||
| src | ||
| .editorconfig | ||
| .eslintrc.js | ||
| .gitignore | ||
| icon.png | ||
| index.html | ||
| package.json | ||
| README.md | ||
| yarn.lock | ||
Brawl
A minimal Matrix chat client, focused on performance, offline functionality and working on my Lumia 950 Windows Phone.
Status
Brawl can currently log you in, or pick an existing session, sync already joined rooms, fill gaps in the timeline, and send text messages. Everything is stored locally.
Why
I started writing Brawl both to have a functional matrix client on my aging phone, and to play around with some ideas I had how to use indexeddb optimally in a matrix client.
For every interaction or network response (syncing, filling a gap), Brawl starts a transaction in indexedb, and only commits it once everything went well. This helps to keep your storage always in a consistent state. As little data is kept in memory as well, and while scrolling in the above GIF, everything is loaded straight from the storage.
If you find this interesting, feel free to reach me at @bwindels:matrix.org.
How to use
You can try Brawl here, or try it locally by running yarn install (only the first time) and yarn start in the terminal, and point your browser to http://localhost:3000.