The next Kintone update is 10th May 2019. The release also includes the following updates.

• The 'When a custom view for mobile is displayed' timing will be added to the Record List Onload event for mobile
  • Relevant API:
    • Record List Onload event (mobile) (mobile.app.record.index.show)
  • Spec change details:
    • On mobile, when the record list view type is set to Custom and one of the following operations occurs, the Record List Onload event will be triggered
      • The user navigates to the next or previous page
      • The category is changed
      • The sorting of the records in the view is changed
• New properties will be added to the Event Object of the mobile Record List Onload event
  • Relevant API:
    • Record List Onload event (mobile) (mobile.app.record.index.show)
  • Spec change details:
    • The following properties will be added to the Event Object of the mobile Record List Onload event, when the view type is set to Custom:
      • viewType (this value will always be 'custom')
      • records
      • offset
      • size

• The API documents will be updated to state that the Record List Onload event for desktop will be triggered after the category is changed.
  • Relevant APIs:
    • Record List Onload event (desktop) (app.record.index.show)
  • Update details:
    • After the category has been changed, the Record List Onload event will be triggered. This is applicable to the desktop version of the event. This was how it always used to work, but it was not officially documented on this website.
• The API documents will be updated to state that the mobile Record List Onload event will be triggered after the following timings.
  • Relevant APIs:
    • Record List Onload event (mobile) (mobile.app.record.index.show)
  • Update details:
    • After either of the following operations occurs within a mobile view with a view type of List, the mobile Record List Onload event will be triggered.
      • The category has been changed
      • The sorting of the records in the view has changed
    • This is applicable to the mobile version of the event. This was how it always used to work, but it was not officially documented on this website.