Currently, I have developed a widget that relies on time sensitive information and creates a timeline divided into events that occur on a minute-basis. Because I am loading so many events into the timeline, I kept the length of the timeline small to prevent the timeline from storing thousands of events rather than less than a hundred or so. Then, at the end of that timeline, I request a new timeline with the next set of events.
However, I am now noticing that when the end of the timeline is reached, the device tends not to immediately request the new timeline. For that reason, I am considering loading the entire day's events into one timeline.
That brings me to my question - Is loading the entire day's timeline okay in this situation and/or are there any potential risks of the timeline refusing to accept so many events?
However, I am now noticing that when the end of the timeline is reached, the device tends not to immediately request the new timeline. For that reason, I am considering loading the entire day's events into one timeline.
That brings me to my question - Is loading the entire day's timeline okay in this situation and/or are there any potential risks of the timeline refusing to accept so many events?
After speaking with an engineer from Apple during the WidgetKit lab, he explained that my current implementation is valid and that it may in fact be more efficient to load one large timeline rather than relying on updating the timeline throughout the day. However, he did note that Apple has not tested the implementation of large quantities of entries in a timeline and that I should experiment with the capacity of the timeline.