close
ShipstryBeta

Share what is broken, missing, or worth building next.

Use the quick form for structured product feedback, or reach out directly if you want a longer conversation. We read every report.

Quick feedback form

Best for bug reports, UX issues, feature requests, and product ideas that benefit from a structured report.

Use the form

Email

Best for private details, screenshots, or longer context that is easier to explain asynchronously.

hi@shipstry.com

Discord

Best for quick back-and-forth discussion with the team and the wider maker community.

Join Discord

X / Twitter

Best for public shout-outs, lighter feedback, and ideas you want to surface in the open.

@shipstry
Before You Send

What helps us fix things faster

A little structure in the report usually saves a lot of back-and-forth.

Include the page where the issue happened.

Describe what you expected and what actually happened.

Mention whether you were signed in, on mobile, or on desktop.

Use email or Discord if you need to attach screenshots or recordings.

Looking for general info first? Check the FAQ.

What Happens Next

What to expect after you send feedback

Quick feedback is meant to be lightweight, but not disposable.

We read every report and use them to prioritize fixes and product improvements.

Leave an email if you want a reply or if the team may need more context.

For urgent issues, private details, or attachments, email or Discord is still the better route.

Quick Feedback

Send a structured report

Best for bug reports, product ideas, and feature requests that are easier to route when the context is written down clearly.

0/2000 characters

Optional. Leave an email if you want a follow-up.