Idk about everything else but I just tried to save a photo from iMessage and it is literally the second option (Save). Tried on my Mac and phone, no problems at all.

Edit: nvm I think this is an issue on ios13. Definitely weird design choice, wonder what is the story behind this decision.

Yeah, it's an iOS 13 issue. Illustrated here: https://imgur.com/a/giqdiAR

First screenshot: "Wait, why is 'copy' the only option?"

Second screenshot: What shows if you scroll past "copy", for which there's no visual indication showing that's even possible.

There's no rational reason for "copy" and all the other options to be visually separated, either. They could've been obviously part of one continuous set of options and it'd be a lot clearer to people.

>My apple dev account was originally a paid one though so maybe that has something to do with it?

Yeah that is why. I had a paid one also and I still have those perks.

From their Facebook page:

>Not seeing any documentation on https and puffin. If I log in using puffin, can your servers see my password?

Their answer:

>Yes. Puffin server will see your password even for HTTPS. The browser is physically running on the server. The closest analogy to Puffin is RDP (remote desktop).

Am I reading this right? Who in their right mind would use this shit?

This by itself is a good enough reason for Apple to reject the app on grounds of protecting customer privacy.

Liking it or not, of the major tech companies Apple has had a track record of caring about its users' privacy. I remember Tim Cook mentioning that as a basic value for him personally.

>The tool works in the browser by leveraging a minimal browser extension.

Am I dumb or it doesn't seem to work with Safari on Mac, which is the whole point of this thread?

You are not :) We just suck at explaining our tech very well and it takes a while to realise the value here because even I have not seen any other product offering packaged in the way we do it today - so it could be confusing initially. This is why I am starting threads like this.

The browser extension depends on the browser technology as the extension ecosystem is different for each vendor. Currently, we support Chrome and Firefox but due to Web Extensions API adoption, we will be supporting out of the box all 3 major browsers: Chrome, Firefox and IE Edge (no Safari I am afraid).

That being said, the packaged app will provide a standalone version as well which means that there is an easy transition between desktop and web users and all major platforms will be supported.

This is the plan at least.

> This is why I am starting threads like this.

Genuine question, but why not fix your own website to tell your product’s story rather than pepper the web with small pockets of useful info about your product leaving visitors to the real deal confused?

This is a good question. Of course, we are working on it and we are also building a very complex product at the same time. So while the main site is nowhere near what we want it to be it does not mean that we cannot publicly share what we are currently doing. And yes it would have been a lot more useful if I had shown you an amazing landing page but unfortunately it is not ready yet.

I hope that some of you may see a potential and although may disagree with the styles and color schemes keep faith in us and come back to check it out later when we have landed the themes, the desktop version and the new extension.

It is still useful application and all discussed changes are in the pipeline.