Forum Discussion
Customizing the "modern" experiences in SharePoint Online - your opinion?
I only have permissions to build solutions that do not involve the app catalog, do not require access tokens, basically if the technology requires SharePoint Admin permissions or approval, I'm not able to use that technology to build my solutions and I currently see Modern Pages, the way they are today as another restriction.
I recently implemented a new intranet site with Modern Pages, the repsonse was not favorable, it was actually over whelmingly negative.
#1 complaint by users and management - the huge unmodifiable header. #2 - limited ability to modify the page, #3 - Branding - having the departments logo cutoff and placed inside the Sqaure in the upper left, why?
For now all Modern pages have been replaced with Classic Web part pages.
Dynamic functionality:
All the new technologies, Add-Ins and SharePoint Framework - for building Modern Page Webparts, are great unless you do not have permission to add them to the App Catalog.
As you may know, getting in-house custom apps approved to be included in a large Enterprise is a tough sell. Lot's of things to consider before this type of solution is allowed into the eco system, IP protection policies, black-out periods, long review board processes, long term support issues etc...
Nothing new, but at least in Classic mode I can rely on InfoPath or the Script Editor webpart without having to worry about going through all the red tape everytime I need to build or modify something.
Currently I see a lot of emphasis on the developer story for Modern Pages and very little on the PowerUser, Domain Expert, Citizen Developer with limited permissions story, which are the ones who in my experience are the primary solution devs for their departments. I completely understand that changes take time and I'm really looking forward to a better story for the Citizen Dev concerning Modern Pages. But until then no Modern Pages will be implemented in my departments Sharepoint sites.
Sure there's also PowerApps, which I understand is replacing InfoPath and I'm currently trying to get a couple of apps I'm developing implemented in the Enterprise, but this type of solution is outside of Modern Pages for now. Please correct me if I'm misunderstanding but currently from what I've read, there's no way to embed these forms, apps in a Modern page without special permissions, special work arounds. Not all solutions should be mobile enabled, which is what PowerApps are by default.
It will be interesting to see how all this plays out.
I really do appreciate all the efforts of the Sharepoint Engineering team, I'm learning all I can about these new technologies which I think are very useful, but are unfortunatley non starters for myself unless I develop them outside of my employer, which is another layer of red tape.
I'm just trying to explain why I'm currently not able to use Modern pages in my day job from the perspective of having limited permissions and no ability to modify the pages outside of the provided Webparts.
Basically if the technology used to build the solution requires the App Catalog, it will be in a lot cases a non starter and I will need to look to other solutions outside of Modern Pages.