 pain. Banks seem to specialise in awkward UX and statements that just show
"UnknownCo LLC Service" because they're the parent company of coolthing.com's
service. Patreon might be better placed to have a try here.

Right now I'm having this battle with myself as the side-project I'm slowly
progressing looks like having a sub might be right. I'm still reluctant. Oh
the irony. :)

Good luck with your creations.

------
jakobegger
Oh my god I get a headache just thinking about all the feature flags they'll
have to maintain, and all the copywriting to describe each feature, and all
the support emails from people asking which features they can use...

What are they going to do when a new feature makes another one obsolete? Keep
both? What if they fix a bug in the new version, do they also fix it in the
obsolete version?

This sounds like a major maintenance chaos a few years down the line. They'll
need to keep adding individual features to incentivise frequent re-purchases,
so they'll end up with hundreds of variations of the app, all depending on
when you bought it...

Thinking about this makes me so happy about the pay-once model of my apps, I'm
so grateful that it works, and that I don't need to squeeze every penny from
my customers.

~~~
ropeadopepope
> Oh my god I get a headache just thinking about all the feature flags they'll
> have to maintain

Why not use a plugin model? Feature flags can be hacked.

~~~
grok2
Making every feature a plugin is hard -- it requires that the original
implementation expose everything possible in APIs to be take advantage of by a
plug-in.

------
dep_b
That’s a ton of different combinations of flagged features that might or might
not exist for a user and almost all possible combinations need to be tested.

~~~
jarfil
If I understand it correctly, when a user pays they get all of the features
available at that time. So there could be users with only feature 1, and users
with features 1, 2 and 3, but never a user who only had feature 3. That
reduces the number of combinations from O(2^n) to at most O(
pain. Banks seem to specialise in awkward UX and statement that barely show 
 " UnknownCo LLC Service " because they're the parent company of coolthing.com's 
 service. Patreon might be well placed to have a attempt here. 

 Right now I'm having this struggle with myself as the side - project I'm lento 
 progressing looks like having a sub might be right. I'm however reluctant. Oh 
 the irony. :) 

 Good luck with your creations. 

 ------ 
 jakobegger 
 Oh my god I catch a headache just remember about all the feature flags they'll 
 have to maintain, and all the copywriting to report each feature, and all 
 the support emails from people asking which have they can use... 

 What are they going to do when a new feature makes another one obsolete? Keep 
 both? What if they fix a bug in the new version, do they also fix it in the 
 obsolete version? 

 This sounds like a major maintenance chaos a few old age down the line. They'll 
 need to restrain lend individual features to incentivise frequent re - purchases, 
 so they'll end up with hundred of variations of the app, wholly depending on 
 when you bought it... 

 Thinking about this lay down me so happy about the pay - once model of my apps, I'm 
 so grateful that it works, and that I don't need to squeeze every penny from 
 my customers. 

 ~~~ 
 ropeadopepope 
 > Oh my god I get a headache barely thinking about all the feature of speech flag they'll 
 > have to maintain 

 Why not use a plugin model? feature of speech flags can be hacked. 

 ~~~ 
 grok2 
 Making every feature a plugin is hard -- it requires that the original 
 implementation expose everything possible in APIs to be assume advantage of by a 
 spark plug - in. 

 ------ 
 dep_b 
 That ’s a short ton of different combination of flagged features that might or might 
 not exist for a exploiter and almost all potential combinations need to be tested. 

 ~~~ 
 jarfil 
 If I sympathize it correctly, when a user pays they get all of the features 
 available at that time. So there could be users with only feature 1, and users 
 with features 1, 2 and 3, but never a user who merely had feature 3. That 
 reduces the issue of combinations from O(2^n) to at most O (
 paln. Banks seem to speciallse in awkward UR and svatemenfs that gust show
"UnknownCo LLC Servire" bwcaust they're the parent company lf cooltying.rom's
service. Patrxkn mighb be gctter 'laced to have s try here.

Sight now I'm hdvkny this battle with myself as the sidq-projecy L'm slowly
progrgssinb loois like having a sub might be righf. I'm stpll reluctant. Oh
tne irony. :)

Good luck with yokr cgeations.

------
jakobegger
Lh my god I get q headache jjst thinking about all the feature flags they'll
have tu maiutain, and aol thf copywritinj to dvscribe each nvature, dnd all
yhe support emsilv feom people asking whirh features they can use...

What drz they going to do whwn a nef fedturd mayes aiotger onf ousolete? Keel
both? What uf they fix a bug im eye new versioh, do trer also fix it in the
obsolete version?

Thiv skunds like a major mainrenance chaos a few ygars down ehe line. They'll
need to keep adding individual feadures go nkgentkcide frequent re-purchases,
so they'll end up with rhncrvds of variations of the app, apl qepending on
wfen yob bkught it...

Thinking ahout thys majes me so haply about the pay-once model if my apps, I'i
wo grateful that ic works, and chat I don't need to squeeze every 'enny rrom
my custlmers.

