3 ms·
The shot->image-process->save->share cycle takes user time, and is an inconvenience that some people will even pay money to avoid. Since we're talking about scr
by indymike 6y ago
The shot->image-process->save->share cycle takes user time, and is an inconvenience that some people will even pay money to avoid. Since we're talking about screenshots, we're actually talking about typically, developers, tech writers and marketers who are automating their day-to-day workflow.
- WesolyKubeczek 6y agoShot - share to your fancy shmancy editor that puts a phone frame around it - put a frame around it - save somewhere. Here, simplified that for you. You can totally make an app that streamlines this and doesn’t cast doubts on its privacy hygiene at the same time.
- indymike 6y agoActually, other than being humorous, you just said, do it the way I want you to without any understanding of why a user may not want to do it that way.
- IggleSniggle 6y agoI think the person you are replying to is saying that the entire flow is a single action: you hit screen shot, and the screen shot is taken, edited, and shared to some configured entity, in one step. Seems pretty obvious to me why a single step that doesn’t remove you from app flow would be waaaayyy more useful than needing to use any other apps to complete the job.