DEV Community

Tech Nexa
Tech Nexa

Posted on

I Got Tired of Losing Context Behind My Work Photos, So I Built FieldStamp

FieldStamp Link

Android: FieldStamp GPS Camera on Google Play

iPhone: FieldStamp GPS Camera on the App Store

A few months ago, I noticed something annoying about the photos on my phone.

I had a lot of them.

Photos from different places. Different days. Different projects. Some were taken just a few hours apart, so they looked almost the same.

At the time I took them, I knew exactly what each photo was for.

A few days later, I did not.

I would open my gallery and ask myself:

  • Was this taken at the first location or the second one?
  • What time did I take this?
  • Which project did this belong to?
  • Why did I take this photo again?

The photo was still there, but most of the useful context was gone.

That problem became the starting point for FieldStamp GPS Camera.

A Photo Is Not Always Enough

For personal photos, this is usually not a big issue.

You take a photo, keep it in your gallery, and maybe look at it again later.

But work photos are different.

People working in construction, maintenance, property inspections, agriculture, utilities, or field services often take photos as evidence.

The photo needs to show more than what the camera can see.

It may also need to answer:

  • Where was this taken?
  • When was it taken?
  • Which job or project was it related to?
  • What issue was being documented?
  • Can this photo be included in a report?

Without that information, someone usually has to remember it, write it down, rename the file, or organize everything manually later.

That sounds manageable when there are five photos.

It becomes painful when there are fifty.

My First Idea Was Very Simple

At first, I only wanted to add location and time directly to a photo.

Take a photo, display the GPS coordinates, address, date, and time on it, then save it.

Simple.

But while building the app, I realized that the watermark itself did not solve the full problem.

The next problem was organization.

Even if every photo had GPS information, users could still end up with hundreds of images mixed together.

So I added projects.

A user could create a project, select it before taking photos, and keep related photos in one place.

For example:

  • Apartment inspection
  • Construction Site A
  • Roof repair
  • Farm Area 2
  • Monthly equipment check

This made the app feel less like a normal camera and more like a small field documentation tool.

The Details That Became Important Later

While testing the app, I started noticing small things that I had not considered in the beginning.

GPS accuracy was one of them.

A phone may detect a location, but that does not always mean the location is accurate.

Sometimes the signal is good. Sometimes it is not.

So the app shows GPS accuracy before the photo is taken. The user can wait a little longer when an accurate location is important.

I also added information such as:

  • Coordinates
  • Address
  • Date and time
  • GPS accuracy
  • Altitude
  • Compass direction
  • Project name
  • Custom notes

Users do not need to display everything. They can choose a layout depending on what matters for their work.

Some people may only need the date and address.

Others may need coordinates, project information, and a note describing the issue.

The Photo Was Only Half of the Workflow

Another thing I learned was that taking the photo is often not the final step.

After a site visit or inspection, the photos may need to be sent to:

  • A manager
  • A client
  • A property owner
  • A contractor
  • A project team

Copying photos one by one into a document takes time, especially when each image also needs a description.

That is why I added PDF reports.

Users can select their field photos and create a report containing the images, project information, location details, and notes.

It is still a simple feature, but it removes a repetitive step from the workflow.

Instead of taking photos first and building the report somewhere else, both actions can happen in the same app.

What I Learned While Building It

The biggest lesson was that a feature is not the same as a complete workflow.

“Add GPS to a photo” is a feature.

But the real workflow is closer to this:

  1. Arrive at a location.
  2. Select the correct project.
  3. Check the GPS signal.
  4. Take several photos.
  5. Add notes when needed.
  6. Keep the photos organized.
  7. Create a report.
  8. Send it to someone else.

Thinking about the full workflow changed many of my product decisions.

I also learned that small utility apps need to be fast.

Someone standing outside at a job site does not want to go through six setup screens before taking a photo.

The app should open quickly, show the important information, and let the user continue working.

That sounds obvious, but it is easy to forget when you are building features from a desk.

FieldStamp Is Still a Work in Progress

FieldStamp is currently available on Android and iPhone.

Android:

FieldStamp GPS Camera on Google Play

iPhone:

FieldStamp GPS Camera on the App Store

I am still improving the camera experience, project organization, watermark layouts, and PDF reports.

I am also trying to understand how different people document their field work.

Some users care most about location accuracy.

Some care about report creation.

Others just want a quick way to prove when and where a photo was taken.

Building this app reminded me that many useful products start from a small, repetitive frustration.

For me, it was opening my photo gallery and realizing that I could no longer remember the story behind the photos.

That was the problem I wanted to fix.

Top comments (0)