Using Parcelable
doesn't seem to be a right approach for your case, from architecture point of view. Most likely such restaurant data should be stored in SQLite DB, in tables. Data structures (data model) is a core for such apps, you probably need to design DB scheme first of all, then you'll be using Activities/Views to display that data, enter new data, and so on.
DB will keep entities in tables (data model), and when you need to operate with an entity (ie a restaurant menu) you just send id of that entity, in this particular case via Intent, most likely it will be a single integer, no need to parcel every attribute of the entity - in the Activity being launched you get the id from Intent's extra, and using that id the activity retrieves the entity's attributes from SQLite DB and puts values to appropriate views, this is an ordinary routine.
When you need to show many records, you'll probably use an Adapter
, its purpose is to map data from source table into views, particularly how to render a record from DB into a view (probably with subviews) which will represent that record. Google for tutorials about adapters, they are used almost always when there are tables on screen.
EDITED - you need to look at Android's ListView
control, read guide here: http://www.vogella.com/tutorials/AndroidListView/article.html
Tables are used in iOS, my mistake.