3 ms·

Engineer on Origami here: Yeah, it's rewritten from scratch as a native mac app in ObjC++. Happy to answer any question you have :D

ConAntonakos 10y ago
Pardon me if it's a silly question, but was Swift not a viable option for macOS development?
- darknoon 10y ago
  Origami eng here: Swift wasn't ready when we started a couple years ago. We actually used some swift for internal things and it has been a bit of a pain, eg with the macOS SDK update for Xcode 8. Combining ObjC and C++ you get a lot of the benefits of swift like functional programming / static type checking etc, paying a similar price in compile time. It would be hard to achieve the elegance of ComponentKit syntax (https://github.com/facebook/componentkit https://github.com/facebook/componentkit) in swift though. It lets us express the UI in a functional way :D
  - ConAntonakos 10y ago
    Interesting! Thanks for the response!
vvanders 10y ago
Very cool stuff, actual interaction prototyping is an area that's sorely missing in terms of tooling. Is there any sort of export to a production framework(I.E. for integrating into existing iOS/Android apps) or is this purely for prototyping?
theschwa 10y ago
That's fantastic. I can't imagine how much work has gone into this project. I'm excited to see what this does for the adoption of Origami. Are there any personal stories from the process you're able to share?
mortenjorck 10y ago
This is, quite simply, incredible. My team was looking for something to replace Pixate even before Google announced they were shutting it down, and just having watched the first tutorial, it feels like we're done looking. I feel silly jumping to a nitpick at this point, but I see one obstacle for my team: There doesn't seem to be a way to enter custom screen sizes, apart from eyeballing it with the resizable window setting (we're designing for a custom-built Android device). That's probably not enough to stop us from using it, but it would be great to have the option.
- natosaichek 10y ago
  custom devices? Elsewhere in the thread this was posted... might be what you're looking for. http://origami.design/documentation/workflow/CustomDevices.html http://origami.design/documentation/workflow/CustomDevices.h...
redindian75 10y ago
I am sure you would have been asked this 100s of times - Is there a way to EXPORT it to actual code (Swift/JS for Web) etc? Or is just used for only previz? That would mean someone can prototype an interaction which is impossible to code Finally, what is the goal? Is it just to be a prototyping tool or Will it evolve into a App maker itself? Or at least able to export code. Thanks for giving it away free!

ConAntonakos 10y ago

Pardon me if it's a silly question, but was Swift not a viable option for macOS development?

darknoon 10y ago
Origami eng here: Swift wasn't ready when we started a couple years ago. We actually used some swift for internal things and it has been a bit of a pain, eg with the macOS SDK update for Xcode 8. Combining ObjC and C++ you get a lot of the benefits of swift like functional programming / static type checking etc, paying a similar price in compile time. It would be hard to achieve the elegance of ComponentKit syntax (https://github.com/facebook/componentkit https://github.com/facebook/componentkit) in swift though. It lets us express the UI in a functional way :D
- ConAntonakos 10y ago
  Interesting! Thanks for the response!

vvanders 10y ago

Very cool stuff, actual interaction prototyping is an area that's sorely missing in terms of tooling. Is there any sort of export to a production framework(I.E. for integrating into existing iOS/Android apps) or is this purely for prototyping?

theschwa 10y ago

That's fantastic. I can't imagine how much work has gone into this project. I'm excited to see what this does for the adoption of Origami. Are there any personal stories from the process you're able to share?

mortenjorck 10y ago

This is, quite simply, incredible. My team was looking for something to replace Pixate even before Google announced they were shutting it down, and just having watched the first tutorial, it feels like we're done looking. I feel silly jumping to a nitpick at this point, but I see one obstacle for my team: There doesn't seem to be a way to enter custom screen sizes, apart from eyeballing it with the resizable window setting (we're designing for a custom-built Android device). That's probably not enough to stop us from using it, but it would be great to have the option.

natosaichek 10y ago
custom devices? Elsewhere in the thread this was posted... might be what you're looking for. http://origami.design/documentation/workflow/CustomDevices.html http://origami.design/documentation/workflow/CustomDevices.h...

redindian75 10y ago

I am sure you would have been asked this 100s of times - Is there a way to EXPORT it to actual code (Swift/JS for Web) etc? Or is just used for only previz? That would mean someone can prototype an interaction which is impossible to code Finally, what is the goal? Is it just to be a prototyping tool or Will it evolve into a App maker itself? Or at least able to export code. Thanks for giving it away free!