Backend tab showing Easy vs Advanced edition and API key
Easy vs Advanced

Appifio Creator · Lesson T06 · Glossary

Easy vs Advanced Storage
- pick correctly from the start

Two Backend editions ship different client scripts and capabilities. Switching mid-project can leave an app expecting Advanced APIs while the link is still on Easy.

Goals: Read Easy/Advanced UI labels correctly; understand backend_version; know quotas; when Advanced is required (CMS, shards, MCP).

Time: 11-13 minutes · Before: F01, T02 · Next: T07

UI: Backend tab · Backend version · Easy version · Advanced version · Your backend API key · Database rows · API requests this month

1. Choice diagram

Account plan AND link config both Advanced?
→ YES → backend_version = 'advanced'
→ loads the Aura appifio_client (appendData, shards, CMS auth…)
→ NO → 'easy' → simpler client
Backend tab: pick the version → save in the Backend area (Save for that tab)
Then: toolbar Save changes if you need the new client on the live site

2. Easy vs Advanced

AspectEasyAdvanced (Aura)
UI descriptionSimple & fast for basic appsFull Aura Storage
Indexed + shardsLimited / don’t expect the full setappendData · readList · updateData (T03)
Aura CMSUsually not enough__cms_manifest__ · roles (T05/T07)
MCP sandboxMay be limitedNeeds Advanced + API key (T12)
Use casesBiolink, one-form landingShop, CMS blog, multi-role admin
Prompt & Skills: Enable exactly one matching template - Appifio Easy Storage - Complete AI Guide or Appifio Aura Storage (Advanced) - Complete AI Guide. Do not enable Easy + Aura together. CMS = Aura only (+ Appifio Aura CMS + Storage - Complete AI Guide when using CMS).

3. Steps in the UI

  1. Tab dropdown → Backend.
  2. Read About Appifio backend and Your backend API key - use Copy.
  3. Backend version → choose Easy version or Advanced version (match Easy plan / Advanced plan).
  4. Save the version in the Backend tab (Backend-area save - not the Routes tab Save).
  5. Check quotas: Database rows / API requests this month.
  6. Open View backend database content if you need to inspect data after a form test.
  7. Toolbar → Save changes so the new client script reaches live.

4. Platform comparisons · Limits

  • Firebase Spark vs Blaze: basic vs full backend.
  • Shopify Lite vs full store: a selling channel needs Advanced-like capacity.

Quota: Database rows = total indexed rows; API requests = read/write calls this month. Hitting the limit → API errors - clear spare data or upgrade the plan.

Security: API key is app-scoped - 32-character hex; don’t paste into public Git; the MCP tab needs the key first (no_api_key).

5. Incidents · Tips

IncidentFix
Missing / invalid API keyCreate a key in account settings; 32-character hex
CMS/MCP needs Advanced but the link is EasyUpgrade plan + switch Advanced version + Save
appendData undefined on the pageStill on Easy client - switch Advanced + Save changes
Out of rows/requests quotaClear spare data (careful - T04); reduce API polling

Two Save layers: (1) Save in the Backend tab = change backend_version + client inject; (2) toolbar Save changes = publish HTML to the live site. Skip (2) → visitors still get the old Easy script even if Backend already shows Advanced.

6. Decision examples by app type

App typeRecommendWhy
One-page biolinkEasyFew APIs, no CMS
Blog + /cmsAdvancedIndexed, roles, manifest
Lead form + admin listAdvancedappendData + readList (T03)
IDE MCP sandbox editsAdvanced + API keyT12 · no_api_key if missing

7. Checklist

  1. Are account plan and Backend version both Advanced when you need CMS?
  2. Did you Save the Backend tab, then Save changes in Creator?
  3. Can you read rows/requests quota on the Backend tab?

Next: T07 - Roles user / admin / superadmin

Appifio Creator · User guide · T06