Home/ Questions/Q 6778477
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T16:16:15+00:00

This is a question about Application design rather than how-to-do specific actions. I am

  • 0

This is a question about Application design rather than how-to-do specific actions.

I am a student taking a beginner’s course in Android Development. I am designing a program which initially requires the person to login, then at a later time they may choose to display a record of all the users that have logged in previous sessions.

As of right now, there are two parts of my app: LoginField Activity which takes the login data from the EditText field, and which is then supposed to write that information to an external .dat file of some kind so that the information will persist across launches, and a LoginHistory Activity which is supposed to display this history in a ListView.

I have toyed with creating a separate class for the ArrayAdapter logic – an ArrayAdapterController class (?) – but was uncertain how to pass information back and forth between it and the two Activities.

so – my questions are these:

  1. since the information needs to persist across sessions what is the
    best method to do this? it does not have to be secure for the moment
    as this is only a student project.
  2. does it make sense to make a separate Controller class to handle the information that will be passed between Views/Activities?

apologies for the general nature of this question – as you can see I am an MVC novice.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You’ve asked a general question, so the best I can do is give you a general answer. You want to use the AbstractAccountAuthenticator class. The documentation there should give you a good jumping off point for you. Furthermore, the SampleSyncAdapter provides a comprehensive (but complex) example of using the authenticator with a full on REST Web Service.

    • 0