React Native or .NET MAUI: we ship both, here is how we choose
An honest comparison of React Native and .NET MAUI for cross-platform mobile, based on FurnitureAxis's Expo companion app and what each framework's docs say.
Blog, page 10
Writing based on projects we built, without listicles or filler.
What a real estate portal needs that a WordPress theme can't do
Listings ingestion, real filters, map performance, and lead routing all break a theme's assumptions in time. Where that line sits, and when a theme still works.
Why we show linked reviews instead of testimonials
Our reviews page links straight to Fiverr and Freelancer profiles instead of curated quotes, and adds no review schema. Here is why both choices are deliberate.
What a realtime voice agent actually consists of
A booking or intake line is five separate pieces, transport, model, tool calls, guardrails, and a handoff path, and each one is a real decision.
Replatforming an online store without losing your rankings
A migration checklist for ecommerce replatforms: URL mapping, 301s, canonical tags, sitemap cutover, structured data parity, and Search Console after launch.
Search: Postgres full-text, Algolia, or Meilisearch
Database-native search covers more than people assume, until typo tolerance and faceting become the job. Where that line sits, and what an index in sync costs.
Serialized inventory: why furniture retail can't run on stock counts
Quantity fields work for interchangeable stock. Big-ticket furniture retail needs a record per physical unit, which matters once returns and repairs enter.
Server Actions or API routes in Next.js
Server Actions cover most mutations in a Next.js app, but webhooks, third-party callers, and non-React clients still need a real route. Here's how we decide.
Should this feature be AI? The checklist we run
A five-question checklist for deciding whether a feature actually needs a model, or whether plain code and a database query would serve the client better.
Static, server-rendered, or islands: a guide for people who buy software
A plain-language explainer of the three rendering models, grounded in two live Dawloom builds, so you know what a proposal is asking you to pay for.
Stripe subscriptions: the patterns we reuse
How we structure Stripe billing: webhooks as the source of truth, idempotent handlers, the customer portal over a custom screen, and test clocks for renewals.
Svelte 5 runes vs React hooks: we write both every week
A mental-model comparison of Svelte 5 runes and React hooks, based on two things we maintain: this site's Svelte island and FurnitureAxis's React 19 frontend.
Posts also ship as an RSS feed.
Got something to build?
Tell us what you need. An engineer replies, not a sales team.