CoralJam is a real-time collaborative whiteboarding application, with inspiration provided by FigmaJam.
This application is deployed to http://coraljam.vercel.app
These instructions will get you a copy of the project up and running on your local machine.
git clone https://github.com/kmcclosk/coraljam.gityarnyarn startWhen you start the application using yarn start your browser will open to http://localhost:3000.
CoralJam starts with a welcome screen where you enter your username. After entering your username you are taken to the main whiteboard application. The whiteboarding application offers a set of tools: notes, stickers, and freeform text. Clicking a tool will place an instance of the tool onto the main whiteboard screen. You can interact with the tool by moving it around.
To see the real-time collaboration features of the CoralJam application, launch a new tab in the same browser or another browser. In this new tab, navigate to http://localhost:3000. Enter a different username and click Enter. Within the whiteboard all items are shared by all users.
CoralJam is a React application built using the NextJs framework. Syncing of data between all open instances of the application is handled using the SyncedStore library, which uses Yjs as a CRDT library. Network communication is handled by WebRTC which is peer-to-peer. No local signalling server is required, since the underlying y-webrtc library uses public signaling servers.
Code written for this system was optimized towards features against the 8 hour timebox. When possible, existing packages were used to provide functionality to speed development. In a true production app, using out-of-the-box packages to provide functionality may be suboptimal from a performance standpoint and needs to be decided on a case by case basis. Emphasis on delivering an MVP meant optimizing time away from unit testing, linting, and Typescript, which are not part of this repo. An early decision was made to have this application be real-time collaborative, resulting in the choice the SyncedStore library. The SynchedStore library uses a proxy model akin to MobX. Mixing MobX type reactive proxies with other ways to manage state is perhaps suboptimal. A unified model of state management would have been pursued if given more time.
In general the pattern used through this app is "contextualized components" which depends entirely on context for state and only utilize props to express variant behavior and appearance or to otherwise effect how the state is used. This avoids a large global state object and facilitates component composibility. Contextual state allows for dynamic scope Additionally, contextual state naturally ties together state with component lifecycles such that the global state object doesn't need to be redundantly signalled that data is no longer needed. Use of context can also produces a better dependency graph. A example of this is exposing the logging library through context as opposed to importing a logger into various files, thereby turning a static import into a runtime subsystem.
It is noted that FigmaJam utilizes an HTML canvas and wasm. It would be interesting to explore those architectural decisions to determine an optimal technology appraoch for a whiteboard application.
- When joining a whiteboard as an additional user, the first drag of an item mistracks. Dropping the item and redragging fixes the issue.
- The drawable canvas of the whiteboard does not share data accross users.
- This application is optimized for desktop only. The CSS was not tested on mobile and TouchEvents are not supported.
- Loading of CSS such as fonts is suboptimal and results in jank.
- Saving is not supported. Reloading the main whiteboard page returns the user to the login screen and all whiteboard work is reset.
- All users share a single shared whiteboard session for all users, there is no way to create additional sessions.
- useMemo and useCallback are used sparingly potentially resulting in redundant renders.
- CSS is basic. i.e. Flex is used, perhaps Grid is more appropriate.