Pieceflow Support

Start here

Use this page for public support information for Pieceflow.

Contact

• Product support: `support@dartscreative.com`
• Privacy questions: `privacy@dartscreative.com`

Metadata

• App: `Pieceflow`
• Locale: `en-US`
• Purpose: canonical source Help front door for future localization
• Status: `draft-source`
• Source of truth owner: Portfolio Core
• Last updated: 2026-04-21

1. Start here

Choose the calculator that matches the fabric question you need to answer right now.

`Pieceflow` is meant to help with bounded quilt-planning math, not to replace every quilting instruction or pattern note.

2. Use the right inputs

Enter the finished dimensions or values the calculator asks for, then confirm the unit system before reading the result.

If a project still depends on pattern-specific seam allowances, piecing assumptions, or custom construction steps, keep those separate from the app’s bounded math.

3. Read the result honestly

Treat the result as planning math for backing, binding, borders, batting, strip yield, or a saved project sheet.

Do not read the app as a pattern validator, certification surface, or substitute for checking your own fabric plan before cutting.

4. Save a project when

Save the project sheet when you know you will come back to the same quilt plan later.

If the project changes materially, update the values before cutting instead of trusting an older saved sheet by habit.

5. Contact support when

Contact support if:

• the math looks wrong for the values you entered
• the wording feels unnatural in your locale
• unit or yardage phrasing looks confusing
• a saved project sheet appears inconsistent with the current inputs

Include:

• which calculator you used
• the values and units you entered
• the locale you selected
• what looked wrong
• whether the issue was math, wording, or saved-project behavior

Metadata

• App: `Pieceflow`
• Locale: `en-US`
• Purpose: canonical source FAQ for future localization
• Status: `draft-source`
• Source of truth owner: Portfolio Core
• Last updated: 2026-04-21

1. What is Pieceflow?

`Pieceflow` is a calm, local-first quilting calculator.

It helps with bounded quilt-planning math such as backing, binding, borders, batting, strip yield, and simple saved project recall. It is intentionally narrow. It is not a sewing suite, pattern marketplace, or social quilting network.

2. What does Pieceflow calculate?

`Pieceflow` currently focuses on bounded quilting math, including:

• backing yardage
• binding length and strip count
• border yardage
• batting size
• strip-from-fabric yield
• saved project sheets for the current quilt plan

The app is designed for planning math, not for replacing every project instruction.

3. Does Pieceflow replace a quilt pattern?

No.

`Pieceflow` helps with reusable planning math. It does not certify pattern correctness, construction order, seam handling, or final fabric decisions for every quilt pattern.

4. Does Pieceflow support different units and locales?

Yes.

The app is intended to localize wording and unit presentation across its world-stage locale bundle. Locale mainly controls how the app speaks and presents values. It does not turn the app into a pattern authority for one country or quilting tradition.

5. Does Pieceflow need an account?

No.

The core product posture is local-first and paid upfront. The app does not require sign-in, cloud sync, or a backend to do the main job.

6. Where is my data stored?

Saved project sheets are kept on the current device in the current product posture.

If that storage posture changes later, the support and privacy surfaces should say so explicitly.

7. Does Pieceflow track me or upload my projects?

No account, sync, or remote project-processing posture is part of the current core product boundary.

8. What should I do if the math or wording looks wrong?

Use the Help front door first to confirm you chose the right calculator and unit system.

If the result or wording still looks wrong, contact support and include:

• which calculator you used
• the values and units you entered
• the locale you selected
• what looked wrong
• whether the issue was math, wording, or saved-project behavior