Home/ Questions/Q 8851065
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-14T13:03:26+00:00

Is there any disadvantage in transferring values from Activity A to Activity B with

  • 0

Is there any disadvantage in transferring values from Activity A to Activity B with static fields of a third class instead of the ExtraBundle?

In my application, sometimes I have like 15 – 20 values that I need to transfer between two Activitys. In my oppinion, it is more lucid solving this with static fields from a sort of TransferHandler.

At the moment, I have one disadvantage in mind: When a value is not put into the Extras before starting Activity B, I will get an Exception. Solving it with static fields, it it possible that I forget to assign a value, and if that value was assigned before from somewhere else, it might be that a wrong value is used in Activity B. Nonetheless, I think this is a “programmer problem” and not a “program problem”. So are there any further minusses or am I free to choice a way? How’s with the performance of the two variants?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    First of all, if you plan to use static values, you should use your Application class to do this (because Android system assures you that it is a true singleton)

    Thus, you can store your datas in attributes of your custom Application class, and use specific methods to store and get these values.
    This will ensure you can’t “forget” any values.

    Also, with 15-20, I will strongly advice you to make a specialized POJO class to store all this…

    • 0