SOLVED

spfx vs tradition addin

%3CLINGO-SUB%20id%3D%22lingo-sub-180487%22%20slang%3D%22en-US%22%3Espfx%20vs%20tradition%20addin%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-180487%22%20slang%3D%22en-US%22%3E%3CP%3Espfx%20vs%20tradition%20addin%2C%20which%20one%20will%20microsoft%20support%20the%20most%20in%20the%20furture%3F%20thanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-182651%22%20slang%3D%22en-US%22%3ERe%3A%20spfx%20vs%20tradition%20addin%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-182651%22%20slang%3D%22en-US%22%3E%3CP%3ESuper%20thanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-180565%22%20slang%3D%22en-US%22%3ERe%3A%20spfx%20vs%20tradition%20addin%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-180565%22%20slang%3D%22en-US%22%3EEy%20Peter%2C%20my%202%20cents%20here%3A%3CBR%20%2F%3E1.%20SPFx%20will%20not%20bring%20remote%20event%20receivers.%20You%20have%20to%20take%20a%20look%20at%20the%20possibilities%20that%20webhooks%20bring%20to%20you%3CBR%20%2F%3E2.%20You%20are%20right%20and%20here%20Microsoft%20has%20promised%20to%20provide%20more%20capabilities%20to%20SPFx%20extensions%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-180563%22%20slang%3D%22en-US%22%3ERe%3A%20spfx%20vs%20tradition%20addin%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-180563%22%20slang%3D%22en-US%22%3E%3CP%3ESPFx%20should%20be%20the%20way%20to%20to%20replace%20%3CSTRONG%3ESharePoint%20hosted%20add-in%3C%2FSTRONG%3E.%20Although%20there%20are%20still%20few%20scenario%20where%20add-in%20is%20still%20unavoidable%3A%3C%2FP%3E%3CUL%3E%3CLI%3EProvider%20hosted%20add-ins%20where%20customisation%20can't%20be%20achieved%20by%20Client%20side.%3C%2FLI%3E%3CLI%3EApp%20Only%20permissions.%3C%2FLI%3E%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-180559%22%20slang%3D%22en-US%22%3ERe%3A%20spfx%20vs%20tradition%20addin%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-180559%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20Juan%2C%20you%20know%20where%20we%20can%20get%20the%20roadmap%20for%20spfx%3F%20I%20believe%20we%20still%20can't%20do%20these%20thing%20in%20spfx%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1.%20remote%20event%20receiver%3C%2FP%3E%3CP%3E2.%20applicationcustomizer%20is%20too%20weak%2C%20only%20top%20and%20bottom%20panel%20can%20be%20customize%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-180511%22%20slang%3D%22en-US%22%3ERe%3A%20spfx%20vs%20tradition%20addin%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-180511%22%20slang%3D%22en-US%22%3EClearly%20SPFx...AddIns%20are%20still%20supported%2C%20but%20Microsoft%20has%20not%20done%20any%20investments%20for%20years%20in%20the%20AddIns%20platform%3C%2FLINGO-BODY%3E
Highlighted
Contributor

spfx vs tradition addin, which one will microsoft support the most in the furture? thanks

5 Replies
Highlighted
Clearly SPFx...AddIns are still supported, but Microsoft has not done any investments for years in the AddIns platform
Highlighted

Thanks Juan, you know where we can get the roadmap for spfx? I believe we still can't do these thing in spfx:

 

1. remote event receiver

2. applicationcustomizer is too weak, only top and bottom panel can be customize

 

Highlighted

SPFx should be the way to to replace SharePoint hosted add-in. Although there are still few scenario where add-in is still unavoidable:

  • Provider hosted add-ins where customisation can't be achieved by Client side.
  • App Only permissions.
Highlighted
Solution
Ey Peter, my 2 cents here:
1. SPFx will not bring remote event receivers. You have to take a look at the possibilities that webhooks bring to you
2. You are right and here Microsoft has promised to provide more capabilities to SPFx extensions
Highlighted

Super thanks