Transparency, accountability and open government are huge themes for African citizens as the number of internet and mobile phone users jump up across the continent. People are connecting and realising that the internet provides them with a quick and easy way to engage with politics, be that via social media or citizen engagement websites.
One group have just launched a parliamentary monitoring platform for Zimbabwe using our Pombola platform. We helped them with the original set up, some small technical issues and some general platform advice, but KuvakaZim has only gotten to launch due to the huge dedication and work of its founders, Regina and Peter.
“The KuvakaZim project was born from a general concern regarding the accountability and activities of Zimbabwean Members of parliament and their duties in regard of their representative role,” Regina Dumba, lead volunteer of the project, tells the world in her press release.
“Many articles, books and studies have explored the issue of good governance in African countries and how it relates to transparency, accountability, and Government performance. Knowing the causes and effects of these plights, we believe it is now time for action in Africa and in Zimbabwe. Until we start putting words into action, only then can we rebuild our country.” She continues on the KuvakaZim blog.
Creating the site.
Regina, Cleopatra and Peter, who has been volunteering technical skills for the project, contacted mySociety in July after being inspired by Kenya’s Mzalendo. Since then they have been working tirelessly to gather MP data and information on constitutional rights, how democracy works in Zimbabwe, electoral law and political parties. The site now allows Zimbabweans to learn more about how their government works, as well as the duties of their MP and whether they are carrying these out. This has been especially timely because of the recent elections on July 31, 2013.
That’s not to say that the site has got to this stage without any hitches however..
It’s been difficult to find official boundary data for Zimbabwe, which means we haven’t yet managed to load an MP look up onto the site. The hope is that this will come in the future, along with other features such as Hansard and the potential to write to your politician.
Despite this the team have managed to gain some on the ground volunteer support and launch the site this week. If you want to learn more about KuvakaZim the check out their blog and their twitter stream. We’ll be following their progress too!
Image credits: Patola Connection by Whologwhy | Hands up by Pim Geerts | Bend in the Road by Andrew Ashton | All Creative Commons licensed photographs. Thank you for making your content creative commons.
Uruguay has one of the most successful e-government initiatives in Latin America. The president supported the development, a generous budget was made available and international cooperation was welcomed. Despite this fact, and an access to information law passed in 2008, up until 2012 there was uncertainty and resistance on the part of the government, both to responding to FOI requests and to accepting e-FOI requests.
All of this changed with the launch of Qué Sabes, a freedom of information requesting platform using the Alaveteli code created by mySociety. For DATA, an organisation working towards more online open government in Uruguay, this allowed them to change laws on email requests. For mySociety, it’s further proof that our platform can be adapted to any jurisdiction, language, and geography by any organisation with some small technical ability.
In the beginning…
To DATA it was obvious that the authorities shouldn’t get away with ignoring requests made by email. Fabrizio Scrollini, one of DATA’s co-founders tells us, “In 2012 at the University of Oxford a group of activists took part in a conference on access to information hosted by British NGO mySociety.” The conference demonstrated the success of online FOI platforms in other countries, so why not Uruguay. This meeting of minds inspired Fabrizio and Gabriela Rodriguez, a software engineer for DATA, to make the leap and create their own FOI platform.
But was mySociety’s code difficult to implement? “Over a week (with some sleep deprivation) the first prototype was ready to go and was quietly online.”
“The platform decision was based on very basic criteria about technology support and usability,” Fabrizio says. “In terms of technology the team looked for relatively clean code, Open Source software, and a community that could support long term work. By that time, Alaveteli was the only software doing the former.”
It also helped that there was an existing Spanish Alaveteli platform up and running from another mySociety partner, TuDerechoASaber, which made translation of the website components easier.
What was the most challenging?
According to DATA, the biggest challenge was collecting data from the government, something that they were best placed to do alone. This was anything from email addresses to finding out if the information they had gathered was out of date.
“The Uruguayan state is not a small one (albeit the country is small),” Fabrizio tells us. “And email [addresses] were not easily available. We made use of an official agenda of authorities (in closed format) to get the first emails.”
Collaboration with other local, sometimes non-technical, NGOs was also key. “Present[ing] a united front [...] solve[d] the crucial issue of making the site work.” It was also crucial in pushing the authorities to accept email freedom of information requests as a valid legal format.
Launch and results
Qué Sabes launched in October 2012 with significant local and international publicity, thanks to DATA’s coordination with both Latin American and European NGOs.
Currently the site has had 228 requests sent through it. Its sister site WhatDoTheyKnow, launched by mySociety four years previously, has over 160,000 requests, which shows the possible growth for a site of this kind.
But for DATA, the biggest result has to be influencing a change in the law. “In January 2013,” writes Fabrizio, “after 170 requests were filed online and [with] significant public pressure, [the] Uruguayan authorities conceded that online access to information requests are legal. Access to information is now a right that Uruguayans can exercise just by sending an email.”
So what have DATA taken away from the process?
“Setting up a website such as Qué Sabes involved a significant amount of [non-technical] time and effort.” We at mySociety, as much as we may want to, are not in a position to support these sites with grants, only technical help and practical advice. “An initial group of 5 highly motivated (DATA) volunteers went from installing the software to launching it, covering several areas such as programming, legal expertise, communication and policy issues.”
The volunteers are essential. Fabrizio tells us, “We hope to organise them so eventually they can run the website and provide support to each other. [...] Yet the crucial point has been made: the state has to answer FOI requests through email in the 21st century.”
Uruguay, Montevideo 1970s public transport plate by woody1778a CC BY-SA
Frightening elevator sign in Hotel Palacio by Chris Hamby CC BY-NC
Need FixMyStreet for your own council? Find out more here.
It’s known for being one of the cleanest and most efficient cities on earth – but even Zürich suffers from potholes and graffiti.
Zürich’s residents can now report infrastructure faults via their city council’s own dedicated installation of the FixMyStreet platform: Züri wie neu, which translates as ‘Zürich: Good As New’.
For Zürich, it’s a new online channel for its infrastructure reports. Meanwhile, for mySociety it’s further proof that our platform can be adapted to any jurisdiction, language, and geography.
We spoke to GIS Project Managers Tobias Brunner and André Graf about the process of installation, and whether or not the launch has been a success.
How it all began
“The project came about as the result of a government competition,” explains Tobias. “Through the eZürich vision, they solicited ideas that would help the city use ICT (Information and Communications Technology).
“FixMyZürich, as the idea was initially presented, was one of the top three suggestions. It clearly matched the competition’s stated aims of increasing transparency and modernising communication channels. Plus there was a strong likelihood that it would also increase civic participation and improve the image of the council – wins all round.”
But Switzerland has a reputation throughout the world for being spotless and efficient – and could Zürich, which ranks second in the world for high standard of living, really have any problems to report?
There was definitely a fear that the service would barely be used. Only after launch would they see whether that fear was justified.
Prior to this, Zürich didn’t have an online channel for infrastructure fault reporting: citizens had to use phone, email, or even fax if they wanted to tell the council about a problem in their community. So it was high time for modernisation. eZürich’s winning entry had mentioned the UK platform FixMyStreet, and so Zürich was well aware of mySociety’s custom software.
They assessed other systems. But a number of factors led to the decision to go with FixMyStreet, rather than either buying a different option, or building a system themselves.
Firstly, says Tobias, “It’s simple! And after the design revamp, it looks stunning.” And then, “mySociety was able to adapt the software to our specific needs, which is very customer-friendly.” And finally, “mySociety has a lot of experience in the field, which also persuaded senior council decision-makers.”
Adapting to Zürich’s needs
To complicate matters, each department had its own incident management system – and in fact they still do. In order to get the pilot scheme up and running, Züri wie neu has had to be a standalone system, although eventually the dots will be connected and a unified system will be introduced.
Anyone familiar with the original version of FixMyStreet will immediately notice one big difference with Züri wie neu – the maps. They’re satellite, unlike the Ordnance Survey maps that our UK users know and love.
“People are used to Google Maps,” says Tobias. “We have nice orthophotos [aerial photographs that are geometrically corrected to show uniform distances]. This way, people can view more details, like trees or landmarks, and therefore will hopefully be able to better locate their problem”.
There are less obvious differences, too. For example, users of the original UK FixMyStreet are required to confirm their reports by clicking on an email link. In Zürich, not so. In fact, all reports are verified on the council side: “We didn’t want to let any reports slip by!” That’s admirable commitment.
With mySociety in one country, and our clients in another, there was always going to be a degree of collaboration from a distance. For mySociety, this isn’t so unusual: many of us work from home habitually, and we have all the tools in place for co-coding, shared documentation, and instant communication.
All the same, there were several additional keys to making sure the process went smoothly:
“A lot of email contact and feedback. Feedback from mySociety was really swift – way faster than what we’re used to from Swiss companies!”
And it was invaluable that there were two face to face meetings at crucial points in the development process. Here’s how it went, according to Tobias:
“First, a lot of talk with council members and other responsible people. Then, even more talks!”
“After that, we provided firm requirements for mySociety to implement. There was a lot of testing throughout. And we provided detailed feedback to mySociety about each implementation sprint.”
The process was not entirely without challenges: for example, we needed to build the accompanying app from scratch, which of course added to development time. And Tobias reckons that another face to face meeting would have been useful, especially as regards the app.
Züri wie neu attracted a real blaze of publicity – clearly, this was an idea whose time had come in Switzerland.
“The media went crazy. Every newspaper in Zürich reported the story. Even European television picked it up. Even now, a month after the launch, the media is still covering us”.
Of course, the outcomes are the important part. We saw at the beginning that Zürich’s main aim was to increase transparency and modernise communication channels. We are sure that all councils are also keen to cut costs and increase efficiency.
In the first month after launch, there were 600-900 reports. Zürich’s population is approximately 400,000: comparable to Reading in the UK, and somewhere between Leicester and Bristol. Zürich’s report rate is way in excess of what we see in any of those cities – but it’s early days for this project, and we expect the number of reports to settle down somewhat as the launch publicity subsides.
It’s interesting to hear that Tobias and André reckon the users of the website are ‘new customers’ – people who never would have been in touch before. You can argue whether that creates extra work, or increases efficiency as more faults are reported that would never previously have been fixed.
Meanwhile, feedback from Zürich residents has been overwhelmingly positive. Zürich council themselves are pleased: their next step is to look into adapting the FixMyStreet system so that it can be used by internal departments too, and, significantly, they are in discussion with other councils across Switzerland.
The final analysis
Would André and Tobias recommend FixMyStreet to other councils, including those abroad?
“mySociety were great. They were always very kind, and they brought a large amount of input from their previous experience. We’d definitely recommend them.
“Working in different countries turned out not to be a problem – so long as someone in your organisation speaks English. But I would definitely say that meetings are vital.
“As an extra plus point, you also gain knowledge about English culture – comic shops, real ale, all that sort of thing!”
We’re not going to guarantee a crash course in comics and beer, but we can promise a street fault reporting system that will suit your needs. Get in touch to find out more.
Photo by Clemens v. Vogelsang (CC)
If you’ve been following mySociety for a while, you’ll know that we have been interested in making maps that show commuting times for several years.
However, we’ve never made public a simple, free, useful version of our slidy-swooshy Mapumental journey times technology. Until today.
Today we pull the wraps off Mapumental Property , a house-hunting service covering England, Scotland and Wales, designed to help you work out where you might live if you want a public transport commute of a particular maximum duration. Have a go, and we guarantee you’ll find it an oddly compelling experience.
We think it’s a genuinely useful tool – especially since unlike some of the other players in this space, we’ve got all the different kinds of public transport, right across the whole of Great Britain. We hope that some of you will find it helpful when deciding where to live.
However, this launch doesn’t mean mySociety is bent on taking over the property websites sector. Mapumental Property isn’t a challenger to the likes of Rightmove, it’s a calling card – an advertisement for our skills – which we hope will help mySociety to attract people and organisations who want beautiful, useful web tools built for them.
In particular we’d like people interested in Mapumental to note that:
- We like to build attractive, usable web tools for clients of all kinds.
- We know how to use complex data to make simple, lovely things.
- We can do some mapping technology that others haven’t worked out yet.
If any of that is of interest, please get in touch, or read about our software development and consulting services.
I’d like to thank quite a few people for helping with this launch. Duncan Parkes was the lead developer, Matthew Somerville ably assisted. Jedidiah Broadbent did the design. The idea originally came from the late Chris Lightfoot, and me, Tom Steinberg. Francis Irving built the first version, and Stamen came up with the awesome idea of using sliders in the first place (and built some early tech). Kristina Glushkova worked on business development, and Zoopla’s API provides the property data. I’m also grateful to Ed Parsons of Google for very kindly giving us a hat tip when they built some technology that was inspired by Mapumental. Thanks to everyone – this has been a long time coming.
We’ll follow up soon with a post about the technology – and in particular how we got away from using Flash. It has been an interesting journey.
Today sees the official launch of FixMyStreet’s open source codebase as a proper tool that we hope people will want to deploy in cities and countries around the world. It is based on FixMyStreet.com which we believe is the most usable, most mature street problem reporting tool in the world, but which is only available to British users.
We’re shouting about this launch a bit because we need your help to make the service ever better. First, we need feedback from programmers about whether we’ve got the install process right – whether it’s as easy and clear as we want it to be. And for non-coders who want to get involved, we want to ask for help with the process of translating the site’s text into different languages.
Over the years there have been many copies of FixMyStreet set up in many countries, often using the site’s original name, but always written by developers from scratch. We’re delighted to have inspired people, but all too often the people trying to build copies have stumbled as they realise just how hard it is to build a tool like this with the polish that users expect. We think that people everywhere would be better off if they could have a local FixMyStreet that was really usable, and really connected to the right people.
So we’re very happy to be able to open up a codebase that has been extensively modified in the last year, to help users around the world manage easy, successful deployments. Steps we have taken include:
- Putting the translation text into Transifex, so that non-technical translators can get started whenever they feel like it
- Developing Amazon Machine Images so people who want to tinker can get started in the minimum possible time
- Rewriting the entire codebase in order to make it a less confusing installation
- Building a global version of our MapIt political boundaries web service, so you can get going without having to wrestle administrative data out of your government before you get started.
Plus with the help of the wonderful OpenStreetMap, you can get maps without licensing hassles too.
Calling it version 1.0 is our way of saying two things. First, that the tool still has a lot of evolution left to do, and a long way to go before it is as good as we want it to become. But more ambitiously, calling it 1.0 is also our way of saying that it’s no longer just a codebase dumped into Github. It’s a real open source project, which we plan to support, and which we hope will make a real difference in the lives of ordinary people. Check it out.
One of the projects we’ve been working on at mySociety recently is that of making it easier for people to set up new versions of our sites in other countries. Something we’ve heard again and again is that for many people, setting up new web applications is a frustrating process, and that they would appreciate anything that would make it easier.
To address that, we’re pleased to announce that for both FixMyStreet and MapIt, we have created AMIs (Amazon Machine Images) with a default installation of each site:
You can use these AMIs to create a running version of one of these sites on an Amazon EC2 instance with just a couple of clicks. If you haven’t used Amazon Web Services before, then you can get a Micro instance free for a year to try this out. (We have previously published an AMI for Alaveteli, which helped many people to get started with setting up their own Freedom of Information sites.)
Each AMI is created from an install script designed to be used on a clean installation of Debian squeeze or Ubuntu precise, so if you have a new server hosted elsewhere, you can use that script to similarly create a default installation of the site without being dependent on Amazon:
In addition, we’ve launched new sites with documentation for FixMyStreet and MapIt, which will tell you how to customize those sites and import data if you’ve created a running instance using one of the above methods.
These documentation sites also have improved instructions for completely manual installations of either site, for people who are comfortable with setting up PostgreSQL, Apache / nginx, PostGIS, etc.
Another notable change is that we’re now supporting running FixMyStreet and MapIt on nginx, as an alternative to Apache, using FastCGI and gunicorn respectively.
We hope that these changes make it easier than ever before to reuse our code, and set up new sites that help people fix things that matter to them.
Photo credit: duncan
Since its launch in 2005, WriteToThem has always covered all parts of the United Kingdom, and the Northern Ireland Assembly was the first body added to TheyWorkForYou after the UK Parliament, in late 2006. So whilst we certainly have not ignored Northern Ireland, it had always been an irritant of mine (and a cause of infrequent emails) that FixMyStreet only covered Great Britain.
This was due to the way it had originally been funded and set up, but those issues were in the past, due to a myriad of changes both internal and external, and it was now more a case of being able to find the resources to implement the necessary work. Late last year, mySociety worked with Channel 4 on the website for their series of programmes on The Great British Property Scandal. This used, in part, code similar to FixMyStreet to let people report empty homes, and it was required to work in all parts of the UK. So as part of that process, code was written or generalised that let aspects of FixMyStreet like the maps and place name lookup work for Northern Ireland locations.
It’s taken a few months since then to allocate the time, but we’ve now been able to take the code written back then, add various other bits, and incorporate it into FixMyStreet – which now covers the 26 councils of Northern Ireland, and the central Roads Service. Issues such as potholes, graffiti, and broken street lighting can be reported to Antrim or Newry and Mourne as easily as Aberdeen or Wyre Forest, and just as in the rest of the UK you can sign up for alerts based around your location or to your council.
All of us at mySociety love the fact that there are so many interesting new civic and democratic websites and apps springing up across the whole world. And we’re really keen to do what we can to help lower the barriers for people trying to build successful sites, to help citizens everywhere.
Today mySociety is unveiling MapIt Global, a new Component designed to eliminate one common, time-consuming task that civic software hackers everwhere have to struggle with: the task of identifying which political or administrative areas cover which parts of the planet.
As a general user this sort of thing might seem a bit obscure, but you’ve probably indirectly used such a service many times. So, for example, if you use our WriteToThem.com to write to a politician, you type in your postcode and the site will tell you who your politicians are. But this website can only do this because it knows that your postcode is located inside a particular council, or constituency or region.
Today, with the launch of MapIt Global , we are opening up a boundaries lookup service that works across the whole world. So now you can lookup a random point in Russia or Haiti or South Africa and find out about the administrative boundaries that surround it. And you can browse and inspect the shapes of administrative areas large and small, and perform sophisticated lookups like “Which areas does this one border with?”. And all this data is available both through an easy to use API, and a nice user interface.
We hope that MapIt Global will be used by coders and citizens worldwide to help them in ways we can’t even imagine yet. Our own immediate use case is to use it to make installations of the FixMyStreet Platform much easier.
We’re able to offer this service only because of the fantastic data made available by the amazing OpenStreetMap volunteer community, who are constantly labouring to make an ever-improving map of the whole world. You guys are amazing, and I hope that you find MapIt Global to be useful to your own projects.
The developers who made it possible were Mark Longair, Matthew Somerville and designer Jedidiah Broadbent. And, of course, we’re also only able to do this because the Omidyar Network is supporting our efforts to help people around the world.
From Britain to the World
For the last few years we’ve been running a British version of the MapIt service to allow people running other websites and apps to work out what council or constituency covers a particular point – it’s been very well used. We’ve given this a lick of paint and it is being relaunched today, too.
MapIt Global is also the first of The Components, a series of interoperable data stores that mySociety will be building with friends across the globe. Ultimately our goal is to radically reduce the effort required to launch democracy, transparency and government-facing sites and apps everywhere.
If you’d like to install and run the open source software that powers MapIt on your own servers, that’s cool too – you can find it on Github.
About the Data
The data that we are using is from the OpenStreetMap project, and has been collected by thousands of different people. It is licensed for free use under their open license. Coverage varies substantially, but for a great many countries the coverage is fantastic.
The brilliant thing about using OpenStreetMap data is that if you find that the boundary you need isn’t included, you can upload or draw it direct into Open Street Map, and it will subsequently be pulled into MapIt Global. We are planning to update our database about four times a year, but if you need boundaries adding faster, please talk to us.
If you’re interested in the technical aspects of how we built MapIt Global, see this blog post from Mark Longair.
Commercial Licenses and Local Copies
MapIt Global and UK are both based on open source software, which is available for free download. However, we charge a license fee for commercial usage of the API, and can also set up custom installs on virtual servers that you can own. Please drop us a line for any questions relating to commercial use.
As with any new service, we’re sure there will be problems that need sorting out. Please drop us an email, or tweet us @mySociety.
As you may already be aware, mySociety is putting considerable effort into making it super-easy to set up versions of our websites FixMyStreet and WhatDoTheyKnow in other countries.
These ‘websites in a box’ are a key part of our strategy to help people develop more successful civic and democratic websites around the world, but they are only the first half of our plan. Today I wanted to talk about the other half.
There are some use-cases for software in which most people are entirely happy to take some software off the shelf, press ‘Go’, and start using it. WordPress is a good example, and so is Microsoft Office.
However, there are some kinds of social issues that vary so much between different countries and regions that we believe one-size-fits-all tools for attacking them are impracticable.
This problem is particularly acute in the arena of sites and apps that allow people to track the activities of politicians. In this area there are several dozen different sites globally, almost all of which are powered by software that was written bespoke for that particular usage.
What drives this pattern of people re-writing every site from scratch is that people in different places care about different aspects of politics. In some countries what really counts is how politicians vote, in others the crux is campaign finance contributions, in others it is information on who has criminal records, and in others still it is whether public money has been vanishing suspiciously.
To build an off-the-shelf software platform that could handle all this data equally well in every country would be an immense coding task. And more important than that, we believe that it would create a codebase so huge and complex that most potential reusers would run away screaming. Or at least ignore it and start from scratch.
In short – we don’t believe there can be a WordPress for sites that monitor politicians, nor for a variety of other purposes that relate to good governance and stronger democracies.
We believe that the wrong answer to this challenge is to just say “Well then, everyone should build their own sites from scratch.” Over the years we at mySociety have been witness to the truly sad sight of people and organisations around the world wearing themselves out and blowing their budgets just trying to get the first version of a transparency website out the door. All too often they fail to create popular, long lasting sites because the birthing process is just so exhausting and resource-consuming that there’s nothing left to drive the sites to success. Often they don’t even get to launch.
A painful aspect of this problem is that the people who work on such sites are genuine altruists who are trying to solve serious problems in their part of the world; too much of their passion and energy is used up on building tools, when there’s still so much work beyond that that’s needed to make such sites successful. However, as we pointed out above, giving them a complete package on a plate isn’t an option. So what can we do?
Our Proposed Answer – The Components
We start from the following observation: coders and non-coders like simple, minimal, attractive tools that help them achieve bigger goals. Simple tools don’t make anyone run away screaming – they encourage exploration and deliver little sparkles of satisfaction almost immediately. But simple tools have to be highly interoperable and reliable to form the foundation of complex systems.
Our plan is to collaborate with international friends to build a series of components that deliver quite narrow little pieces of the functionality that make up bigger websites. These include:
- PopIt – A Component to store and share the names of politicians, and the jobs they have.
- MapIt – A Component to store and share information on the locations of administrative boundaries, like counties, regions or cities.
- SayIt – A Component to store and share information on the words that public figures say or put out in writing.
There will be more, possibly many more. Our goal is to radically collapse the time it takes to build new civic and democratic (and possibly governmental) websites and apps, without putting constraints on creativity.
Characteristics of each Component
There are some crucial architecture decisions that have been baked into the Components, to truly make them ‘small pieces loosely joined’.
- Each Component is fundamentally a tool for storing and sharing one or two kinds of common data – they’re intentionally minimalist.
- As a developer, you just use the Components that make sense for your goals – you simply don’t have to look at or learn about the Components that contain functionality that doesn’t matter to you.
- You don’t have to install anything to get started – you can always begin by playing with a hosted Component.
- We won’t impose our taste in programming languages on you. You can code your website in whatever language you want. The Components are not ‘modules’ - they don’t plug into some overarching framework like Drupal or WordPress. They are stand-alone tools which just present you data over REST APIs, and which you can write data into using REST APIs.
- Each Component’s data structures will offer as much flexibility as makes sense given the goal of keeping each Component really good at one or two tasks. We’ll listen to feedback carefully to get this right.
- Each Component has a clean, simple web front end so you can explore the data held in a store without having to write lots of SQL queries. Often you will be able to edit the data this way, too.
- Get started in seconds – each Component offers at least some functionality which is available inside a minute after getting involved.
- Non coders are welcome – we are building the Components so that non-coders can start gathering, editing and sharing data straight away, possibly long before they are in a position to launch a ‘real site’.
- Data can be added to the Components both through write APIs and through manual editing interfaces, suitable for non-coders.
- Learn from our mistakes – it is really easy to get the wrong data structure for civic, democratic or governmental data. Good practice data structures are baked into the Components, to save you pain later.
- Use our hosted versions, or install open source code locally. It will normally be quicker to get started in using the Components in a hosted environment, but if you want to run them locally, you’re entirely welcome. The code will be open source, and we’ll work hard to make sure it’s attractive and easy to install.
- The Components will talk to each other, and to the rest of the web using simple open schemas which will evolve as they are built. Where possible we’ll pick up popular data standards and re-use those, rather than building anything ourselves.
What the Components Aren’t
Sometimes in life it can be easier to describe things by what they aren’t:
- The Components are definitively not modules in a framework or platform. Each one is totally independent, and they will frequently be written in different languages – partly to force us to ensure that the APIs are truly excellent.
- The Components aren’t either Hosted or Local, they’re both. We’ll always offer a hosted version and a downloadable version, and you’ll always be able to move any data you have stored on the hosted versions down to your local copies.
- The Components aren’t all about mySociety. We’re planning to build the first ones in conjunction with some friends, and we’ll be announcing more about this soon. We want the family of Components to be jointly owned by a group of loving parents.
When can I see some of the Components in Action?
We’ll be blogging more about that tomorrow…
Footnote – To see the provenance of the extremely useful ’small pieces loosely joined’ concept, see this.
FixMyStreet, our site for reporting things like potholes and broken street lights, has had something of a major redesign, kindly supported in part by Kasabi. With the help of Supercool, we have overhauled the look of the site, bringing it up to date and making the most of some lovely maps. And as with any mySociety project, we’d really appreciate your feedback on how we can make it ever more usable.
The biggest change to the new FixMyStreet is the use of responsive design, where the web site adapts to fit within the environment in which it’s being viewed. The main difference on FixMyStreet, besides the obvious navigation changes, is that in a small screen environment, the reporting process changes to have a full screen map and confirmation step, which we thought would be preferable on small touchscreens and other mobiles. There are some technical details at the end of this post.
Along with the design, we’ve made a number of other improvements along the way. For example, something that’s been requested for a long time, we now auto-rotate photos on upload, if we can, and we’re storing whatever is provided rather than only a shrunken version. It’s interesting that most photos include correct orientation information, but some clearly do not (e.g. the Blackberry 9800).
We have many things we’d still like to do, as a couple of items from our github repository show. Firstly, it would be good if the FixMyStreet alert page could have something similar to what we’ve done on http://planningalerts.barnet.gov.uk/, providing a configurable circle for the potential alert area. We also are going to be adding faceted search to the area pages, allowing you to see only reports in a particular category, or within a certain time period.
Regarding native phone apps – whilst the new design does hopefully work well on mobile phones, we understand that native apps are still useful for a number of reasons (not least, the fact photo upload is still not possible from a mobile web app on an iPhone). We have not had the time to update our apps, but will be doing so in the near future to bring them more in line with the redesign and hopefully improve them generally as well.
The redesign is not the only news about FixMyStreet today
As part of our new DIY mySociety project, we are today publishing an easy-to-read guide for people interested in using the FixMyStreet software to run versions of FixMyStreet outside of Britain. We are calling the newly upgraded, more re-usable open source code the FixMyStreet Platform.
This is the first milestone in a major effort to upgrade the FixMyStreet Platform code to make it easier and more flexible to run in other countries. This effort started last year, and today we are formally encouraging people to join our new mailing list at the new FixMyStreet Platform homepage.
Coming soon: a major upgrade to FixMyStreet for Councils
As part of our redesign work, we’ve spoken to a load of different councils about what they might want or need, too. We’re now taking that knowledge, combining it with this redesign, and preparing to relaunch a substantially upgraded FixMyStreet for Councils product. If you’re interested in that, drop us a line.
Kasabi: Our Data is now in the Datastore
Finally, we are also now pushing details of reports entered on FixMyStreet to Kasabi’s data store as open linked data; you can find details of this dataset on their site. Let us know if it’s useful to you, or if we can do anything differently to help you.
On a mobile, you can see that the site navigation is at the end of the document, with a skip to navigation link at the top. On a desktop browser, you’ll note that visually the navigation is now at the top. In both cases, the HTML is the same, with the navigation placed after the main content, so that it hopefully loads and appears first. We are using display: table-caption and caption-side: top in the desktop stylesheet in order to rearrange the content visually (as explained by Jeremy Keith), a simple yet powerful technique.
If you have any technical questions about the design, please do ask in the comments and I’ll do my best to answer.