Why I made Fully McFullface
I kept running into the same small problem: I could see exactly what needed changing on a webpage, but showing it to someone else took far too much explaining.
It should not take this much fuss
Sending a cropped screenshot lost the surrounding context. Capturing the whole page helped, but then I had to open another tool, add an arrow or note, save another file and find it again.
None of those steps was especially difficult. Together, they were annoying.
So I made the tool I wanted
Fully captures the whole webpage, lets me mark up the exact change and copies one finished image. I can paste it into an AI tool, an email, a chat or a document. Fully does not choose the destination or send the image for me.
Capture. Mark up. Copy. Paste. That is the whole job.
The philosophy is simple
I like tools that are obvious. You should not need an account, a tutorial course or ten minutes of setup to do a small everyday job.
Fully has no advertising and no automatic uploads. Screenshots are handled on your device. I am not trying to turn it into a complicated platform. I would rather keep improving the one job people came for.
The test is simple: does the tool save more effort than it creates?
It is still a work in progress
Fully started as something I wanted in my own browser. I now notice when it is not installed, which is probably the most honest sign that it is useful.
It is still a young product. Some webpages are difficult to capture, some browser pages are off limits and there is more to learn.
If something feels confusing or annoying, tell me. That is more useful than pretending the product is finished.
Tell me what you think