Is auto-binding available in the new mobile beta or no?
You can change the value of a thing by using “An input’s value is changed” as a trigger in a new workflow.
I would do it as a form with a single update or save button. On a recent test with a form with 8 fields using the “An input’s value is changed” the app kept throwing up an error about too many workflows running.
Unfortunately a save button doesn’t work for this app–I’m building an app for tracking tasks and notes and so people have to be able to just type what they need to without having to hit save all the time. I may have to stick with the original method for mobile which would basically be building pages with the web editor and making it responsive to mobile. I was just really excited about the new app builder because my original method for creating a wrapper for my app in xcode was kind of janky and inefficient and it looks like they have made it way easier since then, plus you get some featured on the app builder that you don’t get on the web building like being able to slide elements.
I would definitely stick with the native mobile. I have an app published on internal testing and three in build. Sure, they’re not the fastest apps in the world, but they do work surprisingly well. In my case, there are 8 user profile fields with will always have short strings as content. Meaning people who typed fast really motored through the form. But I would suspect that in your use case, data entry may be slower, and there are only a couple of fields. This would have much less chance of causing the same problems.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.