Data model in mobile apps: Revision history

7 September 2025

• curprev 04:5504:55, 7 September 2025 Jzambor talk contribs 16,093 bytes −4 →Managing fields
• curprev 04:5304:53, 7 September 2025 Jzambor talk contribs 16,097 bytes +43 →Managing fields

20 February 2025

• curprev 12:0512:05, 20 February 2025 Jzambor talk contribs 16,054 bytes +275 →Which fields are used?

12 September 2024

• curprev 09:1709:17, 12 September 2024 Jzambor talk contribs 15,779 bytes +175 →Which fields are used?
• curprev 08:5508:55, 12 September 2024 Jzambor talk contribs 15,604 bytes +10 →Which fields are used?
• curprev 08:4808:48, 12 September 2024 Jzambor talk contribs 15,594 bytes +227 →Which fields are used?

16 May 2024

• curprev 06:5506:55, 16 May 2024 Jzambor talk contribs 15,367 bytes +106 →Which fields are used?

15 May 2024

• curprev 11:0511:05, 15 May 2024 Jzambor talk contribs 15,261 bytes +17 →Managing fields
• curprev 11:0411:04, 15 May 2024 Jzambor talk contribs 15,244 bytes +15,244 Created page with "When designing an app project in Woodford, one of the first tasks is to decide which tables and columns should be available on the mobile device. Server databases of your CRM or ERP system often contain enormous amounts of data. However, mobile projects tailored for a particular group of users usually require only a minimal subset of the data. == Why reduce mobile data? == ;Reduce user error : Users can be overwhelmed if their mobile app is packed with data, fe..."