Ask HN: How do you share and update the app specifications with your team?
2 comments
Tests are the only spec I know of that stays up to date. It’s code that is executed regularly and has to change by design if specs change. That doesn’t help a ton in your case as writing tests against specific animations would be very hard to maintain.
The best I have found for stuff like you are dealing with is to put the questions I have in a team/public slack channel and make sure the docs/designs are updated when the question is answered. This will be easier with some groups than others.
The best I have found for stuff like you are dealing with is to put the questions I have in a team/public slack channel and make sure the docs/designs are updated when the question is answered. This will be easier with some groups than others.
I ran a software agency for 8 years, and as soon as you get past the problem of finding work, and finding good talent - I believe this is a problem we all face.
I’m working on a solution right now, a source of truth for software requirements https://userdoc.fyi
I’m working on a solution right now, a source of truth for software requirements https://userdoc.fyi
I have developed various apps for several clients. One of the problems I face every time the application specifications are not fully expected or written in various places and are not up-to-date.
These days, many clients write screen design and screen transitions in Figma and more detailed behavior specifications in Notion. However, often the Figma is out of date, or the content in the Notion does not match the Figma, and in the end I have to ask the product manager via Slack or Zoom.
Have you ever encountered these problems? How did you solve them? Any sophisticated ways to share app specs or keep them up-to-date?