We frequently ship new versions of both the JS and compiled Haskell, and it was painful for our users to manually download and reinstall the application. As more people used Wagon, we wanted to update the code silently in the background, deploy to Windows and Linux, and move away from WebKit (we <3 Chromium’s dev tools!). We soon shipped our first Mac app: a download-able, double-click-able version using MacGap. The earliest alpha of Wagon was a command line program that powered a browser app available at localhost. We want a capable desktop application with the ease of developing for the web. Our CTO Mike described Wagon’s technical architecture: a Javascript application for user experience along with a native process for database connections and streaming data computation. Electron was carved out of the Atom editor project and lets us deploy web UIs to the desktop. Early adopters including Slack, Atom, Quip, Visual Studio, Spotify, MapBox, Front, and Nylas have found ways to weave these once unrelated approaches.Īt Wagon, we’re using Github’s Electron (previously “Atom-Shell”) as our underlying app framework. The standard web browser won’t suffice, so what should we do?Īs many companies are discovering, mixing web and native technologies is very compelling. Unfortunately, browsers can’t connect directly to databases and aren’t optimized for processing millions of data results. Our users want Wagon to connect securely to their database and analyze large amounts of data, while being easy to setup and always up to date. While building Wagon, we’ve encountered a few engineering challenges that aren’t easily solved in the browser.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |