Creo is a next generation Mac tool which aims to combine the Design and Development process into a single easy to use application. Thanks to our CreoKIT we always use NATIVE components and classes, no simulated or web based code is used.
This is a really nice app that came out of private beta today. It merges design and development into a single process so that you can get a prototype built quickly.
Tried it yesterday, I really miss the autocompletion but I'm sure it's coming in a future release. Can you give us any idea regarding what the pricing will be?
Ton of potential. I've seen a few apps that tried and fell short of the mark here, but it's the holy grail of design in my opinion to get an app that would allow me to develop to a point where a dev could do all of the backend work.
Looking forward to trying this out!
It's looking good, but frankly I don't have time to give it a serious test.
I'm hoping to see some independent reviews summing up the pros and cons to figure if I should dive deeper into this
@mmariansky it's a beta released with some undocumented features...personally I think right now you can use it to create mockups of apps that you might want to build for fun an pleasure, as time passes within the next couple of months and the unveiling of the other features it might become a really great way to have non-developers but tech-savvy people develop apps that could easily end up on the app-store.
I'm also writing a longer write-up on my experience so far..
Are there any limitations? Does it have the capability to build all the different types of products that you can build with traditional programming languages.
@jacksitt yes, most common operations will be visual in order to speed up development but everything can also be created/manipulated using a programming language.
@sqlabs How do you see this being used across design / development teams on an ongoing basis? As a developer, I wouldn't be thrilled about taking over generated code and then having to make sure my code changes don't break the tool. I also would hate it if I kept getting new generated code being introduced into the codebase that I'm trying to maintain and having to constantly go back to refactor, add unit tests, etc. What process are you recommending that cross-disciplinary teams use when using your tool?
Dialo