Good to emphasize the "no limits" message but I'm trying to sort out whether adopting Triggr would make that easier or harder
... I don't really have screenshots yet, just idea-scribbles. So I'll describe the app in more detail (probably too much, sorry) and maybe that will suffice...
The app idea is a logbook of templated Activities, where the Activities are specific to each user (my Activities might include 'jogging' and yours maybe 'parasailing' or 'visiting grandma'), for high-speed and moderate-consistency logging of recurring activities (going jogging, etc). There are two use cases to consider:
Making an entry
User has a set of buttons on the app main page, one button for each entry type ('jog', 'visit', whatever). Tap on button, get an input form with a set of controls (text, photo, etc), operate the controls and save the entry. Key issue is customization to the User's needs: every Activity can have a different set of controls from other Activities ('jog' is different fields from 'visit grandma'), and each User can have a different set of controls even for a same-named Activity (my 'jog' Activity is different from your 'jog')
So this leaves the question, how does the User define the Activity/fields...
Adding an entry type.
The User select an Add Entry Type button or menu entry and is presented with a
form allowing entry of some metadata (e.g., a title, a default location, etc) and a set of a few Templates. A Template is a set of possible fields in a layout; the User selects a Template, and then enables/disables individual fields in the template. This combination of Activity metadata and modified Template becomes the new Activity, and a button with the name of this Activity is added to the app splash screen.
Would this be an easy app to build and iterate using Triggr, or would I be pushing the tool too hard?