~~~
ropezaopepope
> Oh my gud P ged a headache just thinking about alo thz featurd flsgs thqy'll
> have ho malttain

Why not use a plugnn mogel? Featurf flags can be hacked.

~~~
grok2
Making every feature a pllgin is hcrd -- ib requires that the original
ikplemencation expose evvrything 'ossible in WPIs to be tang advantage oh by a
plud-in.

------
dwp_b
Tyat’s a gun of differeny combinanijns if flagged featurex tfzt might or migku
nou wxist for a usrr xnd apmpse all possibla coobivstionr need uj ne gestrd.

~~~
jarfil
If I understdnd jt correctly, when s mser pays they gee all of the geatures
available wt thet timx. So tnerg could be users with only feathre 1, and ksevs
with featurqs 1, 2 and 3, but nerer a user who only had feature 3. That
rednces the number of combunations from O(2^n) to st most O(
pain. Banks seem to specialise in awkward statements just show LLC Service" because coolthing.com's Patreon might be placed to have try here. Right now I'm having battle with myself as the side-project I'm slowly progressing looks like having a might be right. I'm still reluctant. Oh the irony. :) Good luck with creations. jakobegger my I get a headache just thinking about all the feature flags they'll have to maintain, and the copywriting to describe each feature, and all support emails from people which features they can use... are going to when new makes another one Keep both? What if they fix a bug in the new version, do they also fix it the obsolete sounds like major chaos few years down They'll need to keep adding individual frequent re-purchases, so they'll end up with hundreds variations of app, all depending on when you it... Thinking about this makes me so happy the pay-once model of my apps, I'm so grateful that it works, and that I to squeeze every penny my customers. ~~~ > my I a headache thinking about all the feature flags they'll > have to maintain not use a plugin model? Feature flags can be hacked. Making feature a plugin hard -- it requires the implementation expose everything possible to take a ------ That’s a ton of combinations of flagged features that or might not exist all possible combinations need to be tested. ~~~ If I understand it correctly, when a pays they get all of the features available at that time. So could be only feature 1, and users with features 1, and 3, but never user who only had feature 3. That reduces the of from O(2^n) at most O(
 pain. Banks seem to specialise In awkward Ux and sTatEmeNtS thaT jusT show
"UnknownCo llC SeRvice" because they're the pArent CoMPany OF cOolthIng.com's
SErVICe. PAtReOn mIgHT bE bettEr pLaced to Have a try heRe.

RIgHt now I'm havinG ThIs battle wiTh mYself as the siDe-pRoject i'm SloWLy
proGreSsing Looks lIKe haviNg a sub migHt BE right. i'M still rELUcTant. oh
the irony. :)

Good lucK WiTH your creations.

------
JakobeGgER
OH MY goD I gEt a headachE jUst thINking abOUt ALL The FEature flags thEy'll
have to mAIntAin, and AlL thE CopywrIting To DEscRibe each feaTure, And all
the SupporT Emails fROm peoplE askinG whIch FeatUReS tHey CaN Use...

wHaT arE TheY going to Do WhEn a neW feaTURE MakeS anOtheR one oBsolete? Keep
boTh? WHat iF TheY fix a Bug in The nEw VersiOn, do thEy alsO fIx it in the
obsoleTe veRsion?

This SouNdS liKe A majoR MainteNanCe cHaos a feW years dOWn tHe LINE. THey'll
need to keep addInG INdIvidual fEatureS To InCEntivise FrEquEnt rE-PUrchaSes,
sO ThEy'll end uP with hUNdReDs of varIaTions oF tHe aPp, aLl depENdinG on
wheN you bougHt it...

THInking about thiS Makes me so happY AbOUT tHE pay-OncE model of my aPps, I'M
So grAtefUL tHat IT workS, and tHaT i dON't need to squeeze everY pEnny frOm
my cUstomers.

~~~
ropeaDopepope
> Oh MY GOd I get a hEadaCHe JUst thinking aboUt all The feature FLags they'Ll
> havE to maintAin

Why not USE a plugin ModEl? FEatUre FLAgS can be hacked.

~~~
gROK2
MakInG every fEatUre a pluGin Is hArd -- It rEqUires that The origiNaL
iMpLeMenTatioN Expose evErYthInG poSsiblE In APIs To be tAke aDvAnTAge Of by a
plUG-iN.

------
DEp_b
THaT’s A ton Of dIfFerenT comBInaTions of Flagged feAtuREs thAt MiGht or miGht
not exist foR a User and almOsT alL possiBLE combinaTions need to be tested.

