This is exactly what we did with Creo a couple of years ago: design, preview and development in a single tool. We rewritten UIKit from scratch in order to be able to preview iOS code on MacOS. Looks like we did it right.
https://creolabs.com
Hi,
we completely rewrite the UIKit framework from the ground up. We started from the abandoned Chameleon Project (http://chameleonproject.org) several years ago and we added tons of classes and improvements in order to be in sync with the latest iOS versions from Apple.
We are able to execute most of the native iOS code directly on Mac, from example this project works without a single code change on MacOS: https://github.com/chrismiles/CMUnistrokeGestureRecognizer (so we have UIView, UIViewController, UIGestureRecognizer, UITouch, UIBezierPath and much much more).
We also didn't block any customisations (like the custom collection view layouts). We simply need more time in order to correctly expose all the functionalities from a graphical user interface and in a coherent way for all the users.
Creo is not just a drag and drop UI/App builder. You can easily create UI with drag and drop but you are always allowed to write more complex interaction or code using a programming language.
@sama We were interviewed last year but we were not selected. We then followed all your advices and we invested all our time developing and finalizing the product.
We'll launch our first beta version within a month and we are receiving a tremendous amount of interest. However we can't really yet prove a traction. What should we prove (or what should we have done) in order to try to apply again?
BTW the video you discovered on vimeo was just a quick demo we did for internal usage. It wasn't meant to be showed to public and it demonstrates a very old version.
There are a lot of critics here and I really appreciate the "brutal" honestly in your answers, we'll do our best to treasured your advices.
I really think that there are some misunderstanding about the real intent of the article and since the website is just a landing page, the best answer is just to release an impressive product as soon as possible.
As I already wrote, a public beta version is expected by mid April.
Guys,
I just wanted to describe my experience, I really didn't want to criticize YC or the interview process. YC was our first pitch and we were surely not prepared enough. As I clearly wrote in my post I started with the wrong assumption that our product and our technology could make the difference. I was wrong.
Website is more a landing page that a real site. Product is not yet released to the general public. We plan to launch a public beta and a brand new website with more useful information in about a month.
I wanted to create a programming language with the following properties:
- Class-based
- A JS/Swift/Kotlin like syntax
- Bytecode generation
- A clear distinction between front-end and back-end so at runtime, we need only the VM related code to execute the bytecode
- Lightweight and easy embeddable
- Extensible/customizable via bridge API(s) exposed via delegation (no need to hack/modify the code)