I have the following class : 

```
public class EnteredValues {

private HashMap<String, String> mEnteredValues;

public boolean change = false;
public boolean submit = false;
private static final EnteredValues instance = new EnteredValues();

// Singleton
private EnteredValues() {
    mEnteredValues = new HashMap<String, String>();
}

public static EnteredValues getInstance() {
    return instance;
}

public void addValue(String id, String value) {

    if (mEnteredValues.put(id, value) != null) {
        // A change has happened
        change = true;
    }
}

public String getValueForIdentifier(String identifier) {
    return mEnteredValues.get(identifier);
}

public HashMap<String, String> getEnteredValues() {
    return mEnteredValues;
}

public void clean() {
    mEnteredValues.clear();
    change = false;
    submit = false;
}
}

```

This class is used to manage the values that a user has already entered, and the class should be accessible to all classes across the application.  

When the activity changes I 'reset' the singleton by calling the clear method. 

I chose the singleton pattern without really considering the option of a static class.  

But now I was wondering if I shouldn't just use a static class.. 

What is the common way to handle a class that just manages values? 
Is a static class faster as a singleton? 

thx