When creating the onboarding engine, we are forced to use an ArrayList to hold ou onboarding pages. This might be a design issue as using a List as constructor parameter would be better than an ArrayList.
For my case, i wanted to take advantage of LinkedList to keep the order of screen. This order in mind would help to better manipulated the screens in bounds to implement further logic
When creating the onboarding engine, we are forced to use an ArrayList to hold ou onboarding pages. This might be a design issue as using a List as constructor parameter would be better than an ArrayList.
For my case, i wanted to take advantage of LinkedList to keep the order of screen. This order in mind would help to better manipulated the screens in bounds to implement further logic