Note that there are some explanatory texts on larger screens.

plurals
  1. USSiddharth
    primarykey
    data
    text
    plurals
    1. COIt isn't, but you need to start somewhere. All products/features start with scenarios in mind. You too can take that approach. Start with a scenario that you hope to support for most of your consumers. Like facebook, or a game with 5 screens and 30 moving characters. Size that up and set your defaults. Then allow configuration both load time and runtime. Can you talk a bit about the scenarios who hope to support ?
      singulars
    2. CODo you know the % distribution between the fastest to the internal storage that is next fasted ? SD card is a not good. May be your can create a LRU to SD card for old objects ? Since a mobile app may be active for not more than 3o mins I guess. Like facebook app. So may be take some scenarios that you want to support to start with. OR the scenario that you want to demonstrate with, and then go from there. That is one way to narrow down the sizing I guess.
      singulars
    3. CO@Robik Its important for you to decide based on "change" expected in future rather than "its a college assignment". If you read through Design Patterns book, they will emphasize on "change". Also they advice that examples are only "guidelines". Remember. If you write "easily changeable" code, which in turn means "change should not cause more testing in areas that were not "changed", or cause defects in areas that did not change. Then you have written good code today. So think "tomorrow's" change before you decide what / where to write code.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload