Back to all news

Back

[Product Updates]

[Product Updates]

Product Update: Feature Lock Complete, Beta Launch Next Week

Product Update: Feature Lock Complete, Beta Launch Next Week

Product Update: Feature Lock Complete, Beta Launch Next Week

5 Dec 2025

We’ve reached a critical milestone: Amorfs Studio features are locked, and we’re in final preparation mode for our first cohort of 500 beta testers.

Where We Are

After months of development, we’ve completed feature lock for Amorfs Studio. This means no new features until after beta—only refinement, polish, and bug fixes.

This is an important moment. Feature lock represents our commitment to shipping something real, not perfect. We’re confident in what we’ve built, and now we need designers to stress-test it in the real world.

What’s Locked In

Here’s what our beta testers will experience:

Amorfs Studio

  • Template system – Create layouts using HTML/CSS with Amorfs data bindings

  • Visual preview – See your designs render in real-time

  • Template library – Browse and apply pre-created templates

  • Data styling – Control typography, spacing, colors, and responsive behavior

  • Export options – Generate and share styled outputs (text, image, Amorfs)

Privacy & Security

  • Zero-knowledge encryption – Data encrypted client-side before leaving your browser

  • Regional storage – Data stored in your geographic region

  • Selective sharing – Share specific collections while keeping others private

  • Full data control – Export, delete, or modify your data anytime

What’s NOT in Beta (Yet)

To ship on schedule, we’ve deferred these features to post-beta:

  • Core Capture & Reuse

  • Automatic web form capture – December

  • Mobile apps (iOS/Android) – Planned Q2 2026

  • Offline mode – Coming Q1 2026

  • Collaborative editing – Post-launch feature

  • Advanced API access – Developer preview Q2 2026

  • Template marketplace – Opens after beta validation

Beta feedback will determine the priority for these features.

The Final Sprint

Between now and our beta launch, our team is focused on:

Pre-Beta

  • Performance optimization – Template rendering speed improvements

  • Browser compatibility – Final testing across Chrome, Edge, Safari

  • Onboarding flow – Streamlining the first-run experience

  • Documentation – Template creation guides and API references

  • Infrastructure scaling – Preparing servers for 500 concurrent users

Week 1 of Beta (Nov 24-30)

  • Stability monitoring – 24/7 team availability for critical issues

  • Rapid bug fixes – Target 4-hour response time for blockers

  • Feedback collection – Structured surveys and Discord engagement

  • Template guidance – Helping designers through their first creations

What Beta Testers Will Do

We’ve designed a structured 6-week program that balances guided tasks with creative freedom:

Week 1: Foundations
Week 2: Exploration
Week 3: Innovation

Task: Create your personal business card template
Goal: Learn the template system, data bindings, and styling basics
Deliverable: One polished business card design

Task: Experiment with different data types (contact cards, travel itineraries, recipes)
Goal: Understand how templates adapt to various data structures
Deliverable: At least two templates for different use cases

Task: Create a template for something we haven’t imagined
Goal: Push the system’s boundaries, discover edge cases
Deliverable: One original template concept


Week 4: Community

Weeks 5-6: Refinement

Task: Review and vote on fellow designers’ templates
Goal: Identify what makes templates excellent
Deliverable: Feedback on at least 10 templates

Task: Polish your best work based on feedback
Goal: Create launch-ready templates
Deliverable: Final portfolio of 3-5 templates


Success Metrics

How will we know if beta is successful? We’re tracking:

Quantitative

  • Template creation rate – Target: 3+ templates per designer

  • Daily active usage – Target: 70% of testers active weekly

  • Data capture accuracy – Target: 95%+ successful captures

  • System stability – Target: 99%+ uptime

  • Template render performance – Target: Under 500ms for typical layouts

Qualitative

  • Designer satisfaction – Exit survey rating target: 4.5/5

  • Template quality – Are designs genuinely beautiful?

  • Use case diversity – Are designers creating things we didn’t anticipate?

  • Community engagement – Is the Discord active with helpful discussions?

  • Would-recommend rate – Target: 85%+ would recommend to colleagues

Known Challenges

We’re entering beta with our eyes open. Here are the challenges we’re aware of:

Technical

  • Complex layout edge cases – Print CSS and multi-column layouts need more testing

  • Large dataset performance – Templates with 100+ items may render slowly

  • Browser inconsistencies – Safari has some CSS rendering quirks

  • Form capture accuracy – Dynamic/JavaScript-heavy forms are challenging

Product

  • Learning curve – Template syntax may be unfamiliar to some designers

  • Documentation gaps – Advanced features need better examples

  • Template discoverability – Library browsing needs refinement

  • Feedback loops – Making it easy for designers to report issues

