DEV3 Technologies home

DEV3 Pingwillow – Messenger Laravel Script: Groups, Channels, Voice Notes, Calls, Flutter App & Gemini AI admin tools

Messenger on Laravel 12 and Filament 4 with Gemini AI admin tools (bring your own key) and a language switcher: phone sign-up, groups, broadcast channels, voice notes, 1:1 calls, web app and safety console. Web installer and demo data included. Flutter app source included.
by DEV3 TechnologiesVerified Author(0) 0 sales 1 viewsUpdated 15 Nov 2026

Video tour. Pick a section below to browse 54 screenshots in 6 sections.

App & phone tours

Tap play to watch each app. Nothing downloads until you do.

  • Mobile web0:11
  • Chat app app1:45

Pingwillow is the software for running your own messenger service: a community, a company or a regional chat brand. People sign up with a phone number or email and a one-time code, chat one to one or in groups of up to 256, follow broadcast channels, send photos, files, voice notes and locations, and call each other. A web app, a Flutter chat app and a safety console for your team come with it. It is built by DEV3 Technologies on Laravel 12 and Filament 4, and the Flutter app source is included.

What it does

  • Chats, groups and channels. One-to-one chats, groups up to 256 members with roles, invite links and join approval, and broadcast channels where only admins post and followers see view counts.
  • Rich messages. Text, photos, video, files, voice notes with a waveform, locations and contact cards, with replies, reactions, forwarding, edit and delete for everyone, pinned chats, archive and search.
  • Receipts, typing and presence. Delivered and read receipts, typing indicators and last seen, each controlled by the user's own privacy settings.
  • Disappearing messages. A timer of 24 hours, 7 days or 90 days per chat; a scheduled job purges expired messages.
  • Contact discovery. Contacts are matched on peppered hashes, so raw phone numbers are never stored for matching.
  • Calls. One-to-one voice and video over WebRTC with signed call tokens. You bring your own STUN/TURN server for real media; the demo uses a simulated driver.
  • Several devices. Sign in on the app and in a browser, link a browser with a QR code and revoke any device.
  • Web app. A full browser messenger at /web, with Laravel Reverb realtime and an automatic polling fallback.
  • Safety console. Reports with a response-time countdown, strikes, bans and appeals, blocklists, rate-limit overrides, messaging health, call statistics, analytics, announcements, API keys and webhooks. Operators cannot browse private chats: the only message text they see is what a reporter attached, and each view is audited.
  • Public pages. A marketing site, public channel previews, group invite landing pages and template privacy and terms pages.
  • Language switcher. A Google Translate language switcher in the public header and the admin bar, plus an in-app language picker in the Flutter app. Private chat text is excluded from translation.

The Flutter app

The chat app (apps/chat) has phone sign-up with a code, the chat list, threads with media, voice notes, reactions and replies, group and channel info, calls, devices and settings. It starts in demo mode with a built-in mock of the API, so it runs without a server; point it at your site with the dart-defines described in apps/chat/docs/STORE-PUBLISHING.md, which also covers store privacy and user-generated-content requirements.

Gemini AI admin tools

Optional, bring your own key: add your own Gemini key after purchase (Google bills your account); with no key the AI buttons say "Add your Gemini key in Settings". Every result is a draft you preview and edit; nothing is applied automatically.

  • Reports and appeals: summarise a report from the context the reporter attached, suggest an outcome for a human to decide, draft a reply, and summarise an appeal. AI triage of reported messages is off by default.
  • Blocklists: suggest terms from confirmed spam patterns, saved inactive for your review.
  • Health and analytics: explain a latency spike or a cluster of call failures, and explain the dashboard and reports.
  • Announcements and users: draft a service notice, summarise an account's metadata and flag risks.
  • A Google Translate language switcher in the public header and the admin bar.

Private message bodies are never sent to Gemini, names, emails and phone numbers are replaced before any call, and no key ships in the code.

Quality checks

The release passed seven gates on the final code: Larastan level 6 with 0 errors, a Pest suite of 287 tests, a build with a 20 KB gzip page budget and no 3D, migrations and the full demo seed on MySQL 8 and SQLite, a headless smoke test over 49 pages and flows, the web installer driven from the zip, and a secret scan. 43 MySQL race checks cover parallel sends, repeated client ids, group caps, edits against deletes, read receipts, simultaneous calls and one-time link tokens. The Flutter app passed analysis, 46 tests and simulator builds, and ran once against the live API.

What you should know before buying

  • Not end-to-end encrypted in v1. Messages are encrypted in transit (TLS) and at rest with your application key. Operators with database and APP_KEY access can decrypt them.
  • Calls are simulated in the demo. Real 1:1 calls need your own STUN/TURN server (coturn). No group calls in v1.
  • Push notifications are simulated until you add Firebase or APNs credentials.
  • Search decrypts and scans a user's newest 5,000 messages; there is no full-text index on encrypted data.
  • Contact discovery uses peppered hashes, which are rotatable but not unbreakable; it is rate limited.
  • Moderation is manual. There is no automatic detection of abuse; keyword blocklists can raise auto-reports.
  • One Flutter app with source and a store-publishing guide. Building, publishing and store approval are your step; the app was verified in simulator builds, automated tests and against the live API, not on a physical device. The device address book is not read in v1.
  • Use MySQL or MariaDB for a live site. One cron entry every minute is required, and Reverb needs a long-running process (polling works without it).
  • Gemini AI admin tools need your own Google Gemini API key (Settings → AI); no key or AI usage is included. Without a key the AI buttons stay disabled.
  • A Google Translate language switcher is on the public site and admin; it needs Google's widget to load in the visitor's browser.

