Help others use what you built.
Documentation software for developers.
Make your software easier for other people to understand and use. Create setup guides, walk through a feature, and give QA or support the context they need.
Windows app. Markdown notes. Shareable guides.
How the new date filter works.
Start with a test account that has report access and sample data.
- 1Choose a date range
Select the previous month or enter a custom range.
- 2Apply and check the results
The report shows records within the selected dates.
- 3Check an empty range
A range with no records should show the empty state.
Check populated and empty results.
Use these steps to explain the filter.
The code is only part
of the handoff.
Someone needs to configure it, test it, or explain it to a user. Give them a guide built around the job they need to do.
- Feature walkthroughs
- Show how a workflow behaves, where to find it, and which details support teams need to explain to users.
- QA handoffs
- Give testers the prerequisites, paths to check, and expected results, with screenshots to make the behavior clear.
- Reproduction steps
- When something fails, record the sequence and add expected versus actual behavior so a teammate can investigate.
From working software to a useful guide
Document it as
you walk through it.
Start with a setup, feature, or test scenario. Capture the workflow, then add the knowledge someone else needs to follow it.
- 01
Capture the workflow.
Record supported browser interactions or capture the relevant window. Show the settings and steps in the order someone will use them.
- 02
Explain the technical details.
Add prerequisites, configuration choices, and expected results in Markdown. Reorder steps, annotate screenshots, and redact sensitive details.
- 03
Share with the right people.
Publish a guide for your teammate, QA, or support team. Link it from an onboarding document or issue, or export HTML or Markdown.

Help the next developer get started
Make the setup
easier to repeat.
A teammate is joining the project. They need the right settings, access, and a way to check that everything works.
Combine captured screens with Markdown instructions. Explain why a setting matters and what a successful setup looks like, so they can follow the guide without reconstructing your decisions.
- Prerequisites and application settings
- Configuration and deployment procedures
- A first-run check with the expected result
Know what you're working with
A few useful
specifics.
- Capture
- Supported browser interactions, plus Windows window and region screenshots. Available context depends on the capture method.
- Explain
- Titles, Markdown, source links, annotations, crops, and redactions. Original screenshots are preserved.
- Deliver
- Published guides with audience controls, HTML, and Markdown. Review content and sharing permissions before sending.
- Start
- Use the Windows app locally without an account. Cloud and AI features require additional setup.
Details before the download
Good questions.
Does UIHike record every application in the same way?
Can I include Markdown and technical notes?
Can I redact a screenshot without losing the original?
What can I share or export?
Does this automatically open an issue in GitHub or Jira?
Do I need AI to use it?
Give the next person
more than the code.
Start with one setup, feature, or handoff you need to explain.
Free during beta. Windows app.