Beta exists precisely to surface these issues. We’re ready to iterate rapidly based on what we learn.


What Happens After Beta

The 6-week beta period ends around New Year. Here’s what follows:

Immediate (Post-Beta)

  • Analysis phase – 1 week to synthesize all feedback

  • Critical fixes – Address any blockers discovered in beta

  • Template curation – Select best designs for launch showcase

  • Documentation update – Incorporate learnings into guides

Public Launch (Target: Late February/Early March)

  • Open access – Anyone can install and use Amorfs

  • Template library – Curated collection from beta testers

  • Beta tester recognition – Showcase of designers and their work

  • Press announcements – Product Hunt, tech media outreach

Q1 2026

  • Public API release – Developer access to Amorfs data

  • Premium tier – Advanced features and extended storage

  • Enterprise features – Team collaboration and security controls

  • Template marketplace – Designers can sell their templates

Why This Matters

Feature lock is more than a technical milestone. It represents a philosophical commitment.

We could keep building in isolation for another six months. We could add more features, polish every edge case, chase perfection.

But the best products are built in conversation with their users. Real designers, working with real data, creating real templates—that’s how we’ll discover what Amorfs should become.

Beta testing isn’t about validating what we’ve built. It’s about learning what we should build next.

Join Us

Applications for our first 500 beta testers open Monday, November 17 at 9am AEDT.

If you’re a front-end designer who wants to shape how people experience data, this is your moment.

How to apply:

500 spots. First come, first served.

See you Monday.

Stay Updated

We’ll be posting weekly product updates throughout beta:

  • Week 1: Beta launch and first impressions

  • Week 2: Early template showcase

  • Week 3: Technical deep dive on what we’re learning

  • Week 4: Community voting results

  • Weeks 5-6: Launch preparation updates


-
Subscribe to this blog or follow us on social media to stay in the loop.

Beta applications open: Monday, November 17, 9am AEDT
Questions? Email beta@amorfs.com
Follow: @amorfshq (X) | First Cognition (LinkedIn)

Amorfs: Your data, beautifully organized. Finally.


We’ve reached a critical milestone: Amorfs Studio features are locked, and we’re in final preparation mode for our first cohort of 500 beta testers.

Where We Are

After months of development, we’ve completed feature lock for Amorfs Studio. This means no new features until after beta—only refinement, polish, and bug fixes.

This is an important moment. Feature lock represents our commitment to shipping something real, not perfect. We’re confident in what we’ve built, and now we need designers to stress-test it in the real world.

What’s Locked In

Here’s what our beta testers will experience:

Amorfs Studio

  • Template system – Create layouts using HTML/CSS with Amorfs data bindings

  • Visual preview – See your designs render in real-time

  • Template library – Browse and apply pre-created templates

  • Data styling – Control typography, spacing, colors, and responsive behavior

  • Export options – Generate and share styled outputs (text, image, Amorfs)

Privacy & Security

  • Zero-knowledge encryption – Data encrypted client-side before leaving your browser

  • Regional storage – Data stored in your geographic region

  • Selective sharing – Share specific collections while keeping others private

  • Full data control – Export, delete, or modify your data anytime

What’s NOT in Beta (Yet)

To ship on schedule, we’ve deferred these features to post-beta:

  • Core Capture & Reuse

  • Automatic web form capture – December

  • Mobile apps (iOS/Android) – Planned Q2 2026

  • Offline mode – Coming Q1 2026

  • Collaborative editing – Post-launch feature

  • Advanced API access – Developer preview Q2 2026

  • Template marketplace – Opens after beta validation

Beta feedback will determine the priority for these features.

The Final Sprint

Between now and our beta launch, our team is focused on:

Pre-Beta

  • Performance optimization – Template rendering speed improvements

  • Browser compatibility – Final testing across Chrome, Edge, Safari

  • Onboarding flow – Streamlining the first-run experience

  • Documentation – Template creation guides and API references

  • Infrastructure scaling – Preparing servers for 500 concurrent users

Week 1 of Beta (Nov 24-30)

  • Stability monitoring – 24/7 team availability for critical issues

  • Rapid bug fixes – Target 4-hour response time for blockers

  • Feedback collection – Structured surveys and Discord engagement

  • Template guidance – Helping designers through their first creations

What Beta Testers Will Do

We’ve designed a structured 6-week program that balances guided tasks with creative freedom:

Week 1: Foundations
Week 2: Exploration
Week 3: Innovation

Task: Create your personal business card template
Goal: Learn the template system, data bindings, and styling basics
Deliverable: One polished business card design

