LeeMate Practical Guide: Annotation, Price Estimation, and Sensor Tools in One App

LeeMate is currently best understood as a compact field tool app rather than a single-purpose utility. In the current project structure, the main navigation is split into four tabs: image annotation, price calculation, sensor tools, and about/support. That layout already tells you what the app is trying to be: a pocket workflow for people who need to mark up photos, make quick material estimates, and check live device-side readings without jumping between multiple apps.

The short version is simple. LeeMate is well suited for annotated photo feedback, lightweight glass or window-related estimates, and quick environmental reference checks. It is not meant to replace professional design software, a full quotation system, or calibrated measurement hardware.

1. What is already released in the current build

Based on the current codebase, three functional areas are clearly present.

Image annotation

This is the most complete part of the product today. The module already supports:

• importing images from the photo library
• freehand brush drawing
• arrows, rectangles, ellipses, numbered steps, and text
• sticker-style image insertion
• undo and redo
• cropping
• zoom and two-finger panning
• saving output back to the photo library

This is important because it shows the module is designed for explanation graphics rather than artistic editing. The practical use case is fast communication: mark a defect, highlight a position, add a sequence, save the result, and send it out.

Price calculation

The calculation tab currently exposes two entries:

• glass weight calculation
• order sheet generation

At the data-model level, the project already defines width, height, glass type, unit price, area, and weight-related logic. It also includes base estimation rules for tempered, laminated, and insulated glass. That means the direction is already specific: this is not a generic consumer calculator, but a lightweight helper aimed at glass, window, or material-related estimation workflows.

That said, the current state still looks more like a structured foundation than a fully developed quoting system. The navigation entry is in place and the model is real, but the interaction depth is not yet as mature as the annotation module.

Sensor tools

The sensor dashboard currently covers seven live metrics:

• decibel
• brightness
• altitude
• heading
• pressure
• coordinates
• speed

The page also supports:

• separate permission handling for microphone, camera, location, and motion
• layout switching between wide cards and two-column cards
• long-press card reordering
• front and rear camera selection for brightness estimation
• place-name resolution for location details

So this is not just a playful sensor demo. It is a practical reference dashboard designed for quick real-world checks.

2. Who LeeMate is best for

Given the current feature boundaries, LeeMate is a better fit for a few specific groups.

People who need to communicate with marked-up photos

If your work involves installation, after-sales support, field inspection, logistics checks, remote troubleshooting, or on-site coordination, you often need to point at an image and explain exactly what changed or what is wrong. The annotation flow is clearly built for that kind of work.

People who need quick material-side estimates

If you repeatedly deal with dimensions, area, or glass weight as part of a first-pass estimate, the price calculation direction makes sense. It is a helper for fast judgment and preparation, not a full office-side quoting platform.

People who need temporary environmental or location references

For fieldwork, testing, route checks, or basic site recording, there are many situations where “a quick reference value” is enough. LeeMate fits that use case better than a dedicated professional meter if the goal is convenience rather than formal measurement.

3. Practical usage tips

Tip 1: treat permissions as module-specific, not all-or-nothing

LeeMate currently touches these permissions:

• photo library add access for saving results
• microphone for decibel estimation
• camera for brightness estimation
• location for coordinates, heading, speed, and altitude
• motion access for pressure and relative altitude

The sensible setup path is to enable them as needed. If you only want annotation, there is no reason to think about the full sensor stack first.

Tip 2: use annotation as an explanation workflow

The annotation module is strongest when used for:

• marking defects
• pointing out installation positions
• adding numbered steps
• attaching short clarifying text

The most useful combinations are usually:

• arrow plus text
• numbered steps plus text
• crop plus annotation
• sticker image plus annotation

In practice, cropping before exporting often produces a much cleaner result than annotating a busy full-frame image.

Tip 3: zoom first, annotate second

The current implementation already includes zooming, two-finger panning, undo, and redo. A stable working pattern is:

1. zoom into the region you actually need
2. place arrows, numbers, or text
3. adjust the selected object instead of redrawing immediately
4. do one export check before saving

That sequence usually reduces rework on dense images or tall screenshots.

Tip 4: use the sensor dashboard selectively

The permission badges in the current dashboard are there for a reason. The intended workflow is not to authorize everything at once, but to unlock only the metrics you need:

• camera for brightness
• microphone for decibel
• location for coordinates, speed, heading, and altitude
• motion for pressure and relative altitude

If you rely on only a few values, reorder the cards and keep your most-used metrics at the front.

Tip 5: treat sensor readings as field references, not formal measurements

The current UI already states the limits clearly:

• decibel is an estimated microphone-based reading
• brightness is inferred from camera exposure data
• device support differs across hardware
• the readings are not intended for medical, safety-alert, or enforcement scenarios

That is the correct mindset. LeeMate is useful for on-site reference and quick context, but not for professional certification-level measurement.

4. Why the app is interesting

LeeMate is interesting less because of feature count and more because of workflow continuity.

In real work, these actions often happen together:

1. import or capture an image
2. annotate it
3. make a first-pass estimate
4. check environment or location context

The app’s real value is that these steps live inside one mobile tool instead of being split across several unrelated utilities.

It also keeps the product scope practical. Annotation saves directly to the photo library. Sensor readings are presented in live cards. The calculation area is clearly structured toward lightweight estimation. The product is trying to help users finish small but high-frequency tasks quickly.

5. What LeeMate should not be mistaken for

At its current stage, LeeMate should not be treated as:

• a professional CAD or advanced design tool
• a full quotation or ERP platform
• a calibrated professional measurement instrument
• a large collaboration platform with cloud-heavy workflows

It is better understood as a fast field companion for recording, explaining, estimating, and checking.

6. Final take

If your day includes marked-up photo communication, first-pass glass or material estimation, and occasional checks of brightness, noise, coordinates, altitude, speed, or direction, LeeMate already has a clear place.

In the current build, image annotation is the most immediately usable module, the sensor dashboard already has practical structure and sensible boundaries, and the calculation module points toward a focused industry workflow. For users who need “record, explain, estimate, and check” in one place, LeeMate is a practical app with a clear direction.