Author name: Jeremy Kratz

Going native with system fonts and form fields

Designing an application interface in today’s world is difficult. Many products offer native implementations for iOS and Android, as well as cross-browser HTML versions. Native platforms each offer their own user interface guidelines, which outline some best-practice approaches to navigation, controls, animations, and more. Apps that follow these guidelines are instantly understandable and usable by

Going native with system fonts and form fields Read More »

Debugging like a Detective

Last week we received an email from a DoneDone customer who was experiencing a strange file upload error. We attempted to reproduce the error with no luck, so we asked the user to notify us if it happened again. They replied that the error had disappeared. Case closed. A few days later, a second customer

Debugging like a Detective Read More »

DoneDone Quick-Start

We’ve done quite a bit of writing over the past few years (and we’ve made quite a few improvements to DoneDone too!), so it seemed like a good idea to collect a few popular posts into a short quick-start guide. Here are a few quick reads to help you squeeze everything you can out of

DoneDone Quick-Start Read More »

Clarifying DoneDone's Issue Workflow

DoneDone features a simple workflow designed to move issues from Open to Fixed. Our workflow manages which new statuses are available based on the issue’s current state and the user’s role. For example, if the Fixer has flagged an issue as Not Reproducible, the Tester will only be able to select Pushed Back (providing steps

Clarifying DoneDone's Issue Workflow Read More »

Issue Tracking for your Home

A few months ago, my wife and I decided it was time to move out of the suburbs and back closer to the city. Granted, Little Rock isn’t a huge metro area, but it regularly takes us 45 minutes or more to run “quick” errands from our current home. So, after searching for a few

Issue Tracking for your Home Read More »

Scroll to Top