The very first PostgreSQL Graphic Tools Developer Meeting happened last week during PostgreSQL Conference Europe 2017 in Warsaw. The meeting gathered 16 developpers repesenting 14 software ( KEXI, Postico, Postgres.app, pgAdmin, DBeaver, pgCluu SQL Tabs, pg_view, bg_mon, pgBadger, pgFormatter, Postgres Professional Manager (not released yet), temBoard, PoWA, pgDevOps, ) and 10 different organizations ( EnterpriseDB, OpenSCG, PostgresPro, EggerApps, Crunchy Data, Dalibo, KDE, 2nd Quadrant, Rider Soft, Zalando )
Here’s my personal report from the meeting, you can also find a more general summary on the PostgreSQL wiki:
PostgreSQL is the best open source database ever and its community is packed with brilliant people. But there’s always room for improvements and the graphic tools is the main area where we need to focus for the forthcoming years. By “PostgreSQL Graphic Tools” I mean any software that provides a visual access to Postgres in large sense. It can be an administration tool, a monitoring tool, an installer or a reporting tool.
The meeting we had in Warsaw was a first step in this direction and it revealed 5 big issues we are currently facing
We are divided
The meeting is just a small part of the whole picture. When we prepared this event with leo cossic we identified more than 60 developers actively working on 35 different tools. This does not include the inactive projects such as PhpPgAmin and the ones we forgot (apologies to Datagrip and Elephant Shed !).
Now let’s compare this to other competitors : Oracle DBAs have
Cloud Control or
TOAD. MySQL users have
Workbench. For MSSQL
Management Studio is pretty much your only choice.
Of course open source is all about diversity, but at some point too much choice is becoming a problem. New PostgreSQL users are getting really confused by this profusion of tools and the comminty workforce is split in separate projects. All in all it is slowing down the PostgreSQL adoption.
What can we do about it ? We need to raise awareness of the community and make a better at promoting the existing solutions. The message must be clear : if you want to build a PostgreSQL administration tool, please fork pgAdmin or another one… But don’t start a new one from scratch….
We don’t talk to each other
The PostgreSQL code base is developped and maintained by a swarm of developers from all over the world, communicating constantly together… If you subscribed to the psql-hackers mailing list, you know that it’s humanly impossible to follow every discussions on a daily basis. However when it comes about graphic tools, the situation is completely opposite. There’s little discussion happening between the different developpers. Every project seems like an oasis in the middle of the desert.
What can we do about it ? The developer meeting itself is a first answer to that. We’ll try to organize a second one in 2018 (probably in Ottawa during PGCon) and hopefully we can have these kind of gathering on a regular basis in different places… We can also create other spaces to talk : a forum, an IRC channels, etc. we’ll see what we need along the way… Right now a dedicated mailing list is probably the best starting point.
We lack basic UI/UX design skills
No offense to anyone here. Developing a database management tool is hard and most of
the GUI developpers I know are primarily DBAs. Very often, they created their
software for their own need and they’re doing their best to build a nice
interface. But we’re in competition against some big companies (Oracle,
Microsoft and others) and they investing a lot in this area. Instread of tyring
to copycat competiting like
Oracle Cloud Control or
PhpMyAdmin, we need to
innovate and improve the design our tools.
What can we do about it ? If you’re a PostgreSQL company, please hire UI/UX experts and make them work with the various existing projects. If you’re a developper with some skills in design, please share your experience and your knowledge.
We don’t know our users
Among the projects presented during the meeting, very few add conducted proper User Research. In fact, most of them didn’t clearly define what is their user base. Again I’m not blaming the developpers here, but if we want to improve the PostgreSQL users experience, we need a better understanding of who our users are, what they want and how they use our software.
Waiting passively for user feedbacks and bug reports is not enough !
What can we do about it ? Again there are multiple tools and methods in the UI/UX design domain that we can learn, adapt and share : personas, user interviews, User Experience Evaluation, etc.
We need support from the whole Postgres community
psql is great. Most advanced PostgreSQL admins use it as their primary
tool. But very few people started using Postgres with
psql. Graphic Tools
are the entrypoints of our community. We should never forget that at one point
we were all just beginners and that today’s beginners are the future of our
What can we do about it ? This one is tough. It may require us to get rid
of a huge culture bias. We need to realize that improving graphic tools is
important for everyone, even for users that use exclusively the commande line.
There’s no magic formula for that, and this culture shift will probably take a while but hopefully we’ll get there.
Now What ?
This first meeting left me with many questions but also with great hopes. I am pretty sure we will see big improvements in this area in the forthcoming years.
In fact, PostgreSQL is now so feature rich that we’ve now reached a point where the new challenges are outside the database core itslef. Improving our Graphic tools is one of these future challenges and if we can gather only 10% of the community’s collective intelligence on this matter, we’re going to make great things !
blog comments powered by Disqus