Idea Summary
For a new application from scratch if somebody wants to use noSQL style design (say agile schema-less applications) when creating a new Form entering or retrieving data from the local database stored in JSON format it will be needed options across the APEX App Builder interface, as well as, an equivalent JSON Workshop, to address the page design with the related JSON documents in a declarative way instead of using Complex Code, Views and/or REST mappings/invocations.

Use Case
Anytime an APEX user wants to add new data into his database (schema) it could be as a row with columns into a predefined table or as a JSON document in a Collection. No matter if the database object previously exists or not. So creating a new Form will be very easy and zero code.
Then, when retrieving that data from a JSON Collection it could be possible without mapping documents into rows and columns by the user itself. Users should select the Collection/s from they want to create new Dashboards, Forms, Reports, Charts and so on easily without coding at all.

Mapping forms, charts or reports data in a we application directly with a JSON documents is the easiest way to be agile and zero code. Our competitors are doing similar approach as Unqork and MongoDB do.

But, instead using HTTP/S endpoint to REST data services (we could do so by using ORDS) the idea is to create and access native JSON documents (CRUD) organized in Collections directly from APEX design pages, both App Builder and JSON Workshop (new features not present in APEX today).

No matter if APEX can work with Tables and Views and REST Data Services right now we will need native JSON documents too.