I was wondering about that for a while now - it feels in my last few jobs as an EM, the major part of my work (or rather the most influential one?) was managing, coaching and guiding product. The realization was actually quite simple for me: while hiring in engineering is defined by an sometimes absurd number of interviews, code challenges and so on, product is a case study and you're good: and that doesn't seem to be doing the trick.
Building Split Flap Displays. Started 18 months ago and kept me on a super interesting learning path. First shot was using open source designs (https://github.com/scottbez1/splitflap), but then kept building more and more parts myself. Coming from a software engineering background, getting into designing mechanical things – and then more importantly the electronics around it - has been really challenging, but also very rewarding. At this point I have my own screen printed flaps, custom PCB Design and a, what I consider, really smart protocol that allows me to daisy chain a basically arbitrary number of display elements. It's fun!
Came here to say the same thing: If you're interested in seeing the traffic caused by your own app (and also making that info accessible to other stakeholders during dev time), netfox is the way to go. Super easy to integrate and provides usually enough info. Also no tinkering with the system settings or third party apps required.
So, this is something i've been working on for a while now. What it does is enable you to use cocoapods to integrate prebuilt frameworks for any pod. binpod does this by recompiling pods into a .framework and republishing that pod to its own spec repository. All you need to do is to add a line to your Podfile and you're got to go.
Sessions are ephemeral – once you close the tab or browser window, the session is gone (and the viewer will go back to the 'waiting for content' screen). This is by design – frop is meant for realtime collaboration or presentations, so having something stick around forever is not really the use case (in my head).
At the moment it's one viewer per presentation, though that limit is quite arbitrary and could be changed in the future.
I thought or considered this to be a nice-to-have but not mandatory feature, but more people keep asking for that. Always good to have some external feedback – thank you!
You are right, the current feedback mechanics need some love. I'm working on that ;)
Supporting Word, Excel, PPT is also an item on the list, but since we rely on client-only processing, displaying documents consistently across platforms and browsers needs some time and work. But: On it!
Not really, I think there are better and more mature tools for doing that (like appear.in or Skype) out there. frop.io is quite special in that it does not do screensharing at all, but just transmits the content, being super bandwidth-conserving.
Ha, I'd actually love that. Google Slides should be in the realm of possible things, PPTX could get more complicated.
What I suggest you try is to upload a PDF. I've built a moderator mode on the presenting screen, there you can do exactly what you want (just not with a PPT but with a PDF-Presentation).
The reason is that PDF can be rendered very consistently across platforms, this is more problematic with Powerpoint and friends.
https://frop.io is a simple application that allows you to present content (PDF presentations, Images, Text, YouTube videos) on a remote screen without installing any software. It's completely based on web standards (Websockets, JS) and runs in most modern browsers.
Simply start a session by calling frop.io/[yoursessionname]
I posted this two weeks ago. Since then I've completely overhauled the design and built a native tvOS and Fire TV viewer app (both free and publicly available).
Once again, looking forward to your comments, suggestions and criticism.
Hi, thanks for trying frop.io and the great feedback!
I'm a bit reluctant into integrating anything that would require WebRTC (screensharing, video, audio) since I feel there a far superior products out there (like appear.in, TeamViewer or Skype).
Regarding private/secure presentations, End-to-End Encryption is in the making and you can already use any URL you want for the session.. like frop.io/operon.
This is something I've been thinking about quite a lot lately – I considered extending our git-flow a bit to contain review branches (or something comparable). If you'd like to chat a bit about potential solutions for your approach just drop me a line!
Along those lines there's also Deckset [0], which is focused on turning "boring" markdown notes to visually appealing presentations. I've used it once or twice and really like the idea. It's only available for Mac (afaik) though..
Hm, completely different experience here. I've been involved with three rather large Xamarin-Projects in the last year, and we were (team-wide) completely surprised at how much of the code can actually be shared, how our velocity compared to native development and the overall dev experience.
I think the code sharing thing really comes down to how you're using Xamarin – if you keep on writing apps the way you're used to from the original platforms, there's not much to gain. On the other hand adopting the patterns and ideas that influence the .NET sphere (DI/IoC, MVVM..), Code Sharing rates (or PCL vs. Native LoC) can be as high as 80/20.
Xamarin Studio certainly has its own shortcomings, but both Microsoft (Visual Studio for Mac) and Jetbrains (Project Rider) are actively improving or developing alternatives, so I think that pain is going to fade over time.