Introducción a SharePoint 2013

Notas del editor

• #16 Key points (bullets refer 1:1 to the 6 sentences on the slide).New Office 365 opportunityWith Office 365, a developer can now assume that Exchange, Lync, SharePoint servers are available even for a small business scenarios. That opens the door to creating apps that leverage SharePoint for collaboration, Lync for voice, without worrying about their availability anywhere. Imagine an app for a real-estate lawyer collaborating with a client, with SharePoint serving as the backend for collaboration and Microsoft Word in the front. New Class of Appscontextual apps in office, can understand the content and help you with scenarios such as data mashups with Excel and content augmentation for Word. developers can host their own service that powers apps which makes app updates and new features easy to add, along with a simple in-application app update process [same as wp7, iOS – you have 3 app updates, we’ll do something similar]new model makes building apps that target office and/or SharePoint on mobile devices easy. It also makes writing native apps that target SharePoint easier with client side libraries that match those available on the server.Increased Productivityconsistency is good, it’s a single model across client and server, we’re reducing the API surface area to remove redundancy, and we’re doing things like making API’s between SharePoint and the client side object model identical, this means less time learning and more time coding.javascript is used by 90% of developers today, we want them all writing apps for office and SharePoint, by leveraging standard web technologies in office 15 we’re making it easy for them to use what they know.
• #17 Key points (bullets refer 1:1 to the 6 sentences on the slide).New Office 365 opportunityWith Office 365, a developer can now assume that Exchange, Lync, SharePoint servers are available even for a small business scenarios. That opens the door to creating apps that leverage SharePoint for collaboration, Lync for voice, without worrying about their availability anywhere. Imagine an app for a real-estate lawyer collaborating with a client, with SharePoint serving as the backend for collaboration and Microsoft Word in the front. New Class of Appscontextual apps in office, can understand the content and help you with scenarios such as data mashups with Excel and content augmentation for Word. developers can host their own service that powers apps which makes app updates and new features easy to add, along with a simple in-application app update process [same as wp7, iOS – you have 3 app updates, we’ll do something similar]new model makes building apps that target office and/or SharePoint on mobile devices easy. It also makes writing native apps that target SharePoint easier with client side libraries that match those available on the server.Increased Productivityconsistency is good, it’s a single model across client and server, we’re reducing the API surface area to remove redundancy, and we’re doing things like making API’s between SharePoint and the client side object model identical, this means less time learning and more time coding.javascript is used by 90% of developers today, we want them all writing apps for office and SharePoint, by leveraging standard web technologies in office 15 we’re making it easy for them to use what they know.
• #18 Key points (bullets refer 1:1 to the 6 sentences on the slide).New Office 365 opportunityWith Office 365, a developer can now assume that Exchange, Lync, SharePoint servers are available even for a small business scenarios. That opens the door to creating apps that leverage SharePoint for collaboration, Lync for voice, without worrying about their availability anywhere. Imagine an app for a real-estate lawyer collaborating with a client, with SharePoint serving as the backend for collaboration and Microsoft Word in the front. New Class of Appscontextual apps in office, can understand the content and help you with scenarios such as data mashups with Excel and content augmentation for Word. developers can host their own service that powers apps which makes app updates and new features easy to add, along with a simple in-application app update process [same as wp7, iOS – you have 3 app updates, we’ll do something similar]new model makes building apps that target office and/or SharePoint on mobile devices easy. It also makes writing native apps that target SharePoint easier with client side libraries that match those available on the server.Increased Productivityconsistency is good, it’s a single model across client and server, we’re reducing the API surface area to remove redundancy, and we’re doing things like making API’s between SharePoint and the client side object model identical, this means less time learning and more time coding.javascript is used by 90% of developers today, we want them all writing apps for office and SharePoint, by leveraging standard web technologies in office 15 we’re making it easy for them to use what they know.
• #19 Key points (bullets refer 1:1 to the 6 sentences on the slide).New Office 365 opportunityWith Office 365, a developer can now assume that Exchange, Lync, SharePoint servers are available even for a small business scenarios. That opens the door to creating apps that leverage SharePoint for collaboration, Lync for voice, without worrying about their availability anywhere. Imagine an app for a real-estate lawyer collaborating with a client, with SharePoint serving as the backend for collaboration and Microsoft Word in the front. New Class of Appscontextual apps in office, can understand the content and help you with scenarios such as data mashups with Excel and content augmentation for Word. developers can host their own service that powers apps which makes app updates and new features easy to add, along with a simple in-application app update process [same as wp7, iOS – you have 3 app updates, we’ll do something similar]new model makes building apps that target office and/or SharePoint on mobile devices easy. It also makes writing native apps that target SharePoint easier with client side libraries that match those available on the server.Increased Productivityconsistency is good, it’s a single model across client and server, we’re reducing the API surface area to remove redundancy, and we’re doing things like making API’s between SharePoint and the client side object model identical, this means less time learning and more time coding.javascript is used by 90% of developers today, we want them all writing apps for office and SharePoint, by leveraging standard web technologies in office 15 we’re making it easy for them to use what they know.
• #21 Key points (bullets refer 1:1 to the 6 sentences on the slide).New Office 365 opportunityWith Office 365, a developer can now assume that Exchange, Lync, SharePoint servers are available even for a small business scenarios. That opens the door to creating apps that leverage SharePoint for collaboration, Lync for voice, without worrying about their availability anywhere. Imagine an app for a real-estate lawyer collaborating with a client, with SharePoint serving as the backend for collaboration and Microsoft Word in the front. New Class of Appscontextual apps in office, can understand the content and help you with scenarios such as data mashups with Excel and content augmentation for Word. developers can host their own service that powers apps which makes app updates and new features easy to add, along with a simple in-application app update process [same as wp7, iOS – you have 3 app updates, we’ll do something similar]new model makes building apps that target office and/or SharePoint on mobile devices easy. It also makes writing native apps that target SharePoint easier with client side libraries that match those available on the server.Increased Productivityconsistency is good, it’s a single model across client and server, we’re reducing the API surface area to remove redundancy, and we’re doing things like making API’s between SharePoint and the client side object model identical, this means less time learning and more time coding.javascript is used by 90% of developers today, we want them all writing apps for office and SharePoint, by leveraging standard web technologies in office 15 we’re making it easy for them to use what they know.
• #22 Key points (bullets refer 1:1 to the 6 sentences on the slide).New Office 365 opportunityWith Office 365, a developer can now assume that Exchange, Lync, SharePoint servers are available even for a small business scenarios. That opens the door to creating apps that leverage SharePoint for collaboration, Lync for voice, without worrying about their availability anywhere. Imagine an app for a real-estate lawyer collaborating with a client, with SharePoint serving as the backend for collaboration and Microsoft Word in the front. New Class of Appscontextual apps in office, can understand the content and help you with scenarios such as data mashups with Excel and content augmentation for Word. developers can host their own service that powers apps which makes app updates and new features easy to add, along with a simple in-application app update process [same as wp7, iOS – you have 3 app updates, we’ll do something similar]new model makes building apps that target office and/or SharePoint on mobile devices easy. It also makes writing native apps that target SharePoint easier with client side libraries that match those available on the server.Increased Productivityconsistency is good, it’s a single model across client and server, we’re reducing the API surface area to remove redundancy, and we’re doing things like making API’s between SharePoint and the client side object model identical, this means less time learning and more time coding.javascript is used by 90% of developers today, we want them all writing apps for office and SharePoint, by leveraging standard web technologies in office 15 we’re making it easy for them to use what they know.
• #23 Key points (bullets refer 1:1 to the 6 sentences on the slide).New Office 365 opportunityWith Office 365, a developer can now assume that Exchange, Lync, SharePoint servers are available even for a small business scenarios. That opens the door to creating apps that leverage SharePoint for collaboration, Lync for voice, without worrying about their availability anywhere. Imagine an app for a real-estate lawyer collaborating with a client, with SharePoint serving as the backend for collaboration and Microsoft Word in the front. New Class of Appscontextual apps in office, can understand the content and help you with scenarios such as data mashups with Excel and content augmentation for Word. developers can host their own service that powers apps which makes app updates and new features easy to add, along with a simple in-application app update process [same as wp7, iOS – you have 3 app updates, we’ll do something similar]new model makes building apps that target office and/or SharePoint on mobile devices easy. It also makes writing native apps that target SharePoint easier with client side libraries that match those available on the server.Increased Productivityconsistency is good, it’s a single model across client and server, we’re reducing the API surface area to remove redundancy, and we’re doing things like making API’s between SharePoint and the client side object model identical, this means less time learning and more time coding.javascript is used by 90% of developers today, we want them all writing apps for office and SharePoint, by leveraging standard web technologies in office 15 we’re making it easy for them to use what they know.
• #24 Key points (bullets refer 1:1 to the 6 sentences on the slide).New Office 365 opportunityWith Office 365, a developer can now assume that Exchange, Lync, SharePoint servers are available even for a small business scenarios. That opens the door to creating apps that leverage SharePoint for collaboration, Lync for voice, without worrying about their availability anywhere. Imagine an app for a real-estate lawyer collaborating with a client, with SharePoint serving as the backend for collaboration and Microsoft Word in the front. New Class of Appscontextual apps in office, can understand the content and help you with scenarios such as data mashups with Excel and content augmentation for Word. developers can host their own service that powers apps which makes app updates and new features easy to add, along with a simple in-application app update process [same as wp7, iOS – you have 3 app updates, we’ll do something similar]new model makes building apps that target office and/or SharePoint on mobile devices easy. It also makes writing native apps that target SharePoint easier with client side libraries that match those available on the server.Increased Productivityconsistency is good, it’s a single model across client and server, we’re reducing the API surface area to remove redundancy, and we’re doing things like making API’s between SharePoint and the client side object model identical, this means less time learning and more time coding.javascript is used by 90% of developers today, we want them all writing apps for office and SharePoint, by leveraging standard web technologies in office 15 we’re making it easy for them to use what they know.