When you figure out you missed something in your app, do you find it easier to redo the whole thing? Some of my pages have MANY components visibility and such, that I like, but feel if I rework my app, i may have to do it from scratch. Any thoughts on that process or things you have done in a similar situation? Can you copy all the components from 1 and use them again on another page?
My problem is I created an app that shows every time I have met a certain person under many a circumstances so I know when i met them and why. But, now, I want to be able to have a main details page for each person and then add to that every time I have met them, but it seems it has to be on separate sheets. I want to be able to create someone and add to them but since I already have them in my sheet, some with multiple instances of meetups, I now need to create a āmain pageā for each person with general notes and details.
I hope that made sense. It does in my mind but articulation may beā¦meh.
Probably you can duplicate the tab and make changes where you need, while keeping the old tab as a fallback option just in case.
Without knowing much about how you currently set up things, just talking about the data structure, I believe you just need one sheet for all āpeople you have metā and one other sheet for āmeeting instancesā related to each person.
If you want to add a new person, add it to the first sheet, else you add a meeting instance to the second sheet and relate that back. Would it work?
A bummer part of rebuilding/reworking an app is that you canāt have two GDEās open at the same time, so if you make a fresh one, or a duplicate of your app you canāt compare them side-by-side on the back end. Plus no copying/pasting of components across screens/tabs/apps etc.
yeah, that is annoying.
What I normally do to work around that is make a duplicate of the app, and then have that open in another window to use as a comparison.
And at other times Iāve taken screenshots of all component and column configurations
I have recently had to rebuild an app, and building it from scratch turned out to be the best option.
You can go back to the database and do some serious tinkering, using any new skills you have developed. This doesnāt just help the back end, as it usually allows some front end tweaks that would have been difficult/cumbersome to implement.
It is also far faster than the first build, especially if you are copying certain parts and have the old app alongside.
Iāve found there are some serious traps that you canāt get out of, and unfortunately, starting from scratch seems to be the best option. The road to learning the best practices for your particular application has some big potholes - the kind that leave you with a flat tire LOL.
Iām taking the hit on my app (telemedicine) to redo using Tabs.
I hide the tab menu with css / leaving the hamburger and back (in some places).
I have flows in my app driven by increments (click a button, add 1, changes visibility). That works really nicelyā¦
But things can get complex fast, especially if you need to drive things through rel inline lists and āview detailsā. Very hard to manage and update (Iāve got complex live data with lots of columns in a row so itās annoying to recreate).
I now do many actions as ānavigate to tabā, keeping functionality and screen logic in specific tabs. Users can get to these tabs directly as the tab menu isnāt there
I think so. I have been working on it and then adding a sheet when I couldnāt relate something for a reason and now it seem I have so many columns I donāt know where anything goes anymore. So trying not to rethink recreating an app with all the data I haveā¦
Right?! I have seemed to have ācolumnedā myself into problems I canāt get out of. As I am still learning and have an awesome workable app for meā¦ but want to update it so there are user specific fields and then I am trying to navigate how to go pro and sell the app and then update things on an admin side for certain itemsā¦
