Last active last year
I think you're absolutely right @marco - the world does need something better, but in all honesty I can't remember any dev I've worked with actually saying "I wish there was something better than 'x' ". We all encounter frustrations with languages and frameworks but find ways to work around them. The first questions usually asked when assessing a new product are "can I re-use skills I already have with this?" and "how do I extend it if I wanted to do....".
No matter how much better any framework thinks it is (and let's face it every new framework believes it's better than the last) will have issues that need to be worked around, and that task is made all the easier if it's a known quantity, backed up by a global userbase and support from the likes of StackOverflow and other large developer communities.
Let's hope Creo achieves the traction it needs to get to that stage rather being passed over by people in favour of languages backed by FaceBook (React), Google (Angular) and Microsoft (TypeScript). That's one hell of a mountain for any team to climb. Personally I'd have borrowed a helicopter from one of those guys and given myself a fighting chance.
Very best of luck - you've made an exceptional development tool, I just wish it was based on one of the huge open ecosystems that everyone knew and could leverage, out-of-the-box. Then you'd have a game-changer.
Pretty sure I remember this dialog when it said 'available in the next beta'. :-(
afaict the website docs and those accessed from within b5 (same?) haven't changed.
Is there an ETA?
To my mind the single most impressive thing about Creo (so far) is the design experience. The "Everything is an object" concept is fantastic, the data-binding tool for wiring-up API data is certainly one of the best out there and....Creo even supports Sketch importing. What's not to love?
Well, hopefully nothing - but I have my concerns.
The 'rapid app development' and 'low code' space is already crowded and getting more so each day. I'm not talking about the hundreds of 'get your app running in 5 minutes with our simple RSS building blocks' - I mean NativeScript, Ionic, Appery, Screendy, Appgyver, Appcelerator...all offer highly visual tools for doing what Creo hopes to achieve. This week another one was announced in the guise of ReactStudio and there are bound to be many others I've missed.
These tools can be run on Mac, Windows & Linux. Creo is just Mac (which is perfectly fine by me, but....) They are also based on existing web technologies (JS, TS, React, Angular, nodeJS...) which from a development point of view means using existing, transferrable skills. Also they can draw upon hundreds of thousands (!) of existing free & commercial modules via npm, Github, PhoneGap....to easily add app functionality without having to develop from scratch. I have yet to read an answer to my other post asking about any module support in Creo.
Genuinely excited about the upcoming b5 release but again, in my opinion, Creo needs to embrace existing open technologies in order to succeed, not try re-inventing wheels which already spin perfectly well for 99% of the planet. We'll see.
What I'm hoping for and waiting to see with b5, is thst Creo doesn't integrate anything like push - but instead is *open* to all the existing providers via the providers own SDKs.
There must be 20+ different push providers atm, many free even at scale.
Hi @marco It's a little disappointing to hear there's no ETA for Android.
Whenever I read 'we have no ETA' it gives me the impression that something has been kicked into the long grass in the hope people will forget about it. Can you at least indicate where Android support is on your roadmap and what major things are ahead of it please? Or perhaps clarify whether 'no ETA' means months, years...
I've been holding out for Creo ahead of starting two projects, to give the app a decent real-world test, but if it's only going to be able to deliver iOS apps for the foreseeable future, that isn't great news.
I appreciate we've previously touched on the potential of Creo to include existing 3rd party SDKs, case of FireBase, OneSignal, all sorts of backed providers etc.
But what of 3rd party functional modules?
I'm involved with a mobile project which simply wouldn't exist without being able to call upon external modules which the dev platform doesn't ship with. Ionic, NativeScript, Appery and of course Phonegap can leverage Cordova plugins, Titanium can use the node based ecosystem just as NativeScript does.
Will Creo be able to call upon existing functional modules from the likes of Cordova / Phonegap / npm etc?
The mobile development marketplace is so fragmented, with the greatest respect I can't see developers having time to port their modules to Creo very quickly. Surely a fantastic team who can reverse-engineer iOS so it runs on a desktop Mac can support Phonegap or npm modules? :-)
What a huge unique-selling-point that would be for Creo.