Task: Experiment with different data types (contact cards, travel itineraries, recipes)
Goal: Understand how templates adapt to various data structures
Deliverable: At least two templates for different use cases

Task: Create a template for something we haven’t imagined
Goal: Push the system’s boundaries, discover edge cases
Deliverable: One original template concept


Week 4: Community

Weeks 5-6: Refinement

Task: Review and vote on fellow designers’ templates
Goal: Identify what makes templates excellent
Deliverable: Feedback on at least 10 templates

Task: Polish your best work based on feedback
Goal: Create launch-ready templates
Deliverable: Final portfolio of 3-5 templates


Success Metrics

How will we know if beta is successful? We’re tracking:

Quantitative

  • Template creation rate – Target: 3+ templates per designer

  • Daily active usage – Target: 70% of testers active weekly

  • Data capture accuracy – Target: 95%+ successful captures

  • System stability – Target: 99%+ uptime

  • Template render performance – Target: Under 500ms for typical layouts

Qualitative

  • Designer satisfaction – Exit survey rating target: 4.5/5

  • Template quality – Are designs genuinely beautiful?

  • Use case diversity – Are designers creating things we didn’t anticipate?

  • Community engagement – Is the Discord active with helpful discussions?

  • Would-recommend rate – Target: 85%+ would recommend to colleagues

Known Challenges

We’re entering beta with our eyes open. Here are the challenges we’re aware of:

Technical

  • Complex layout edge cases – Print CSS and multi-column layouts need more testing

  • Large dataset performance – Templates with 100+ items may render slowly

  • Browser inconsistencies – Safari has some CSS rendering quirks

  • Form capture accuracy – Dynamic/JavaScript-heavy forms are challenging

Product

  • Learning curve – Template syntax may be unfamiliar to some designers

  • Documentation gaps – Advanced features need better examples

  • Template discoverability – Library browsing needs refinement

  • Feedback loops – Making it easy for designers to report issues

Beta exists precisely to surface these issues. We’re ready to iterate rapidly based on what we learn.


What Happens After Beta

The 6-week beta period ends around New Year. Here’s what follows:

Immediate (Post-Beta)

  • Analysis phase – 1 week to synthesize all feedback

  • Critical fixes – Address any blockers discovered in beta

  • Template curation – Select best designs for launch showcase

  • Documentation update – Incorporate learnings into guides

Public Launch (Target: Late February/Early March)

  • Open access – Anyone can install and use Amorfs

  • Template library – Curated collection from beta testers

  • Beta tester recognition – Showcase of designers and their work

  • Press announcements – Product Hunt, tech media outreach

Q1 2026

  • Public API release – Developer access to Amorfs data

  • Premium tier – Advanced features and extended storage

  • Enterprise features – Team collaboration and security controls

  • Template marketplace – Designers can sell their templates

Why This Matters

Feature lock is more than a technical milestone. It represents a philosophical commitment.

We could keep building in isolation for another six months. We could add more features, polish every edge case, chase perfection.

But the best products are built in conversation with their users. Real designers, working with real data, creating real templates—that’s how we’ll discover what Amorfs should become.

Beta testing isn’t about validating what we’ve built. It’s about learning what we should build next.

Join Us

Applications for our first 500 beta testers open Monday, November 17 at 9am AEDT.

If you’re a front-end designer who wants to shape how people experience data, this is your moment.

How to apply:

500 spots. First come, first served.

See you Monday.

Stay Updated

We’ll be posting weekly product updates throughout beta:

  • Week 1: Beta launch and first impressions

  • Week 2: Early template showcase

  • Week 3: Technical deep dive on what we’re learning

  • Week 4: Community voting results

  • Weeks 5-6: Launch preparation updates


-
Subscribe to this blog or follow us on social media to stay in the loop.

Beta applications open: Monday, November 17, 9am AEDT
Questions? Email beta@amorfs.com
Follow: @amorfshq (X) | First Cognition (LinkedIn)

Amorfs: Your data, beautifully organized. Finally.


Share to

PRODUCTS

Amorfs Extension

FORUM

SUPPORT

Don’t want to miss anything?

Get weekly updates on the newest posts, events and tips right in your mailbox.

© 2025 Amorfs. All rights reserved.

Don’t want to miss anything?

Get weekly updates on the newest posts, events and tips right in your mailbox.

© 2025 Amorfs. All rights reserved.

PRODUCTS

Amorfs Extension

FORUM

SUPPORT

Don’t want to miss anything?

Get weekly updates on the newest posts, events and tips right in your mailbox.

© 2025 Amorfs. All rights reserved.