explanation
-
How a list-with-detail feature is assembled (geodirectory reference architecture)
How mam-geodirectory assembles a list-with-detail feature: one content class drives list/map/calendar surfaces, content sections, tab-bar buttons, forms, and notifications.
-
How Favorites works: what users can save and where it shows up
Favorites is a per-user saved-items list — mam-main renders the screen, while sibling plugins decide what’s favoritable and hold onto the saved data.
-
How geofilters and location work: city picker, radius, content filtering
How a MAM app decides where the user is — GPS, IP, or the city picker — and how the active city plus a search radius filter the content the…
-
The home screen stack: how blocks, sections, and ordering compose a layout
How your app’s Home screen comes together from an ordered list of stacked sections, category rows, and a few pinned blocks — rendered top to bottom, exactly as you built…
-
How a MAM app is structured: tabs, screens, buttons, and content classes
The mental model behind every MAM app: a tab bar and left menu made of buttons, each one backed by a content class that renders a single screen.
Knowledge Base Categories
Need Support?
Can't find the answer you're looking for? Don't worry we're here to help!
