Timeline for (Why) Should I Use Lightning Apps?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 15, 2020 at 8:11 | history | edited | CommunityBot |
Commonmark migration
|
|
| Sep 2, 2015 at 16:44 | comment | added | pchittum | An app built with lightning components isn't really an app without access to Salesforce data, that's true. But a single component can be large or small. And there is opportunity for SOC in a single component, particularly in smaller discreet components. Perhaps your definition of SOC is a bit too narrow? But you're welcome to disagree. :-) | |
| Aug 30, 2015 at 16:29 | comment | added | altius_rup | @Peter "Separation of Concerns" is a design pattern concept and term which supposes that the app clearly separates parts such as UI, controller/services, model/data, etc. Lightning Components do not separate the model/data from the rest : they are necessarily linked up to the Salesforce data model. They are precisely linked up with the Salesforce server data model : it is not possible to develop an offline mobile app with SmartSync from the SF Mobile SDK with Lightning Components. That is why I suggest Lightning Components do not adhere to the "Separation of Concerns" design pattern. | |
| Jul 24, 2015 at 9:40 | history | edited | pchittum | CC BY-SA 3.0 |
Made updates based on current state of implementation of Lightning Components.
|
| Mar 4, 2015 at 16:05 | comment | added | Adrian Larson♦ |
I would add to this that you cannot create a Lightning Homepage Component. Score one more for VisualForce!
|
|
| Feb 27, 2015 at 18:06 | comment | added | Adrian Larson♦ | Ah yes, this is what I was looking for. All good answers but you offer the best response to my final question: "What types of problems are they worse at handling?" Thanks! | |
| Feb 27, 2015 at 18:04 | vote | accept | Adrian Larson♦ | ||
| Feb 27, 2015 at 16:46 | history | answered | pchittum | CC BY-SA 3.0 |