Here’s everything the SocietyWorks team has been up to this sprint.
—
Image: Gautam Lakum
Here’s everything SocietyWorks is up to this sprint.
We prepared for the soft launch of the Bromley Waste service.
The new FixMyStreet Pro features we’ve been working on have taken a little longer than we anticipated, but we’re confident that they should be completed this sprint. We’ll be letting clients know all about them as soon as they’re live.
We’ve been prepping for our user groups and creating an agenda for the day. The challenge here is to make sure it’s not death by PowerPoint. We’re working with mySociety’s Events Manager Gemma to decide how best to shape it, and to explore the various online tools that make online events that bit more dynamic.
Since April 2020 Highways England have been trialing FixMyStreet in their East Midlands area to evaluate the response by users to a new digital channel for reporting highways issues. As of 9 November this trial has been expanded in size and scope to cover the whole of England, running until March 2021.
—
Image: Leo Sammarco
Here’s everything SocietyWorks is up to this sprint.
As we’ve mentioned previously, we’re working on new functionality around bins and waste as part of the ongoing SocietyWorks brand and product expansion.
This service is coming on apace, and we’re creating a showcase site to demonstrate the new features as they become ready: as yet it’s really just a clickable prototype, but you can have a quick play with it here.
We’re moving forward on a couple of the tickets on our public Roadmap:
We’re a step closer to getting completion photos out of Alloy, and will be adding this to one of our client’s staging sites next week for feedback.
FixMyStreet mobile improvements were demonstrated to everyone at mySociety last Friday — and board members also joined to see what progress has been made. We’re now scheduling in the development work to get these changes live with one of our Developers.
—
Image: Jilbert Ebrahimi
Here’s everything SocietyWorks is up to this sprint.
One big area we’re working on this sprint comes from our development roadmap.
We’re referring to it as a ‘photo first’ workflow, and it’d enable users to take a snap of a street fault and upload it as a way of initiating a report. This all keys into a piece of research we’ve done which found that reports with photos attached have around a 16% higher chance of being fixed than those without.
As part of our exploration, Developer Dave’s been training an AI model to automatically scan each image and guess what category it falls into — very cutting edge!
But at the same time, we’re aware that we must keep every type of user’s best interests at the heart of all our development: we don’t want to sacrifice the simplicity that’s always been the key to FixMyStreet’s success, and the reason it has such vocal advocates amongst its citizen users.
As an example of this: as we assess the available technology to help us work on this functionality, we’re being resolute about basing decisions on what the job needs, not which product has the most bells and whistles.
An avenue we’re also exploring as part of this work is the potential for extracting geolocation metadata from the photograph, which would cut down on the amount of detail the citizen needs to type in. However, here, again there are balances to be struck: we don’t want to increase the potential for errors where a phone’s GPS isn’t accurate enough, or where the data we pass onto councils isn’t as precise as they need it to be.
Meanwhile, Designer Martin has been looking into the user experience on mobile, making improvements for what is increasingly the most popular way to report.
We’ll soon be making the existing app redundant in favour of Progressive Web Apps (PWAs) — Martin’s work will still be relevant there, though.
PWAs are more flexible, allowing each council to incorporate their own branding and templates at no extra cost, and effectively offer residents what looks and feels just like a dedicated app. We’ve written a bit about these previously.
Development continues on our Waste product. We’re integrating with Bromley and Veolia’s Echo system and doing plenty of testing around that — in particular, making sure it picks up on irregular dates such as bank holidays, and that it can handle the 48-hour window for reports of missed bin collections.
And, having completed our user research and consequence scanning exercises on the Noise concept, we’ve come to the conclusion that it should incorporate anti-social behaviour reports: Noise and ASB are so intertwined that it makes the most sense to combine them into a single service, albeit one that will divert each type of report to the relevant council department.
Feedback from our test users was all good, so we’ve now reported our findings back to Hackney and are waiting to hear if they’d like us to progress with integrating with their two back-end systems.
Meanwhile, you can see more about consequence scanning in the well-received session Martin led at LocalGovCamp a couple of weeks ago.
We’ll be conducting one of our regular scheduled pen tests to ensure the security of FixMyStreet Pro.
We’re setting up a new instance of FixMyStreet Pro for our latest client: this one involved Symology, a system we’ve worked with extensively in the past, so it should be reasonably straightforward.
Hackney’s instance, an Alloy integration, should be going live by the end of this month, so we’re making plans for that.
One exciting feature here is that we’re looking into pulling ‘completion’ photos out of Alloy — that is, photos taken by the maintenance crew to show that the problem has been fixed — so we can display them on the relevant FixMyStreet report, and possibly also include them in an email update to the report-maker.
Welcome to the first of our sprint notes.
For anyone who’s interested in our work around Noise, or who would just generally like to understand more about how development is managed at SocietyWorks, these regular catch-ups will allow you to follow along as we progress through the various stages of making a new service.
So: here’s what we did last sprint.
Image: Matt Brown (CC by/2.0)
Schedule your one-to-one demo
Request a demo