Videos can be embedded. Documents can be embedded. Spreadsheets can be embedded.
But what about geometry?
For the past decade, whenever a product needed users to draw a geometry problem, edit a dynamic figure, or save an interactive geometry asset, the workflow usually broke in the same place: leave the product, use a separate tool, take a screenshot, and paste it back. That fractured workflow has sat in the middle of education platforms, teaching research systems, and AI math products for years.
Today, Algeo SDK 2.0 embedded editing mode is officially available. Geometry is no longer the missing embeddable format. It can now live inside your product like a standard component, with data flowing back into your business system, UI matching your product design, and permissions staying under your own control.
Here are five common scenarios we see. If any of them sounds like your product, this release is worth a closer look.
Scenario 1: online education platforms can let teachers create geometry problems in place
A high school math teacher is preparing tomorrow's geometry lesson on your platform. She needs an example problem about angle proofs in a circle.
Before: she opened a separate geometry tool, finished the diagram, took a screenshot, and pasted it back into your question bank. The text lived in one place and the image in another. Students saw a static picture that could not be dragged, edited, or reused after the test.
Now: she clicks "insert geometry board" in your question bank admin, and the Algeo editor opens in place. Circles, points, and auxiliary lines are created in the same workflow. When she saves, the board data enters your question bank and is bound to her account, school, and textbook chapter.
When students open the problem, they can drag a point on the circle and see the angle change directly. Throughout the whole process, your product stays in control: the data is yours, the permissions are yours, the content rights are yours, and the user behavior logs are yours.
Scenario 2: AI math products can let AI and students work on the same board
This is one of the fastest-growing customer categories we have seen over the past year.
A student uploads a photo of a geometry problem. Your AI parses the problem and generates a solution path. But text alone is not enough. The student needs to see why an auxiliary line is drawn that way, and needs to test by hand whether an equality still holds when a point starts moving.
Algeo embedded editing closes that loop for the first time:
- After AI parsing, code can generate board content and load it into the editor automatically
- Students interact directly inside your product by dragging, modifying, and trying alternatives
- Every student edit can be sent back to your system as an event and used in the next AI analysis round
- AI can respond to the student's specific change instead of giving generic explanation
Education is a feedback loop. Text plus static diagrams can no longer carry that loop for geometry. The missing piece is a board that can be driven by code while still giving students hands-on control.
Scenario 3: educational publishing can turn geometry assets into a managed production workflow
In many publishing workflows, geometry illustrations used to operate like a separate workshop: an author drew the figure, a designer remade it as vector art, an editor reviewed it, and a layout designer processed it again. One geometry asset for one problem could pass through four tools and five people.
After embedding Algeo into a content management system, that pipeline becomes much flatter:
- Authors write problems and draw figures directly in the CMS, with assets stored as structured geometry data rather than images
- Editors can open the original board and revise it directly instead of asking the author to recreate it
- The same geometry data can export to PDF, web, print, and interactive courseware: draw once, reuse everywhere
- Version control stays inside the CMS, so geometry boards stop being external unmanaged files
For content organizations, this is not just about saving one tool. It is about turning geometry into a managed asset.
Scenario 4: schools and institutions can finally build a shared geometry asset library
Teaching research has an old pain point: Chinese language groups have material libraries, English groups have corpora, math teams have question banks, but geometry often remains scattered. Every teacher has dozens of local geometry source files. They leave with the teacher, disappear with an old computer, and are hard for new teachers to inherit.
When an institution embeds Algeo into its collaborative teaching research platform:
- Geometry assets enter the institutional asset library and can be organized by subject, grade, and knowledge point
- Teachers can remix the same board while keeping a complete revision history
- New teachers can receive accumulated geometry resources on day one
- Permissions and approvals follow the institution's own rules, including what can be shared broadly and what stays inside a subject group
Scenario 5: question banks and homework systems can make geometry a first-class format
Many question bank systems have structured templates for multiple choice, fill-in-the-blank, and written-response questions. Geometry is often still just an image. That creates three limits:
- Similar-question recommendation is weak because the system cannot tell whether two geometry problems share the same mathematical structure
- Fine-grained grading is hard because the student's answer often comes back as another image
- Learning analytics are shallow because the system cannot see which construction step caused the student to get stuck
Once Algeo turns geometry problems into structured data, these workflows become possible:
- Both the problem and the solving process are structured, so the question bank can handle geometry more like algebra
- Every student operation can be reported back, allowing the grading system to locate which point was moved at which step
- Learning analytics can tell a teacher that 70% of a class did not think to draw a specific auxiliary line
What is ready at the technical level
The scenarios are compelling, but production adoption is always an engineering problem. Algeo SDK 2.0 is designed to be production-ready in several core areas.
Bidirectional communication with clear data ownership
Every edit, board switch, and save request can be sent back to the host application through postMessage. You control the save button. The iframe does not bypass your business system to persist anything directly. When to save, where to save, and which permissions are required are all decided by your backend. The SDK only maintains the UI state for saved and unsaved changes.
Fully configurable UI that fits into your product
The navigation bar, board list, toolbox, algebra panel, and document panel can each be toggled independently at runtime. In an AI-assisted scenario, the editor can be reduced to a clean canvas. In a professional authoring scenario, the full toolchain can be shown. In advanced integrations, you can even replace our board list with your own UI and drive it through the SDK capability APIs.
Engineered capability layers
The SDK separates editor capabilities into four clear units: board file document, multi-board slides, history, and display mode. Each unit can be called independently, which also gives us room to improve each one over time without breaking the others.
Versioned protocol for long-term evolution
Every handshake between the SDK and iframe carries a protocol version. That means an integration you build today can continue to work after future upgrades, while still allowing us to deliver new capabilities without asking you to rewrite the integration every time.
Production-oriented robustness
The SDK includes a 30-second initialization timeout, standardized error codes, a clean destroy lifecycle, and self-hosted base URL support through baseUrl. These details matter when a real product faces network jitter, CSP rules, and complex route changes in single-page applications. We have already validated the approach in multiple production customer environments.
Why choose Dino-GSP and Algeo
There are very few teams in China that can build a dynamic geometry editor at this level. We spent a year making it production-ready, then another release cycle turning it from a product into a component. Geometry as a category really opens up only when it can be installed inside any product.
If your product contains the word "geometry", whether in K12, higher education, AI math, educational publishing, or teaching research, we would be glad to talk.
Docs: open.dajiaoai.com
Repository: github.com/dajiaoai/algeo-sdk
Put a geometry board inside your product, starting today.
Top comments (0)