Replies: 2 comments
-
Another random thought: We want reusable components that are snapped together into "distributions" (AAO, carls). There are several layers of reusable components, though: low-level UI (list row, button), high-level UI (searchable, grouped, alphabet list view with filters), features (menu) and uh high level feature (bonapp menu?). |
Beta Was this translation helpful? Give feedback.
-
Far-future idea: Interface Builder…
Ideally also a way to publish and share your routes, components, and views. Allow others to subscribe to your published items And maybe new version of applescript, or shortcuts or something. |
Beta Was this translation helpful? Give feedback.
-
I think I do like the model of having AAO/AAA as a "platform" app.
Each "app listed on the store" gets an autogenerated Xcode project, and both xcproj and runtime app are configured by a file in the repo - every module for every college is in the platform, and configured by that json file into the appropriate tab / stack combo
… kinda like what I scribbled a few days ago with the json app config thing. *idea heavily inspired by expo's EAS config thing.
A summary of how different screens should expose filters/search/grouping/sorting options
App config as JSON
Beta Was this translation helpful? Give feedback.
All reactions