Would it really hurt to include a screenshot of what it's like to use? Sorry for the grouchy comment but we're all busy people, there has to be a modicum of convincing on a programmers part to encourage us to divert us attention to their project.
Some screenshots would be useful but I'm still rapidly developing Timestrap and the interface is getting stuff added to it every few hours so I feel like it'd be a wasted effort on my part right now. EDIT: Added some screenshots to the bottom of the readme
Show HN: Timestrap – Self-hosted online time tracking
11–20 of 78 posts
Re: Show HN: Timestrap – Self-hosted online time tracking
#12Timestrap currently does fully support time tracking and CSV exports for multiple projects and tasks. It has a full REST API and admin panel. Invoicing will come after I get the dashboard more fleshed out, more export options and better security.
Re: Show HN: Timestrap – Self-hosted online time tracking
#13Earlier quoted context omitted.
Some screenshots would be useful but I'm still rapidly developing Timestrap and the interface is getting stuff added to it every few hours so I feel like it'd be a wasted effort on my part right now. EDIT: Added some screenshots to the bottom of the readme
You could show off mock-ups you've done in Photoshop (and perhaps add a disclaimer) if you don't have a stable UI right now!
Re: Show HN: Timestrap – Self-hosted online time tracking
#14Re: Show HN: Timestrap – Self-hosted online time tracking
#15Re: Show HN: Timestrap – Self-hosted online time tracking
#16Server error 500. Well too bad then.
Re: Show HN: Timestrap – Self-hosted online time tracking
#17Would it really hurt to include a screenshot of what it's like to use? Sorry for the grouchy comment but we're all busy people, there has to be a modicum of convincing on a programmers part to encourage us to divert us attention to their project.
Some screenshots would be useful but I'm still rapidly developing Timestrap and the interface is getting stuff added to it every few hours so I feel like it'd be a wasted effort on my part right now. EDIT: Added some screenshots to the bottom of the readme
In the long run you can diff the images and assert that they haven't changed more than N% from the reference, but for now, it makes evergreen documentation.
Re: Show HN: Timestrap – Self-hosted online time tracking
#18Hello HN, developer here. I started this Friday night because I wanted something much simpler than all the options I was given and something that I could host myself. There is a lot to do on this project still and I wanted to see what the reception was for the start. Timestrap currently does fully support time tracking and CSV exports for multiple projects and tasks. It has a full REST API and admin panel. Invoicing…
Re: Show HN: Timestrap – Self-hosted online time tracking
#19Hello HN, developer here. I started this Friday night because I wanted something much simpler than all the options I was given and something that I could host myself. There is a lot to do on this project still and I wanted to see what the reception was for the start. Timestrap currently does fully support time tracking and CSV exports for multiple projects and tasks. It has a full REST API and admin panel. Invoicing…
I don't know if I speak for other users, but rather than focusing on invoicing, why not tie into Quickbooks? Or similar services. i.e. There's already invoicing software. If the integration between the timesheets is the only differentiator, why rewrite the invoicing part?
For my own use case I would like to have one location to enter time then select a range, hit "invoice" and be able to send that to a client with a very simple credit card payment system.
Re: Show HN: Timestrap – Self-hosted online time tracking
#20Earlier quoted context omitted.
Some screenshots would be useful but I'm still rapidly developing Timestrap and the interface is getting stuff added to it every few hours so I feel like it'd be a wasted effort on my part right now. EDIT: Added some screenshots to the bottom of the readme
Automate it! Set up a browser test that screencaps the important pages for the documentation (and checks them for basic errors like 500 status or no text). In the long run you can diff the images and assert that they haven't changed more than N% from the reference, but for now, it makes evergreen documentation.