Rethinking the Thread Counter Tool

Android app concept. UX design.

The Problem

First-year textile engineering students rely on a physical thread counter to analyze fabric samples.
However, not all students have access to one. This creates a fragmented workflow between measuring, annotating, and storing information.

Objectives

Replicate core functionality of a thread counter using a smartphone camera.

Allow users to document samples (images + notes).

Keep the experience lightweight and accessible.

Reduce dependency on external tools.

The Product

An Android app: A mobile experience that not only replaces the thread counter, but improves the way students interact with textile samples.

Timeline

October 2024 to December 2024. (2 months)

Constraints

Convenience: Using the app should be easier than just investing in the physical tool.

Device variability: Different devices with different hardware: camera qualities, screen resolution.

No budget: Solution had to rely entirely on built-in capabilities.

Technical uncertainty: Measuring through a camera without calibration.

Early Exploration

The core challenge appeared immediately:

How do you measure a physical sample using a smartphone camera without specialized hardware?

Initial Concept

The first approach focused on a simple, low-tech solution:

  • A fixed square overlay on the camera view

  • Users manually draw a reference square on the textile

  • Align both square to approximate scale

This approach intentionally shifts precision responsibility to the user, avoiding complex calibration.

These are the first wireframes that I made that night in the lab. The setting of this story is Argentina, please excuse the Spanish and my messy handwriting.

Wireframes

I started with paper wireframes, focusing on:

  • Fast access to camera

  • Clear guidance for first-time use

  • A minimal interface to reduce cognitive load

Prototyping

Through multiple iterations in Figma, the design evolved to:

  • Simplify the capture flow

  • Improve onboarding (“how to use”)

  • Strengthen visual hierarchy for notes and sample data

User feedback

It would be great to have a way to keep track of where you’re counting. Like the needle on the physical device.
— N.
It would like to be able to save a diagram of the sample’s weave pattern in addition to taking text-based notes.
— C.

The feedback received revealed something important: Users weren’t just thinking about measurement.

They wanted context and tracking.

The product was no longer just a measuring tool. It was becoming a sample documentation system.

This reframed the project:

  • From tool replacement → to workflow enhancement

  • From single action → to collection and analysis

Outcome

The project evolved into a broader concept. A mobile app for building a personal textile sample library that combines:

  • Image capture

  • Measurement approximation

  • Notes and annotation

  • Potential for pattern visualization

What’s next

This exploration led to a new product direction focused on textile sample documentation. I’m currently developing this idea further as a separate project.

Next
Next

Reactive Task Manager