Canvas Pointer Laravel Package

Product Decisions This Supports

• Build vs. buy for image-annotation UI: The core capability—rendering an image in an admin form and capturing click coordinates as structured data—is a deceptively fiddly front-end problem (responsive image scaling, coordinate normalization, marker persistence, edit/delete). This package lets you buy that primitive for the cost of a Composer dependency instead of a 1–2 sprint build, freeing roadmap capacity for the workflow around it.
• Feature scoping for admin/back-office tooling: Because it is a single Filament form field, it answers the scoping question "how much annotation do we actually need?" If your requirement is points of interest on one image, this closes it. If requirements drift toward polygons, bounding boxes, freehand, or multi-image galleries, this package sets a clear boundary that forces an explicit scope decision rather than silent scope creep.
• Roadmap sequencing for inspection/annotation workflows: Common fits include marking defects on product photos, tagging locations on floor plans or site maps, flagging regions in documents/scans, and pinning interest points on diagrams. This supports shipping a v1 "mark it on the image" workflow now—storing coordinates you can later render on a customer-facing map—without committing to a full annotation platform.
• Use-case validation before investment: At 23 stars, this is a lean, single-purpose package. It is best treated as a proof-of-concept accelerator: use it to put a clickable-image field in front of users in days, validate that operators actually annotate images the way you expect, then decide whether to invest in a bespoke or heavier library.
• Dependency/architecture decisions: Adopting it implicitly commits the feature to Filament and to the package's storage shape (coordinates on the model). That is a useful forcing function to confirm your admin stack and data model before building downstream consumers (APIs, mobile views, reporting) on top of the coordinate format.

When to Consider This Package

Consider adoption when:

• You are already running Filament (v3-era) and the feature lives in an admin/resource form—not a public-facing or customer app.
• The requirement is point markers only, on a single image per record, with coordinates persisted to your own model.
• You want a fast, low-cost v1 and are comfortable treating the package as a dependency you may fork or replace later.
• MIT licensing matters (permissive, commercial-safe, no procurement friction) and the recent release cadence (Aug 2025) suggests active maintenance.
• Your team can absorb the vendor risk of a small, low-star package—i.e., you have PHP/Laravel capacity to read, patch, or vendor the source if upstream stalls.

Look elsewhere when:

• You need shapes beyond points—polygons, rectangles, freehand, or multi-region annotation. This is a pointer field, not an annotation suite.
• You need multi-image, image versioning, or collaborative/multi-user annotation with audit trails.
• Your front end is not Filament (Inertia/Vue/React SPA, Livewire-only, public site). Integration cost will exceed the value.
• Filament major-version compatibility is unproven for your version—validate against your exact Filament release before committing.
• You need SLAs, security review, or vendor support. A 23-star, single-maintainer package does not carry those guarantees; if the annotation feature is business-critical or regulated, budget for in-house ownership.

How to Pitch It (Stakeholders)

To executives: This is a small, MIT-licensed Laravel/Filament component that lets operators click and place markers on an image inside our admin panel—covering a class of "mark it on the picture" workflows (defect flagging, location tagging, diagram annotation) that would otherwise cost us a sprint or more of custom front-end work. It is free, commercially safe, and low-commitment: we can pilot it in one admin screen, measure whether users adopt it, and walk away with minimal sunk cost if it does not fit.

To engineering: It is a Filament form field that captures click coordinates against a rendered image and persists them—no new front-end stack, no bespoke canvas code to maintain. Adopt it as a time-boxed pilot on one resource: verify Filament version compatibility, confirm the coordinate storage shape fits our model and any downstream consumers, and assess maintainer responsiveness. Treat it as a thin dependency we are prepared to fork or vendor if upstream goes quiet; the surface area is small enough that ownership cost is low. Recommendation: pilot, not platform bet—ship the workflow, keep the annotation UI replaceable behind our own form-field abstraction.