HiTag

Revolutionizing fish research data collection

The challenge

The Large Pelagics Research Center was losing critical fish migration data. Their manual data entry system relied on fisherpeople's memories, with data entered days or weeks after catch-and-release events. This delay resulted in incomplete and inaccurate records that undermined global fish population research.

The opportunity

New fish tags carry an RFID chip, which can automate the process of tag identification via bluetooth.

The approach

Working with the Olin College of Engineering, I designed an iOS app that works with new RFID-equipped fish tags. Fisherpeople can now scan tags instantly using their phones, capturing accurate data at the moment of catch.

This transformed a weeks-delayed manual process into real-time data collection, improving both fishing experiences and scientific research quality.

The team

Team: 3 researchers, 1 iOS engineer, 1 product designer

My role: Lead Product Designer

Part 1: Understanding our users

Due to tight timeline constraints, I worked directly with the 3 marine researchers to understand three distinct user groups and their unique needs.

Commercial fishers

  • Monetarily incentivized to record data

  • They work in professional operations with structured workflows, so there is time pressure during commercial operations

  • They need fast, efficient data entry that doesn't disrupt fishing activities

Recreational fishers

  • “Citizen scientists” personally invested in conservation

  • They have privacy concerns about sharing their exact fishing locations

  • They need optional data inputs and an interface that requires minimal training for occasional, casual use

Marine researchers

  • Care about scientific accuracy and comprehensive data collection

  • Often aboard commercial and recreational vessels for data collection support

  • They need the ability to collect complete, accurate records with scientific precision

These insights shaped early product requirements

  • 45-second rule: Commercial fishers revealed the entire process needed to complete in under 45 seconds to fit their operational pace.

  • Privacy controls: Recreational fishers' location concerns led to flexible sharing options (general region vs. precise coordinates).

  • Offline-first design: All user groups highlighted poor connectivity while fishing, driving our offline-capable architecture.

  • Progressive complexity: Mixed user technical comfort levels led to our hybrid approach—simple inputs for basic users, detailed options for researchers.

Part 2: Workflows & information architecture

I mapped the complete catch-and-release workflow and proposed two interaction approaches

Workflow 1: Step-by-step screens

  • Each data point on separate screens

  • Better for complex data entry

  • Supports detailed validation

Workflow 2: Single form

  • All inputs on one screen

  • Faster completion (critical for 45-second requirement)

  • Easier engineering implementation

The team agreed to move forward with workflow 2. It would be easier to implement and maintain, and it was faster and more flexible than ordered screens.

Part 3: Interaction design & patterns

I designed interaction patterns for challenging field requirements.

Species selection

  • Feedback: Researchers noted recreational users often couldn't identify species precisely -> how might we handle "unknown" species or scientific name variations?

    • Fuzzy search for ease-of-use for non-experts

    • Included "I don't know the species" option for recreational users

    • Implemented both common and scientific name search

  • Feedback: Fisherpeople are often working with the same types of species, so searching every time could be cumbersome -> how might we improve efficiency?

    • Added "recently used" shortcuts for efficiency

Location data

  • Feedback: Recreational fishers expressed strong privacy concerns about exact locations -> how might we balance research needs with user comfort?

    • Created flexible privacy options (general region vs. precise coordinates)

    • Added map interaction for area selection when users want less precision

Data entry for non-experts

  • Feedback: Non-researchers are sometimes unfamiliar with RFID chips and measurements like fork length -> how might we make technical details easy to understand?

    • Created a pattern of progressive information via sheets

Part 4: Visual design system

Accessibility for extreme conditions

The UI needed to be visible in high-glare situations. It also needed large touch targets to support usability on the rocky ocean, and have clear visual hierarchy to support speed under stress.

Design Goals: Maritime, utilitarian, and efficient.

Final design

1. Homepage -> New entry
2. Detect RFID tag
3. Add details
4. Add species
5. Add location
6. Confirm details
7. Data submitted confirmation

Results & Impact

Delivered:

  • Complete iOS app design ready for development

  • Design system and component library

  • Prototype for stakeholder validation and investor presentations

Current Status:

  • App in active development with continued design consultation

  • Preparing for field testing with real users

  • Planning user feedback integration for future iterations

Business Impact:

  • Enabled funding approval from research stakeholders

  • Created foundation for long-term scientific data improvement

  • Demonstrated feasibility of real-time marine research data collection