I just wanted to make a special announcement that in the next Monthly Community Call (Wed, Jan 8, 2PM EST) we’re planning to discuss the future of the Field Kit UI/UX, specifically the “Edit Log” screen.
This screen in particular has irked me for a while, as it’s got so much going on visually, but with very little overarching structure to organize it. I’ve spoken with some users who have made excellent suggestions on how to streamline the interface and experience. Some of them will be joining the call and I’d like to invite the whole community to take part and provide their feedback.
I see two primary avenues for improvement:
- Overhaul the existing “Edit Log” Screen so that it can be read and edited more easily and concisely. The current screen has evolved many times over, and often design best practices have taken a backseat to expediency. I’m in the middle of prototyping a new layout which puts an emphasis on readability, and moves away from the traditional form-like layout. You’re welcome to view the prototype here, which we’ll look at in more detail on the 8th, but of course bear in mind it is still a work in progress.
- Create new Field Modules, which will provide an alternative to treating all logs all at once. Instead, each Field Module will allow us to design for a specific user scenario, like taking a scouting observation, or assigning a worker with the task of applying an input to a field on a future date. This will be the direction forward for Field Kit in the future, and I expect the “My Logs/Edit Log” module will become less pivotal to day-to-day use of the app, as more specialized Field Modules take it’s place (though we’ve also discussed the idea of transforming it into a general “Log Manager” module for power users and to help with maintenance and debugging).
I hope folks are able to join; the more the merrier! In the meantime, feel free to provide your impressions/suggestions in this thread and we’ll try address them in the call.