I was going to create this thread asking how to create an iOSTable with inconsistent row heights.
Actually I have just found the solution which is very simple but took some time.
Setting the Table.EstimatedRowHeight anywhere else than just before adding cells in the Table.Open event will fail to display the correct RowHeights or will fail completely with an ObjectC Error.
your example above doesn’t look like a candiadate for a Table/Listbox (unless there is more than is visible)… but that an opinion 
You need to get access to heightForRowAtIndexPath delegate (via a declare most likely)
I quite agree that the amount of controls displayed in the example could be set up directly in an iOSView or ScrollableView for iPhone 4s that has a smaller screen.
But later on in the project a dozen more rows will be added.
The advantage of using a Table here, is that the DatePicker visibility is toggled by tapping the first row. The DatePicker toggle produces a smooth animation which would require declares.