Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Codea is AMAZING

I've been away a while learning how to use Xamarin.Forms.

After struggling with Visual Studio and the constant cycle of update breaks code, finally get code working again, new update breaks code again, I realized something.

Codea is AMAZING.

When I'm using Xcode, I swear the time spent wrestling with the IDE vs. actual coding is around 50/50.

When I'm using Visual Studio, it's also around 50/50.

With Codea the time spent coding is a whopping 99.5% or even more.

You guys don't get half the credit you deserve. A practically invisible IDE that just lets you code and gets out of the way--and can make FULLY FUNCTIONAL apps (that's right I'm screaming it)--this thing is practically holy.



  • SimeonSimeon Admin Mod
    Posts: 4,829

    Thank you @UberGoober! That's really great to hear

    Yeah sometimes I go to Codea to work on new projects now instead of Xcode because the iteration time is so much faster for graphics-related stuff (i.e., time between pressing "run" and seeing the result)

  • Posts: 557

    I swear, write a UIKit bridge and you'll rule the world.

  • SimeonSimeon Admin Mod
    Posts: 4,829

    I'm thinking about it, more and more I want native shells around Codea "canvases"

  • Posts: 557

    My guess is that the problem is that once you start fiddling with UIKit, you get mired in ViewController shenanigans and AutoLayout and then boom you're back to struggling with the IDE all the time.

    Unless you can figure some genius way to Codea-fy UIKit.

  • SimeonSimeon Admin Mod
    Posts: 4,829

    I love using autolayout programatically with

    I think any UIKit that comes to Codea would be a more flexible shell for making tools rather than full-blown UIKit. More like how parameters works but more flexible and better looking.

  • edited February 16 Posts: 237

    @Simeon Since this discussion has already been made, I might as well give my input. I tried Corona and Unity because I wanted an engine that was cross-platform, and although they are powerful and have great APIs, I just always thought Codea was far more user-friendly and simple to use. The games are so much easier to make as well. In Unity, you have to drag and drop all the game objects, which is nice for other people, but the thing I like about Codea is that you get to draw in game objects from the code. Every time I try to use a different SDK, I always end up back to Codea. It is way underrated, TLL has to give themselves a pat on the back, great job!

  • SimeonSimeon Admin Mod
    Posts: 4,829

    Thanks @CamelCoder!

  • Posts: 60

    Agreed, Codea's API is straightforward, it is easy to use and extremely user-friendly. It usually takes me a long time to get used to a framework or an engine, this has never been the case for Codea. And it is fun to use as well :)
    @Simeon It would be amazing if your version of UIKit could find its way into Codea!

  • pacpac
    Posts: 150

    Just to say I don’t think you know how to use Visual Studio if it 50/50 but from my time it was about 75/50 but codea takes the cake with the 3d it does not make you write thousands of lines of code like direct x made me do. And it is simple to use the objects unlike unity. They need to try to make a pc version. I would get it.

  • Posts: 557
    @pac I’m honestly confused and my feelings are hurt that you felt it so important to put me down so you could brag about a 75/25 productivity rate.

    I’m glad your experience is better I guess.
Sign In or Register to comment.