These are separate screens, but do not necessarily have to be separate activities. Consider architecting this with Fragment s. This would allow you to utilize a single ViewModel bound to the lifecycle of the Activity . Each fragment would be responsible for collecting its own information and handing that into the ViewModel , and then once all the information is submitted, you have it all in one place and ready to go.
Activities are heavy weight components, whereas Fragments are lighter weight. Unless you have a very good, explicit reason to do so, prefer a single activity approach with multiple fragments (or multiple composable screens, if this app is being written from scratch utilizing Jetpack Compose).