What's everyone's workflow for sharing their protos with devs? Do you host your prototype somewhere? I'm reluctant to hit the "share" button, as what I'm working on is confidential :/
You can send the source files directly.
I get local file restrictions when I don't open with Framer though... guessing there's a way around that
I have a website I upload them to, with the rest of our documentation.
Have them get framer or have them use an http server (devs should be familiar with Python SimpleHTTPServer)
Chase Curry I'm sure devs have a localhost installed? Just place the example.framer folder in localhost and then navigate to http://localhost/example
It's almost impossible someone would guess or accidentally reveal your link. What are you afraid of?
I deploy mine on a free Heroku instance and run them on a small Express.js server. It's literally two extra files and 10 lines of code.
Interesting... thanks all. Will mention these options to the devs
And you can add password protection with 4 extra lines of code.
Josef Richter he's afraid of his companies net security team hassling him about releasing confidential info, not about info actually being leaked. This is actually a really big concern for corporate users of framer.
How about private Bitbucket/Github repo
Could also work, though would still need someone to run a localhost I'm guessing
Jesper - I'm interested in learning more about your setup... Can you point me in the right direction?
Im with Jordan, please share Jesper :)
I'll post the code and a short explanation on git a little later :-)
Gist, not Git. It requires a github account or Heroku Toolbelt (and node.js and NPM) installed. But everything requires node and git these days anyway :-)
I created a guide for deploying your Framer prototypes to Heroku with password protection: https://gist.github.com/woeldiche/4a49103bcc1f669f5925
Simpler version of Jesper Wøldiche solution for dummies like me: you just copy-paste two files to your Framer folder and push it to Heroku.
Thanks Jesper! I've been a heroku user for like 5 or 6 years now... But I really appreciate the guide!
The benefit of the node.js version with an extra file is the ability of being able to run it locally with a simple 'npm install' instead of having to setup and configure Apache and PHP. But both work equally well once configured.
Jesper Wøldiche and any other people who want to run a server to just serve static files: `python -m SimpleHTTPServer` from the directory you want to serve
That reminds me, need to take a look at that ol' python script for colleagues.. simply running the script in the project root spins up the SimpleHTTPServer- I'd hate to ask them to type it in terminal.
well, you can run that PHP shit locally too - in Framer studio, in browser, in frameless, whatever you do now. the point was to avoid setting up any custom directory structure etc. but in principle the solution is the same.
It'd be cool to have Framer Studio export a mac app that just packages the prototype with a small script to run the python server. Framer Viewer.
Could be a separate app that just packages up the open prototype as well. If the share button opened up a share sheet it could plug into that to give you that option instead of uploading to share.framer.com
I guess you reach for the tools you know. I don't have much experience with Python :-) Since framer uses JS, node.js seemed a good choice.
Also I didn't know what platform the OP wanted to run it on.
You could easily create an app from your prototype using Electron http://electron.atom.io/ for both OSX, Windows and Linux.
Thanks for the write up Jesper Wøldiche - worked like a charm!