I'd actually focus on few things:
- Show the workflow or the pain-point you're solving via a video.
- Developers might not worry too much about this you need to reach people who require Jira updates like managers, agencies, C-suite folks etc.
- Make it trustful, be explicit about: what is read, what is stored, what never leaves the machine, whether it works offline etc.
It runs on your machine locally, understands your work and takes care of your Jira task updates for you. No data leaves your machine
This is where it is right now, but the idea is that it does all the boring stuff developers hate to do and don't have to do, if it can see what you do then it can learn and take care of those things that can be taken care of
I'd actually focus on few things: - Show the workflow or the pain-point you're solving via a video. - Developers might not worry too much about this you need to reach people who require Jira updates like managers, agencies, C-suite folks etc. - Make it trustful, be explicit about: what is read, what is stored, what never leaves the machine, whether it works offline etc.
Sure and any suggestions on processes to follow to make some good open-source impressions and github stars?
It runs on your machine locally, understands your work and takes care of your Jira task updates for you. No data leaves your machine
This is where it is right now, but the idea is that it does all the boring stuff developers hate to do and don't have to do, if it can see what you do then it can learn and take care of those things that can be taken care of