OneSignal

AI Models Still Recommend Twilio for Notifications

Bersyn tested four AI models (ChatGPT, Claude, Gemini, Perplexity) with developer-style prompts asking for the best multi-channel notification API for a B2B SaaS platform. In the experiment (published June 26, 2026), three models mainly recommended incumbents such as Twilio and OneSignal, while Anthropic’s Claude was the outlier and named modern notification providers (Knock, Novu, Courier) far more often. Bersyn highlights a table of model responses showing Claude frequently naming Knock (80%), Novu (80%) and Courier (60%), whereas ChatGPT omitted Knock and Courier entirely and barely mentioned Novu. The author argues this discrepancy matters because buyers who ask LLMs may never learn about newer category-specific tools, so companies must create verifiable, third-party content that ties them to the category to appear in model recommendations.

Cord Cutters News Spring 2026 Reader Survey

Cord Cutters News published a Spring 2026 reader survey asking visitors to spend about five minutes answering questions about the current state of cord cutting. The post, authored by Luke Bouma, notes all responses are anonymous and provides an alternate Google Forms link for iPhone and iPad users due to embedding issues. The article also discloses the site uses affiliate links (for example to Amazon) to help monetize the publisher and mentions third-party ad/notification tooling and partners on the page. The notice appears on the publisher’s site and is intended to collect reader feedback.

Developers Switch from Firebase to Supabase

A developer-published guide (originally on iloveblogs.blog, republished on dev.to) argues that many developers are migrating from Google’s Firebase to Supabase in 2026. The article lists four main drivers: unpredictable per-read Firestore pricing, NoSQL query limitations, vendor lock-in with Firebase, and better server-side/Next.js support from Supabase. It provides concrete migration steps including mapping Firestore collections to PostgreSQL tables, migrating Firebase Auth users to Supabase Auth, exporting data with scripts and pg_dump, updating application code to Supabase SDK calls, and replacing Firebase services with Supabase equivalents. The post includes SQL and TypeScript examples, a suggested two-week migration timeline for mid-sized apps, and claimed outcomes such as lower monthly costs (60–80% savings), improved developer velocity, and data portability because Supabase is open-source and self-hostable.