March was a product-heavy month for Formaly.
On the surface, the releases look unrelated: SDK targeting, slash commands, AI themes, PDF import, paste-to-create, response quality checks, and language analytics. But they all push in one direction, Formaly is becoming a feedback system, not just a form builder. Here is what shipped and why each piece matters.
Formaly SDK
The biggest release is the Formaly SDK.
Most surveys are sent too late. A user hits friction inside the product, and days later gets an email asking what happened, by which point the memory is weak and the context is gone. (Timing isn't a small factor: a trigger that fires within the hour reliably beats a weekly batch send.)
The SDK lets teams ask questions inside the product, based on triggers like page view, delay, scroll depth, exit intent, element click, or a manual Formaly.show() call, with targeting conditions and cooldowns so it stays respectful. More on the engineering in In-Product Targeting.
Slash-command editing
Survey editing should feel fast. The new slash-command editor lets you type / and drop in question blocks instantly, multiple choice, rating, ranking, matrix, slider, email, phone, and more.
It is a small interaction that changes how the builder feels. Instead of hunting through menus, you stay in the flow of writing.
AI theme generation
Brand trust matters in surveys, respondents engage more when the experience clearly belongs to the company asking. AI theme generation lets you describe a brand and get a first-pass theme: colors, type direction, background treatment, and interface styling. The goal is not to replace design taste; it is to reach a better starting point faster.
PDF import and paste-to-create
Old forms already exist. Teams have questionnaires in PDFs, intake documents, applications, and research docs, and rebuilding them by hand is slow and error-prone. PDF import extracts the questions so you can edit instead of retype.
Paste-to-create covers the same problem for non-PDF sources: questions living in an email, a doc, a spreadsheet, a Notion page, or an old survey export. Both are part of the broader idea that creation should meet your work where it lives.
Quality checks
Response quality is a real problem, low-effort answers, inconsistent responses, suspicious patterns, and unusual geolocation signals can all distort a result. Formaly now surfaces quality signals so you can review responses with more context. These checks are not final truth; they are useful warnings, and they fit into the broader analytics layer.
Language analytics
Language patterns reveal whether a survey is reaching the audience you expected, and whether localization matters. Language analytics gives teams more visibility into who is responding and how surveys perform across audiences, which pairs naturally with translation management.
What I am optimizing for
The product direction is simple:
- Help teams create better surveys faster.
- Help them ask at the right moment.
- Help respondents finish with less friction.
- Help teams trust and understand the data.
That is the loop I care about. March moved Formaly meaningfully closer to all four.