Android UI Design Principles -

im writing program going type of scheduler backed database.

we'll call database items, b c , each relies on each other. can't add b without a, , can't add c without b (relies on row ids).

they're simple list of items, want little more b hold, extend, , view c items.

initially figured use context menu reading through android design guidelines, understand while desirable, should not way of navigating items.

so listview a, can add button delete item or allow press on item listview b.

but how recommend design listview b?

after b record added, don't need edit it, have options hold , extend. wouldn't want allow click on list item b go straight listview c bypass options needed b.

im guessing either:

1) ignore guidelines , stick context menus 2) have greyed out edit form b, clickable button go c 3) have greyed out edit form b, include c listview on edit form b

the last 2 options raises own issues, in c relies on b, either need have "save , continue" or "next" button ensure b item saved, or if included c listview on b edit form presumably save bid on c window temporary id of -1 bearing in mind haven't yet saved b , don't know row id is, remembering save/tidyup on returning.

how guys handle this?

is acceptable have "next..." options in android screens? save new database option, utilise save button, or handle "onback" contacts edit screen?