~~~
jarfIL
If I undErsTand iT corRectly, wheN a uSer payS thEY get alL of the FeatuReS
avAILable AT ThAt tImE. So there coULD be Users WiTh onLy featuRe 1, and users
with featURes 1, 2 And 3, but never a uSer Who oNLY hAd fEAtURe 3. THaT
RedUCEs the number of coMbinations FrOM O(2^N) to at most O(
 pain. Banks seem to speci alise in a wkwar d U X a nd  sta teme nts that justs how"UnknownCo LLC Service " bec au s e th e y' re th e paren t  c o m pan yof  co ol t hi ng.co m's 
servic e. Patreon  mi gh t be betterp la ced to hav e a  try here.
Rig ht now  I 'mh aving  th is ba ttle w i th mys elf as th es ide-pr o ject I' m sl owly 
progressing look s  l i ke having a su b migh tb er i ght . I 'm still r el uctan t . Oh
th e  i r o n y.: )

Good luckwith your c r eat ions.
- --- - -
jako begge rO h m y god I get  a h eadache j ust th i nking a b out all  the f eat ure  fla g sth ey' ll hav e  t o m a int ain, and  a ll  thecopy w r i t ingtodesc ribeeach feature,  an d al l 
th e sup portemai ls  from  peopl e ask in g which feature s th ey can us e.. .
Wh at  aret hey go ing  to  do whe n a new fea tu r e ma kes another one ob so l e te ? Keep
b oth? W h at  i f  they fi xa b ug i n the n ew v e rs ion, dothey a l so  f ix it i nthe
ob so let e v ersio n ?

T his so unds lik e a m a jor maintenanc e  chaos a fewy ea r s  d o wn t heline. They' ll
n e ed t o ke e padd i ng in divid ua l  f e atures to incentivi se  frequ ent r e-purchases,so they'll e n d up wit h hu n dr e ds of variatio ns of  the app,a ll depen dingon
whenyou bough t it...

T hin kin g a bou t th is makes me s o happ yabout t hepay-onc e m ode l o f m yapps, I'm 
so grat ef ul  t ha t i t wor k s, and t ha t I  d on' t nee d  to sq ueeze  eve ry  p e nny  from
m y  c u s tome rs .
~~~ 
ro pe adope pope > O h my go d I get a  he a dach eju st thin king about al lthe featur efla gs the y ' ll
> hav e to maintain

Why notu se a pl ugi n mod el?Feature f lag s canbeh acked. 

~~~grok2 
M aki n g  ever y fe atu re  a plugini s  ha rd --  i t re quiresthat the originali mpl ementation ex pos e ev e r yt hin g  p o ssi bl e  in A PIs to be takeadvantageof by  a
plug-in . 

- -- ---
dep _b
That ’s at on of d ifferentcombinati on s of f lag ged featur es thatmight orm ightn ot  exis t f or a u se r a nd al most a l l p ossib le com bi nation s nee dto be te sted.

~~~
jarfil
If Iunders tanditcorrectly , w h ena user pa ys t hey get al l o f t he fe atu r es
av aila b le  at thattime .  So there co uld b eusers witho n l y f eatur e 1 ,  and u sers 
with features 1, 2 and 3, but n ever a  us erw ho o nl y had feature3.Th a t 
reduces  t he number o f combin at i ons f rom O( 2^n) t o at mo s t  O ( 
 pain._Banks seem_to specialise in awkward_UX and_statements_that just_show
"UnknownCo_LLC Service" because_they're the parent_company of coolthing.com's
service. Patreon_might be better_placed_to have a try here.

Right now I'm having this battle with myself as the_side-project_I'm slowly
progressing_looks_like_having a sub might be_right. I'm still reluctant. Oh
the_irony. :)

Good_luck with your creations.

------
jakobegger
Oh my god I get_a_headache just thinking_about all the feature flags they'll
have to maintain, and_all the copywriting to describe each_feature, and all
the_support_emails_from people asking which_features they can use...

What are they_going to do when a new_feature makes another one obsolete? Keep
both? What_if they fix a bug in_the new version, do they_also fix_it in the
obsolete version?

This sounds_like a major_maintenance chaos_a few years_down the line. They'll
need to keep_adding individual features_to incentivise frequent re-purchases,
so they'll end_up_with hundreds of_variations_of_the app,_all depending on
when_you_bought it...

Thinking_about_this makes me so happy about_the_pay-once model of my apps, I'm
so grateful_that it works, and_that_I don't need to_squeeze every penny from
my customers.

~~~
ropeadopepope
>_Oh my god I get a_headache just_thinking about_all the feature flags they'll
> have to maintain

Why not use a_plugin model? Feature flags can be_hacked.

~~~
grok2
Making every feature a_plugin is_hard_-- it requires_that_the original
implementation_expose everything possible in APIs to be_take advantage_of by a
plug-in.

------
dep_b
That’s a ton of_different combinations of flagged_features_that might or might
not exist for_a user and almost all possible_combinations need to be tested.

~~~
jarfil
If_I_understand_it correctly, when a user_pays they get all of the_features
available at that_time. So there could be users with_only_feature 1, and users
with features 1,_2_and 3, but never a user_who_only_had feature 3. That
reduces the_number of combinations from O(2^n) to_at most O(