Speechius VS ViewForge

Speechius's answer

It recognises the words you actually say and finds them in your script, rather than scrolling on a timer or reacting to how loudly and quickly you speak. That means it still follows you when you rephrase a sentence, skip a line or jump back.

Recognition runs entirely on your own device, and the window can be excluded from screen sharing and screen recording.

ViewForge's answer:

Three things. (1) Data ownership: ViewForge writes fitment as Shopify metaobjects native to your store — most competitors store fitment in their own database. (2) 8 verticals out of the box: auto, motorcycle, tractor, marine, power equipment, bicycle, printer, electronics — most competitors are automotive-only. (3) Smart Parse: extract fitment automatically from your existing product titles and descriptions instead of re-typing everything.

Speechius's answer

Several teleprompters advertise voice-controlled scrolling, but most of them track your speaking pace and volume: they speed up when you speak faster and stop when you go quiet. They do not know which words you said, so going off-script or jumping back confuses them.

Speechius matches the recognised words against your script, which is the part that keeps working when you stop reading and start talking. It is also a one-time purchase rather than a subscription, and nothing is sent to a server.

ViewForge's answer:

Data ownership. Fitment lives in your Shopify metaobjects, so uninstalling does not take your compatibility data with it. Convermax, EasySearch and PartFinder all keep it in their own databases, and getting it back depends on their export tooling on the day you cancel.

Cost at the low end. The search widget, the compatibility table on the product page and the saved-vehicle garage are all on the free tier, up to 50 products, with no expiry. EasySearch puts the table and the garage behind its $75/month Premium plan. Convermax starts at $250/month.

Automotive and non-automotive coverage. Eight built-in templates, and fully custom templates from $19/month, for catalogs that do not decompose into Year/Make/Model at all.

Speechius's answer

People who speak to a camera or an audience while their script has to stay out of sight:

• Creators recording screencasts and tutorials
• Trainers and teachers running online classes and webinars
• Speakers rehearsing conference talks

Typically solo, on their own machine, without a studio setup.

ViewForge's answer:

Shopify merchants whose customers need to know whether a part fits before they will buy it — and who do not have an engineer on staff to build that themselves.

Concretely: auto and truck parts retailers, powersports and motorcycle dealers, tractor and agricultural parts sellers, marine and outboard suppliers, small-engine and power equipment stores, bicycle and e-bike component shops, printer supply merchants, and electronics accessory sellers.

Catalog sizes run from a few dozen products on the free tier up into the tens of thousands; it is running in production on a catalog of roughly 40,000 SKUs. The common thread is not the industry — it is that "does this fit my thing" is the question deciding the sale.

Speechius's answer

I record programming tutorials for my own YouTube channel, and neither option worked for me: reading from a script sounds read, and improvising means losing the thread until a ten-minute recording takes forty. Existing teleprompters scroll at a fixed pace, so I ended up chasing the text instead of explaining.

I built the thing I wanted, and it turned into my first own product, released in July 2026.

ViewForge's answer:

ViewForge came out of agency work. Normal View was building for a parts retailer running roughly 12,000 SKUs who needed fitment search, and every app we evaluated stored the merchant's compatibility data in the vendor's own database.

That is a strange trade when you look at it directly. Fitment data is genuinely expensive to produce — it is weeks of work — and the merchant would not own the result. It would belong to whichever app happened to be installed that year.

Shopify metaobjects made a different answer possible: write fitment as native structured data inside the merchant's own store. The theme reads it, the Storefront API queries it, Admin GraphQL exports it, and it is still there after an uninstall. That decision is what the rest of the app is built around.

Everything else came from real catalogs rather than a roadmap. Eight verticals exist because a tractor catalog is not Year/Make/Model. Smart Parse exists because that retailer had already written fitment into 12,000 product titles, and nobody was ever going to retype them.

Speechius's answer

• Flutter for the user interface on macOS and Windows
• Apple Speech for on-device recognition and window exclusion on macOS
• Vosk, bundled as a local model, for recognition on Windows
• Ed25519 signatures for licence keys, sold through Paddle
• Sparkle for updates on macOS, Sentry for crash reporting

ViewForge's answer:

• TypeScript
• Shopify metaobjects, as the fitment data store
• Shopify theme app extensions for the storefront components: fitment search, saved-vehicle garage, compatibility table, product-page fit notice
• Shopify Storefront API, for querying fitment from the theme
• Shopify Admin GraphQL API, for writing and exporting fitment records
• NHTSA vehicle database, for VIN decoding
• ACES and PIES XML parsing, for automotive catalog import