Relationships are all about what we are trying to achieve with Monica. We want it to become the best tool that helps you have a life full with love and friendships. Today's release is a great step towards this vision.
Redesign of relationships
Monica has always let you link contacts together. However this was limited to parent->child relationships, or love relationships. This wasn't the most flexible system. Starting now, you can now link contacts with many different relationship types, like uncle/nephew, coworker, mentor/protege, etc... The complete list of the possible relationships is defined here.
We've also tried to respect genders when we can. For instance, if contacts are women, we'll say "aunt" instead of "uncle", and so on. This is a real challenge for contacts who have a custom gender though. We do not support this case yet, but we are working on finding a good solution to manage this specific case.
This change was the biggest change we've made to Monica yet. Despite an extensive testing period, we had some bumps in the road while deploying this new feature, and I hope things are more stable now.
Ability to define which features you want to activate on a contact sheet
We now have an option to customize which features you want to use with your contacts. Under the Personalization tab in the Settings panel, you can now toggle features you care about. If you don't want to display the Gifts section, for instance, you can now hide it.
Journal entry date
You can now specify a date for a journal entry - allowing you to have more control over your journal.
Right to left languages
We now support right to left languages, starting with Hebrew. We'd like to thank our amazing community of translators for making this happen and their contributions to the translation process in general.
Markdown in activity comments
Markdown is a fantastic formatting tool. We were using it on a Call note, now we also use it in an activity's comment.
We are very lucky to have a great community around this project. I'd like to thank every contributor (above 100 now) who've helped by contributing to the code, every translator for their insane effort in translating the thousands of words we have in the app, every subscriber and donator for their monetary contributions. Everything helps. In a world who finally realizes how big social media platforms destroy the privacy of users and affect relationships between people, we need independent, open source projects like Monica to restore our faith in how great human relationships can be.
Version 2.0.0 is already available as a download, and is live on our hosted version.
As time passes, we’ve added more and more settings in Monica. This is against what I believe in and something I’ve tried to avoid for many years: do not pollute your software with an endless number of settings and personalization options.
A product should be opinionated and follow its own vision, at the risk of pushing back potential users. Why would people sign up for your product if it doesn’t have an unique voice or ways of doing things? My vision includes a simple, powerful product with the least amount of settings possible.
How on earth then have we added a Personalization tab under Settings?
I intend to allow personalization for things that I can’t control or decide myself. Monica is not a business tool. It’s supposed to mimic real lives of people and adapt to the unique situation of everyone. One of the mistakes I made early on was about genders for instance: I only allowed at first two genders, male and female. This was my own reality - but it wasn’t the reality of many, many people out there. Instead of deciding for my users, we’ve added the flexibility to define your own genders, that match your reality, not ours. I intend to do that for every concept that represent important aspects of our lives.
Note that settings won't include to personalize the number of elements to display on a page or any insignificant details like that. They just don't matter.
I hope that this clarifies a little bit where we are going with the personalization of the product in general.
We have received our first award: Open Source Rookie of the Year 2018, which recognizes some of the most innovative and influential open source projects launched each year. It’s great to see Monica being recognized, but the community should be recognized as well. It’s thanks to you, the community, that we are here today. You are the driving force behind this project, the reason we are building it, and you help decide what we should build next. I’m proud to be part of this adventure.
Let’s make this project a great story.
A while ago I posted this formula:
Good product design: value for users > ease of use > speed > design
I’d like to explain my reasonings behind it.
What is product design? It’s the combination of what a product does and how it does it.
Product designers have more responsibility than simply choosing how things should look or behave. They build the way users interact with the product. They need to take into account a large amount of criteria to do their job effectively. However, it’s worth asking the question of which criteria should be prioritized over others in the design process if you can’t afford to cover the whole spectrum of what constitutes a good product design practice.
The most important thing a product (or feature) should do is bring value to the user. Any other consideration comes second. Your product can be slow, ugly, not easy to use, buggy - if your work is going to help users solve a specific problem they suffer with, they will endure anything to use it. You can’t say the same thing for a beautiful product that does not bring any value: no one will use it.
Once you are sure that the product or the feature brings value, you can put your energy on creating a great user experience. This doesn’t mean making it beautiful - or even pretty. Just really simple to use or really easy to understand. Users will come to your product because you’ve promised them something - this can be summed up by either making their lives easier, or their jobs simpler. They will want to take advantage of your solution as quickly as possible and will consider your product less valuable if they can’t do what they need to in a simple way, or if it makes them feel stupid.
Once your product brings enough value and is simple to use, you will want to focus on speed. Great products are fast. They don't waste their users' precious time. The faster a product is, the more confident you feel about it. Most of the teams I’ve worked with think a feature is shipped once the code is done and the quality assurance passes. However, a feature should not be considered as complete if it’s not as fast as it could be. Your product is the sum of your features. If you start to introduce slow features here and there, the whole will suffer eventually. It will be worth less to users.
Finally, once a product brings enough value, is easy to use, and is fast, you can make it pretty if you have time left or enough money to afford this process. But it’s not necessary per se. I would go as far as saying that if something brings enough value to the user design is irrelevant. How things look is cherry on the cake. Design in itself shouldn’t be your main differentiator. It will help to differentiate your product from its competitors a little bit when you become successful, and many copycats will do exactly what you do, exactly the same way. The implication is that if your main differentiator is a matter of design, you have other problems to solve first. Design is a trend that changes often and quickly. What’s seen as beautiful today will be less valued tomorrow, just because, evaporating that advantage.
Every day, I use Monica. And every day, I wished it had a better design, had a better UX, and was faster. But I don't prioritize those aspects at all - and while it pains me a lot, I prefer creating as much value as possible first and foremost. When Monica reaches a state in which we can afford to take some time to make design better, that will mean we created a product that brings tremendous value, is extremely easy to use and fast enough for everyone. We are not there yet.
To sum up, what would you like your users to say about your work? Is it “Ok, it’s not pretty, but it’s so useful that I don't mind”, or “Ok, it’s beautiful, but I don't see why this product even exists”.
Reminders are a convenient and popular feature on Monica. Before today, they were sent the day events happen. If your goal was to buy a gift for your friend who has his birthday today, it would have been be too late to find and buy the gift. From now on, you will be reminded some time in advance that an event is coming. We call this a notification - or a reminder of reminder.
By default, notifications are sent 30 days before the event happens, then 7 days before, then the day the event happens. That way, you’ll have plenty of time to plan for whatever the event is.
Those notifications can be disabled in your Settings panel, under Personalization.
Notifications only affect monthly and yearly reminders, not weekly.
Cherry on the cake: you also now have the possibility to define the hour in the day you want to receive the reminder emails.
These new features are already in production, and will be available in v1.8.1, which will be released in a few days, if you are into running Monica on a server that you own.
Maintaining translations is really painful. I've yet to find a project where it's an easy and painless process. Until now, to translate Monica, you needed to clone the repository, update the language file and finally submit the result as a pull request. Well, no more.
Thanks to Crowdin and their generous open source program, you can now use a very simple tool to translate Monica in the language you want. The project is available at https://crowdin.com/project/monicahq and will ask you to create an account if you want to contribute. Don't hesitate to create an issue if you want to translate a language that we don't support yet.
When I launched Monica last year, I didn't realize that only offering two genders (man and woman) to identify contacts wasn't enough. We received a lot of feedback about this very specific point. The reality is that gender is not a binary option. Monica needs to represent reality, and it is more complex than what I originally thought.
This is why we are introducing the notion of custom genders. By default, each account still comes with three genders (male, female and other), but now you can customize this list, add or remove genders at will. You will be the one deciding which gender people should have. While we should be careful not to add too many options in Monica, this is a case where we need to put you, the user, in control of what your reality is.
Monica has the ability to manage gifts related to a contact. You can easily remember gift ideas for your best friend, or gifts that you've received from your grand mother that year. Now you have the ability to mark a gift idea as being offered. The section has been slightly redesigned to reflect this new feature.
A lot of other smaller additions have been recently added. We'll cover those in upcoming blog posts - but you can always read about all the changes we make on Monica on the release notes page.
When you are working every day on something, you don't take the time very often to think about the big picture. I don't want to lose sight of what I would like Monica to accomplish - so here is what I’d like to do in 2018. This post is not a roadmap per se. Think of it as my very own Wishlist.
- Launch the mobile application. The work has already started and we are close to a v1 that should ship in the coming weeks. The first version will be read only, and v2 will allow the edition of data. The code of the mobile application is already on GitHub, and is 100% open source (obviously).
- GraphQL support: we already have a REST API that the v1 of the mobile application will use. If we truly want a great mobile application, we need to make sure that all the requests made to the API are efficient and GraphQL is the best solution for this.
- Support for Carddav and Caldav. I believe this is what will make Monica shine on the long run. These two protocols will let you sync your contacts and calendar entries with your existing mail and calendar apps on mobile or desktops. Monica would become the central source of your social data.
- More love to reminders, with the possibility to be warned before an event actually happens.
- Provide statistics about your social life: how much time you went out a given month, who do you see the most, where do you hangout the most, etc… The more data you feed to Monica, the more insights you’ll have.
- A calendar view that shows reminders, future events,…
- The concept of “rich” activity sheets: for instance, if you indicate that you went to a restaurant, have the ability to set where it was (with automatic placement on a map), what you’ve eaten, how long it took, etc… Each type of activities would have specific information to fill.
- The journal should become the place where your life is auto documented. This will be great once we’ll have rich activity sheets.
- Stabilize the platform, add a lot of tests to make sure we don't break things as we move forward.
- If I have the time, but only if I do: make the app prettier. However I believe it’s more important to have a functional application than a good looking one.
- And last but not least: add more ways of importing data. This will be a real pain as, surprisingly, most social networks or systems are not open source and don't provide you with the data they have on you.
I hope to accomplish all the points above this year. I also know that things are constantly changing for a variety of reasons, so take it with a grain of salt.
Most sites these days make use of all the data they gather. Amazon recommends other articles I might like based on what I’ve already bought or consulted. Twitter, Instagram and Facebook try to suggest new friends or content I might like.
While it makes sense for a shopping website to use all the data it knows about me to help me buy better things for me, I find it extremely disturbing that social networks do that for me.
Everything social is way too personal for companies to mess up with it. They don’t have all the cards at hands to determine what those recommandations will do to me. Moreover, they think they know what we’ll want, but in my experience they are very often wrong.
The trend these days is to help users by doing all the work for them - including all the work they didn’t want the site to do in the first place.
On Twitter I don’t want to know what content other users have liked.
On Facebook I don’t want to be suggested to have more friends. I’m fine with the friends I already have - and if I’m not friends with other people it’s probably for a reason.
I don’t want this to happen on Monica. I think we need to provide a tool that does only what the users want the tool to do.
This doesn’t mean we shouldn’t provide features that help the users by analyzing their data. But these features should never be a surprise to people. And they should never give the feeling that the site knows too much about its users.