Any recommendations to write requirements for Product Development using Low/No Code Tools?

Question

I observed the following options to write both technical and business requirements to describe product behaviour or data schema and documentation

1. Detailed Specification(SRS) using word/Google Documentation according to template (I think Traditional Development may use )
2. Use Wiki Page or Online Editor like notation or git markdown or other pattern(Make live specification)
3. Use User stories using any project management tool like JIRA etc
4. Follow Figma Designs or Similar Designs

Do you think using gherkin (https://cucumber.io/docs/gherkin/reference/) and user stories effective option for long term product development ?

Suppose, User is planning to use any Low Code/No Code Tools like Bubble to build the application, Do you have any suggestion to write requirements? will maintaining simple word document and wiki page is sufficient? Any other suggestions to consider  based on your experience

Ryan Zhang · Accepted Answer

When crafting requirements for product development with Low/No Code tools, it's crucial to focus on clear, user-centric objectives and the specific outcomes you aim to achieve. This approach ensures that the development process remains agile and aligned with your users' needs, making the most of the flexibility offered by these tools.

Any recommendations to write requirements for Product Development using Low/No Code Tools?

Replies