Composer 2

There's a steep learning curve, but it's WAY worth it. To set yourself up for success, be sure that you've figured out what you want your core design elements to look like. I was discouraged at first when I dragged in some elements and it looked like crap. But then I put in my brand colors, decided what size I wanted my buttons, etc. Now, things look good by default and just need to have the spacing adjusted. Putting in the effort to make my components look good up front made it easier to be excited about the process (=put in more development hours).

Also, you MUST use the forums at forums.appgyver.com. It's such a sophisticated tool that you simply won't be able to figure out every nuance on your own. When you have a question, first search the forums to see if someone else already came up with an answer. If not, then post the question. The project manager for Composer is the primary responder, and he or one of the team members usually respond within 24 hours. (Don't hesitate to post a reply on a thread if you didn't get a reply--squeaky wheel gets the grease.)

My project is so complex that even with AppGyver, I have paid a developer $20K to build out the back end and insert some custom code into AppGyver to handle the data accordingly. Without AppGyver, this project would have taken hundreds of thousands of dollars and simply not been possible for me. But because I could do the majority of the work myself--and then iterate quickly--I actually have a shot at success.

Very Frustrating

There is an initial learning curv e, but if you go in understanding that, you can start small and then use their forum, tutorials and documentation to quickly build a base of knowledge that enables you to build a real mobile app.

If you think AppGyver is missing a feature or capability, take a moment to check out their forum, docs, and youtube channel. Almost everytime I have found what I need. If you don't they have the ability to submit new feature requests and vote on them.