https://www.growthbook.io/ logo
#announcements
Title
# announcements
f

flat-advantage-68891

12/20/2022, 1:20 AM
Wondering how people are managing toggles in Mobile apps because of the following scenario. Let’s say you push build 1.0.0 to the App Store and release that build to the public. This build includes a Feature A (completed) and Feature B (partially complete). The team continues developing over the next two weeks and pushes build 1.1.0 to the App Store and releases it. This build includes code that completes Feature B (completed) and the beginnings of a new Feature C (partially complete). At this point in time there are some users of the app that have v1.1.0 and some that are using v1.0.0 still. How do you make sure that you don’t accidentally turn on Feature B until all the active clients are updated to version v1.1.0?
f

fresh-football-47124

12/20/2022, 1:25 AM
you can add the build version to the user attribute, and then target releases to versions. We currently don’t support SemVer comparisons, but you can do regexp matching
f

flat-advantage-68891

12/20/2022, 1:25 AM
Ah thx so much
f

fresh-football-47124

12/20/2022, 1:26 AM
(or do some kind of semantic version to integer as the attribute)
that might be easiest
f

flat-advantage-68891

12/20/2022, 1:28 AM
hmm, yeah I guess conceptually what I want is for it in production to not be able to be enabled unless the user is on a “minimum version” or greater.
@fresh-football-47124 is there any support for us implementing custom toggle types or custom evaluation of toggles locally?
f

fresh-football-47124

12/20/2022, 1:30 AM
what SDK are you using?
f

flat-advantage-68891

12/20/2022, 1:32 AM
Flutter
f

fresh-football-47124

12/20/2022, 1:33 AM
if you only have three levels in your semantic versioning - you could split it as attributes, eg: 1.2.12 would be: major_version: 1 minor_version: 2 build_version: 12 then the targeting could be very specific
f

flat-advantage-68891

12/20/2022, 1:33 AM
yeah, I was just thinking that
then I could use the greater than comparison
and I wouldn’t need custom evaluation
f

fresh-football-47124

12/20/2022, 1:33 AM
correct
I can check with the team if we can build semantic versioning comparison into the SDK
but I dont have a timeline for it
f

flat-advantage-68891

12/20/2022, 1:34 AM
cool
I have another question if you have a minute
f

fresh-football-47124

12/20/2022, 1:34 AM
yep
f

flat-advantage-68891

12/20/2022, 1:35 AM
I am wondering where you all stand on contributions. We have effectively built a wrapper around the Flutter SDK to add support for it working in automated testing, for local overrides, etc. https://github.com/uptech/uptech-growthbook-sdk-flutter
A lot of this is stuff that should probably just be rolled into the Flutter SDK
f

fresh-football-47124

12/20/2022, 1:36 AM
oh cool
ya, we welcome contributions
f

flat-advantage-68891

12/20/2022, 1:36 AM
I also have a list of small things that I feel should change with the Flutter SDK to match the others better.
f

fresh-football-47124

12/20/2022, 1:37 AM
that would be great
I’m not a flutter expert
can you open issues? or would you like to meet with that team?
f

flat-advantage-68891

12/20/2022, 1:37 AM
Yeah, I can open issues and pull requests
Just wasn’t sure if you had a standard approach for facilitating contributions
like standards / requirements
f

fresh-football-47124

12/20/2022, 1:40 AM
we have a contribution guide
f

flat-advantage-68891

12/20/2022, 1:40 AM
I am pretty experienced with Feature Toggles and built an open source library for them in the Ruby ecosystem years ago. https://github.com/uptech/togls
10 Views