I'm having a super frustrating experience trying to *securely* deliver my framer prototype to a 3rd party research company in a foreign country.
Framer Cloud goes into an endless loop of sending a link to the invitee and then the linked page says to look for an email with a link.
I tried setting up my own server with a directory that was secured using .htaccess. But the mobile app doesn't support this kind of authentication.
It's cost me and my team a lot of hours in trying to find a way to make this work, and has had the effect of creating a pretty negative view of the tool.
Has anyone found a good way to securely deliver these prototypes?
I'm so sorry. Edwin can help look into what is going on with the looping invite. And you are right that the app does not support http auth.
My best advice for right now would be to create a "secret" public link as in one that is very hard to guess. Framer Cloud does this by default (we don't publish them anywhere), but if you need a longer more random one, Dropbox does a fine job.
Is the 3rd party team tech savvy? Meaning, do they have the ability to run 'npm install' and gulp to compile and then launch the framer prototype?
If they are you might look at something like this. “How to Run Framer JS on Windows” @joeday https://medium.com/microsoft-design/how-to-run-framer-js-on-windows-94e6a06abfe4
It's a possible solution which would guarantee security, and demonstrate software development best practices to your client. The framer project would be in source control [in the clients repo even].
They would then be able to pull the latest source, run gulp from command line, and then experience your prototype.
Hi Eli, I've been making some tweaks that should address the looping issue. Can you let me know if you're still seeing this?