Weave Code
Echoo Laravel Package
lara-zeus/echoo
Echoo is a lightweight Laravel package from the Lara Zeus suite that simplifies real-time broadcasting and notifications. Connect Laravel Echo, fire events, and keep users in sync with an expressive, minimal API and almost no boilerplate.
Zeus Echoo is filamentphp form component to record audio from your browser
Frequently asked questions about Echoo
- How do I install lara-zeus/echoo in a Laravel Filament app?
- Install it with composer require lara-zeus/echoo, then register the field or plugin with your Filament panel provider. Publish the package config and any front-end assets so the recorder UI loads correctly, then point the component at a configured storage disk. The setup assumes a standard Filament panel running on Livewire and Alpine, so no custom SPA wiring is required.
- Does Echoo support Filament v3 and Filament v4?
- Echoo is a Filament form-field plugin, so its compatibility tracks the Filament major version declared in the package composer.json. Because the Lara Zeus plugin family moves quickly, check that constraint before upgrading your panel rather than assuming both v3 and v4 are supported. Pin the package version alongside your Filament version and run a single form through a smoke test after any major Filament bump.
- What changed in lara-zeus/echoo 1.0.4?
- Version 1.0.4 is a patch release that fixes pre-save audio preview URL generation, so users can record and listen back before submitting the form. It also includes CI and dependency hygiene, with Dependabot bumps confined to GitHub Actions workflows rather than the shipped runtime code. No new features, deprecations or schema changes are signalled, which makes the upgrade low risk.
- Which storage disks can Echoo save recordings to, and do previews expire?
- Echoo writes through Laravel's filesystem abstraction, so the target disk is configuration-driven and typically includes local storage as well as S3-style drivers. Preview URLs before save sit between the browser blob or temp file and the storage disk, which is exactly the seam the 1.0.4 fix touched. If previews use temporary or signed URLs, confirm the TTL in config and tune it so ops users have enough time to listen back and re-record.
- What audio format does the browser recorder produce, and does it work on Safari and iOS?
- Output depends on the browser's MediaRecorder implementation, so you will see webm/opus on Chromium-based browsers and mp4/aac in some Safari and iOS environments. Echoo captures what the browser provides; playback compatibility, transcoding and transcription downstream remain your responsibility. Test record, preview and playback on your actual target devices before rolling the field out widely.
- Can I limit recording duration, file size, or allowed MIME types in Echoo?
- The recorder is configured through the published package config, where you set the storage disk, directory and related field options. Duration caps, file-size limits and MIME validation should be confirmed in the package config and reinforced with Laravel validation rules on the form. Enforcing limits server-side as well protects you if a client bypasses the browser-side recorder constraints.
- Are there hooks or events in Echoo for post-save processing like transcoding or transcription?
- Echoo is a form field rather than an application API, so there is no broad service layer to wrap. If the package does not expose dedicated events, hook into your model's saved and updated events or a queued job to transcode to mp3, run virus scanning, or send audio to a speech-to-text service. Confirm the available extension points in the package source before designing that pipeline, and add PII redaction where recordings may contain sensitive speech.
- What happens if a user denies microphone permission or their browser doesn't support recording?
- Browser MediaRecorder support and permission state vary, so the recorder UI needs to fail gracefully rather than silently. Test the field under permission denial, an unsupported browser and a network drop mid-recording, and surface a clear message plus a free-text fallback where the audio is optional. Because the component is a Filament field, validation and required rules should not block submission when the browser cannot capture audio.
- Is lara-zeus/echoo a real-time broadcasting package like Laravel Echo?
- No. Despite some descriptions mentioning broadcasting and notifications, Echoo is a Filament form component that records audio from the browser and stores it through a configured disk. It does not replace Laravel Echo, events or websockets for real-time sync. Evaluate it specifically as an audio capture field inside a Filament panel, not as a notification or broadcasting layer.
- Should I use Echoo or keep a custom Vue/Alpine audio recorder?
- If your admin surface is already Filament, Echoo gives you a near-native field with minimal boilerplate and is quick to sponsor for voice notes, debriefs or verbal consent capture. If your primary surface is a custom SPA or Inertia app, the value drops sharply and you are better off reusing the underlying recorder pattern directly. When migrating from a bespoke recorder, run both behind a feature flag on one low-risk form, compare saved format, size and playback on target devices, then retire the custom code. Also weigh the single-maintainer ecosystem risk and pin versions deliberately.
Weaver
How can I help you explore Laravel packages today?