We have been working hard, and we are super-proud to announce that the DMMapp 3.0 is out there and available for everyone to explore and enjoy!
“It’s the best DMMapp yet!”
“It just works!”
“10/10 would DMMapp again”
No they don’t, but we like to imagine they do! Let’s go and see what has happened in the past months.
What has Changed in the DMMapp? And Why?
What we wanted to address in this release were two things: maintainability and usability of the DMMapp.
We’ll start with the latter: the DMMapp 2.0 worked fine; but “fine” was not good enough in our opinion.
We believed that there was no need for two different tabs , but rather we thought that there should be a single tab where the user could choose what to see and explore. In our vision, the data and the map should have been in a single page, interacting with each other. Furthermore, we considered the filtering tool inadequate and rather clunky.
With these two problems in mind, we went to work: we implemented an omni-search box that replaced the old, clunky, filtering method: just type any text in the search box, and the app will start filtering instantaneously the results as you type: Searching for libraries in “London”? Type it in, and magically the list will display only the libraries from that city. Want to know which libraries are from Italy? Type “Italy”, and ta-daah! – only the libraries in Italy are displayed.
That took care of the filtering, but what about the “Single tab” dream? We addressed that too: The table interacts with the map now!  After you find the library you want to browse in the table, you tap on the table and you will be taken to the map. The link to your library will appear, zoomed in and highlighted, on the map. All that is left to do is tap the button and off you go to the manuscripts from the institutions you chose!
If you simply want to browse the map you can still do that too!
Back Office stuff
This is the boring part of the post which involves the technical stuff; the “maintainability” mentioned above.
Essentially we had to do the same work, twice, per each link we wanted to add to the app.
The front-end worked, and it looked good, but the core was a bit rotten in our view.
We knew the whole process could be optimized: the map and the data have mostly the same technical details; they could come from the same origin point. “Could” became “MUST” in the end.
The only way to do this, in our eyes, was to redesign the whole DMMapp, dropping Google Fusion Tables entirely in favor of an code-only solution (HTML, JS, JSON, CSS.) So we got to work again.
This resulted in a super-light, lean, and quick app, which is also easier to manage and update. A win-win situation for both the users and the Sexy Codicology team! If you are interested in how we coded exactly, please go to our Github page, you will find all our code there.
Now, we simply have to add a line in the JSON code whenever we receive the link to a new library, and query the JSON code to monitor for broken links in the app! Awesome!
All in all we are very satisfied of how the app turned out and we hope you will make some awesome discoveries in the medieval manuscripts’ field while using it!
Enjoyed this piece? Take a second to support Sexy Codicology on Patreon and keep us writing!Become a Patron!
Our fine selection of books about codicology and medieval manuscripts
References & Footnotes [ + ]
|1.||↟||“Data” tab, and the actual “map”|
|2.||↟||Datatable and Google Maps simply didn’t like each other. Google Fusion Tables is also a non-Mobile Friendly solution. A good 15% of the traffic to the app happens via mobile devices|
|3.||↟||Read: “We didn’t know how to code well enough”|