Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Highlights

  • Franchisee will be able to configure a second time slot for the restaurant break time ( visible on the guest application: web, app)

  • Localize translation sync timeline - has been improved and now, the change performed will be reflected to production much faster (the previous timeline was 2 weeks vs the current timeline which is twice per day)

  • Capacitor 5 Update Android performance impact - Our engineering team is continuously working on optimizing the performance of the app by reducing the time that it takes to open and load on/from an Android device. This work started at the end of the month of October and will continue in the following period

Applications

Guest Application (Web/iOS/Android)

  • Feature "Break time" - 2 time slot for delivery service - possibility to create a “breaking time” period for delivery service on the restaurant openings. It will provide the correct time of service to the user

  • Capacitor 5 update - the framework used by our applications to access native device features.

    • As we have notified you on the release note from October 4th, our teams continued working on optimizing the performance of our app by reducing the time that it takes to open and load from an Android device. So far, based on the preliminary results of one of our largest markets, the delay between opening the app and the point at which the JavaScript code starts running has been reduced by 17% arriving at 2.57 seconds (javascript_start metric), while the time required by the app to show the content from the moment on which the end-user/customer opened (the app) has been reduced by 11% arriving at 4.79 seconds (react_start metric). We will keep updating the release notes with the results and findings as we come across them.

Platform

Translation

  • Translation improvements - string updates are synchronized twice per day, at 10:00 and 22:00 UTC respectively. After the updates have been published, an application restart or website refresh is required to get the up-to-date content. String updates are only propagated to the latest application version

  • No labels