2 added 3 characters in body
source | link

Well....neither. The Native mobile app uses the module Mage_XmlConnect to get the needed data. It makes calls to the controllers in this module.
  

A bit ofoff topic:
(almost) all the controllers inherit Mage_XmlConnect_Controller_Action so (almost) all calls pass through this action Mage_XmlConnect_Controller_Action::preDispatch().
Most of the actions just load the layout and display it, so if you want to know how some data is rendered look in the blocks of this module.

Well....neither. The Native mobile app uses the module Mage_XmlConnect to get the needed data. It makes calls to the controllers in this module.
 A bit of topic:
(almost) all the controllers inherit Mage_XmlConnect_Controller_Action so (almost) all calls pass through this action Mage_XmlConnect_Controller_Action::preDispatch().
Most of the actions just load the layout and display it, so if you want to know how some data is rendered look in the blocks of this module.

Well....neither. The Native mobile app uses the module Mage_XmlConnect to get the needed data. It makes calls to the controllers in this module. 

A bit off topic:
(almost) all the controllers inherit Mage_XmlConnect_Controller_Action so (almost) all calls pass through this action Mage_XmlConnect_Controller_Action::preDispatch().
Most of the actions just load the layout and display it, so if you want to know how some data is rendered look in the blocks of this module.

1
source | link

Well....neither. The Native mobile app uses the module Mage_XmlConnect to get the needed data. It makes calls to the controllers in this module.
A bit of topic:
(almost) all the controllers inherit Mage_XmlConnect_Controller_Action so (almost) all calls pass through this action Mage_XmlConnect_Controller_Action::preDispatch().
Most of the actions just load the layout and display it, so if you want to know how some data is rendered look in the blocks of this module.