Included

Source code, the web installer, the Flutter app source with a store-publishing guide, a buyer guide, demo data for a fictional service (1,804 users, 420 groups, 36 broadcast channels, 2,853 conversations, about 617,000 messages, 18,000 calls and 76 reports) and six months of support.

How it's built

Architecture, stack, key decisions and the quality gates DEV3 Pingwillow passed before release.

The engineering behind Pingwillow: per-chat message ordering under a row lock, client-id de-duplication, device fan-out with a polling fallback, group receipts, disappearing-message purging and a console that never browses private chats.

The problem it solves

A messenger fails in small ways that cost trust: messages arriving out of order, a retry that sends twice, a removed member still receiving a group, a read receipt that is wrong in a big group, a joiner past the group cap, or an operator who can read everything. Each case must end with one winner and a record of who did what.

Architecture and approach

Pingwillow is a Laravel 12 application with a Filament 4 safety console, a web messenger, a public site and an app API used by one Flutter app. Every message takes the next number in its conversation under a row lock, clients render by that number and fetch gaps through a sync call. A client-generated id makes a retried send return the same message. Delivery goes to each device with its own cursor, and realtime events carry metadata only: bodies always come from sync, so a Reverb outage falls back to cursor-aware polling. Message bodies and files are encrypted at rest with the application key. Group membership, roles, caps and invite links are checked in one visibility rule used by every route, so an outsider gets a 404 rather than a 403. Contact discovery matches peppered hashes, and the console shows no message text apart from the copy a reporter attached, with each view audited.

Quality gates and results

The release passed seven gates, including a headless smoke test over 49 pages and flows and 43 MySQL race checks: fifty parallel sends giving contiguous numbers, the same client id twice, two joins at the group cap, an edit against a delete, parallel read receipts, simultaneous calls and a one-time link token. The consistency command passes on the demo data: 1,804 users, 2,853 conversations and about 617,000 messages.

Tech stack

Area Technologies
Application Laravel 12, Filament 4, Blade, REST API
Data MySQL 8, SQLite
Frontend Tailwind CSS 4, Vite
Mobile Flutter
Quality Pest, Larastan level 6, Playwright

Inside the build

Your own messenger: the marketing site with the willow-and-water hero and the Gemini AI admin tools. Your own messenger — the marketing site with the willow-and-water hero and the Gemini AI admin tools.

Groups and channels: one-to-one chats, groups up to 256 and broadcast channels with view counts. Groups and channels — one-to-one chats, groups up to 256 and broadcast channels with view counts.

Guides & articles

Practical guides and engineering write-ups for DEV3 Pingwillow.

Messenger app software: 7 things to check before you pick one

Last updated
Messenger app software: 7 things to check before you pick one: DEV3 Pingwillow

People want a messenger that is fast and private. Operators want groups that behave, channels that reach everyone and a safety desk that does not read private chats. Here are seven things to check before you pick messenger app software, with DEV3 Pingwillow as the worked example.

The Pingwillow home page

1. Do groups and channels cover your community?

Look for groups with roles and caps, invite links with approval, and broadcast channels where only admins post.

Group info with members and an invite link

2. Do messages arrive in order, once?

Each message should take a number in its chat and a retry should never send twice. Pingwillow numbers messages under a row lock and de-duplicates by a client id.

A thread with photos, replies and receipts

3. What can users control?

Read receipts, last seen, who can add them and disappearing messages should be the user's choice.

Privacy settings

4. How do calls work?

One-to-one calls over WebRTC need your own STUN/TURN server for reliable media. Pingwillow signals calls with signed tokens and simulates them in the demo.

A call in the web app

5. Can the operator read private chats?

In Pingwillow the console shows no message text except the copy a reporter attached, and every view is audited.

Reported context in the console

6. Is there a safety desk?

Reports with a countdown, strikes, bans, appeals and blocklists, with optional Gemini AI admin tools that only produce drafts.

A report triage draft

The chat app on a phone

7. Are the limits honest?

Pingwillow is not end-to-end encrypted in v1: messages are protected in transit and encrypted at rest with your application key. Calls are simulated in the demo, push needs your credentials, and the Flutter app was verified in simulator builds and tests, not on a physical device. Say all of that plainly to your users.

Video: The Pingwillow tour

Frequently asked questions

The complete source code (version 1.0.0) as a download from your account, with the setup and usage guides shown on this page. You can modify the code to suit your product.

Buying guides: Laravel scripts with Filament panels and a web installer · Next.js or Laravel for a SaaS script?

Questions about this product (0)

Answers from the DEV3 team and the community.

Ask a question

No questions yet.

Wondering about setup, licensing or customisation? Ask, and the DEV3 team will help.

More from this author

View all

Related in Web Scripts & Software

View all