Files to check:
- LDPagination+Ext.swift
- LDItemViewFlip+Ext.swift
- FollowerListVC: getFollowers()
- UserInfoVC: getUserInfo()
Branches
- gettingStarted: Contains initial integration/testing of LaunchDarkly platform.
- LaunchDarklyGHFollowers: Production app that uses the Production mobile key.
- LaunchDarklyGHFollowersTest: Test app that uses the Test mobile key.
I started with a simple test project based off the Hello LaunchDarkly for iOS project.
I decided on using conditional functions for changing the labels and then went with the use of a ternary operator shown in the checkFeaturevalue() function to update all of the labels at once once I activated the feature flag.
After, I began thinking through what the best way to utilize and integrate the platform would be. One of the main ideas I wanted to tackle was to see how we accomodate for UI changes to see the bugs/errors that may occur when moving them around. For this reason, I decided it would be best if I used a course project I have been recently working on in order to test the LaunchDarkly SDK in a more full featured app. I felt as though this would allow me to focus more on the integration of the platform and try to find solid solutions to abstract some of the logic required for the LaunchDarkly services away from the view controllers.
I felt as though the best way to achieve this was to create extensions on the view controllers and classes that needed feature flagging.
I started with changing the pagination values for the GitHub followers API utilizing the String variation to create different cases.
I decided to create the custom featureFlag struct due to stored properties not being allowed inside of extensions. This way, we dont need to keep the stored properties on the views that will be feature flagged and instead keep all of the LaunchDarkly methods in one extension. This would allow us to only have to delete the extension and the function at the call site when it comes time to fully integrate the feature into the application and archive the feature flag in the platform.
The pagination switch statement changes the followersPerPage located in the NetworkManager. When the configureLDFeatureFlagOnMainThread() is called, it will change the followersPerPage to the appropriate value depending on the variation chosen in the dashboard. I included the third variation to test a feature flag with more than two variations.
Here, I have decided to insert the configureLDFeatureFlagOnMainThread() upon the success case whenever users are retrieved from the server. This way it will update as you scroll through a list of users.
The pagination feature flag is much easier to see while using the app. I recommend searching the user "twostraws" in the main view controller to see a large list of followers.
I then wanted to see how I can change UI elements in the app. I decided to do this in the UserInfoVC by using configureItemVCFlipLDFeatureFlag() at the call site for when a single user is sucessfully retrieved and is about to have their information displayed.
This is the result when activating the ItemView flipping feature flag.
