Difference between revisions of "GSOC 2022 - Offline Smoothie"

From Open Food Facts wiki
Jump to navigation Jump to search
(Created page with "Offline Smoothie === Summary === === Description === '''Status''': planning '''People''': ==== Impact (why) ==== ==== Expected outcomes (what) ==== ==== Timeline ===...")
 
(Add from initial proposal)
Line 9: Line 9:
  
 
'''People''':  
 
'''People''':  
 +
* Aman Raj / Open Food Facts user-name: ashaman / Slack: @Aman Raj / Github: AshAman999
 +
* Edouard
 +
* Marvin
 +
* (PM support: Pierre)
  
 
==== Impact (why) ====
 
==== Impact (why) ====
Line 16: Line 20:
  
 
==== Timeline ====
 
==== Timeline ====
 +
 +
* Community Bonding Duration ( May 20 - June 12) :
 +
** Explore the documentation and codebase thoroughly
 +
** Discuss a roadmap with the mentors for a long-lasting solution
 +
** Discuss the general working of how the offline mode is going to work that might include some design patterns as well.
 +
* Week 1 ( June 13 - June 18 ) :
 +
** Discuss with the mentors about the making if using any SQL-based local DB or go with some JSON-like ones.
 +
** Making UI changes to the app so as to highlight the users if they are using the app in the offline mode through snack bars.
 +
** Start plotting the schema of the data to be stored for the scanned/searched items.
 +
* Week 2 ( June 21 - June 26 ) :
 +
** Start plotting the schema of the data to be stored for the scanned/searched items.
 +
** Take into consideration all the attributes to be stored.
 +
** Adding a menu for the users to control/delete the cached items from the stored data, the user might want to get rid of the data so as to make the app lightweight again.
 +
* Week 3-4 ( June 29 - July 10 ) :
 +
** Start the changes to make a lookup of data in the local database.
 +
** Search for the results on the scan and search page in the local database.
 +
** Store the image path into the local DB.
 +
** Use cached Network Image to keep the images stored in the local DB or take inspiration from PR 1600
 +
* Week-5 ( July 12 - July 17) :
 +
** Start storing the scanned product barcodes in the local DB
 +
** Start with mapping a search of the barcodes scan in the scan page to look into the local database and if not found show an appropriate msg through snack bars.
 +
* Week 6 ( July 19 - July 24) :
 +
** Work on leftover over and improve the design aspects to the UI changes
 +
** Clean up the code and maintain the documentation.
 +
** Prepare the work for the first evaluation.
  
 
=== Resources / Contributing ===
 
=== Resources / Contributing ===
* repository:   
+
* repository:  https://github.com/openfoodfacts/smooth-app
* project board:   
+
* project board:  https://github.com/orgs/openfoodfacts/projects/33
* meeting minutes:  
+
* meeting minutes: https://docs.google.com/document/d/1qRkbZwtkASM3_BNhZSkFEekkhrllddR4Tv69bCdquPs/edit#heading=h.crn3zp8c1ahp
  
 
=== Archives ===
 
=== Archives ===
  
 
[[Category:Project]]
 
[[Category:Project]]

Revision as of 10:46, 8 June 2022

Offline Smoothie

Summary

Description

Status: planning

People:

  • Aman Raj / Open Food Facts user-name: ashaman / Slack: @Aman Raj / Github: AshAman999
  • Edouard
  • Marvin
  • (PM support: Pierre)

Impact (why)

Expected outcomes (what)

Timeline

  • Community Bonding Duration ( May 20 - June 12) :
    • Explore the documentation and codebase thoroughly
    • Discuss a roadmap with the mentors for a long-lasting solution
    • Discuss the general working of how the offline mode is going to work that might include some design patterns as well.
  • Week 1 ( June 13 - June 18 ) :
    • Discuss with the mentors about the making if using any SQL-based local DB or go with some JSON-like ones.
    • Making UI changes to the app so as to highlight the users if they are using the app in the offline mode through snack bars.
    • Start plotting the schema of the data to be stored for the scanned/searched items.
  • Week 2 ( June 21 - June 26 ) :
    • Start plotting the schema of the data to be stored for the scanned/searched items.
    • Take into consideration all the attributes to be stored.
    • Adding a menu for the users to control/delete the cached items from the stored data, the user might want to get rid of the data so as to make the app lightweight again.
  • Week 3-4 ( June 29 - July 10 ) :
    • Start the changes to make a lookup of data in the local database.
    • Search for the results on the scan and search page in the local database.
    • Store the image path into the local DB.
    • Use cached Network Image to keep the images stored in the local DB or take inspiration from PR 1600
  • Week-5 ( July 12 - July 17) :
    • Start storing the scanned product barcodes in the local DB
    • Start with mapping a search of the barcodes scan in the scan page to look into the local database and if not found show an appropriate msg through snack bars.
  • Week 6 ( July 19 - July 24) :
    • Work on leftover over and improve the design aspects to the UI changes
    • Clean up the code and maintain the documentation.
    • Prepare the work for the first evaluation.

Resources / Contributing

Archives