Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (13)
Destaque
Semelhante a Apps en office15
Semelhante a Apps en office15 (20)
Mais de Mario Cortés Flores
Mais de Mario Cortés Flores (20)
Apps en office15
- 1. Apps
- 2. Agenda
- 3. Hybrid On Premises Online La mejor experiencia entre Cloud según tus dispositivos necesidades Voice Content Enterprise Reporting Messaging & Video Management Social & Analytics Integrando mejores soluciones
- 4. Touch Mode añade más espacio y es Con un toque el más finger-friendly ribbon se puede minimizar Responder Inline te permite componer correos sin salir del contexto Rápido y fluido para accede a tu calendario, personas, tareas sin salir del inbox Barra de navegación con accesos rápidos ocupando menos espacio
- 5. Nueva vista de presentación que con la que enfocarte en tu audiencia Anotaciones mientras presentas Pinch & zoom con los dedos
- 6. Log in to Office 365 from a browser to update your user profile and install the latest version of the Office apps Select your language to start installing the new Office apps El Nuevo Offic se descaga mediante streaming en tu PC
- 9. Arquitectura Cross-device Nombre para las soluciones de Office 2013 App Catalog Server Web Server App Web Manifest Page App <XML> HTML+JS La potencia de la Web Basado en estándars Seguras Un App es una region donde las aplicaciones de Las Apps se desarrolland con tecnologías Apps están securizadas por un modelo Office extienden la funcionalidad con HTML y estándar como CSS, HTML and JavaScript de permisos y una ejecución en JavaScript sandboxed.
- 10. Office Creado con tecnologías Web
- 11. Office Multiplatafomra & Cross-app (Web / Desktop) (Web / Desktop / Mobile Web) (Desktop) (Desktop)
- 12. Office Tres formas de usarse dentro de Office
- 13. Office Integra Desafío Escenario Beneficios Dificultad al integrar Office con información Crear un conjunto de soluciones proveniente de Extender soluciones y proporcionar en la web. multiples orígenes de información, local, on- contenido web enriquecido. Mejorar la premise, o web. productividad unificando multiples tareas desde un Entorno familiar.
- 14. Outlook Write once, run everywhere Basado en estándares Seguro Outlooks Apps son compatibles con Desarrollado en tecnologías web como Outlook Apps están diseñados a tres niveles de distintos dispositivos. Corre desde CSS, HTML5 and JavaScript. permisos y se ejecuta en un proceso ailsado. Outlook, Outlook Web App y Mobile Outlook Web App.
- 15. Escenarios Business Processes Sales & Marketing, Rich Web content YouTube Video, Photo Gallery Finance, HR Content Resumes, Contracts Authoring Data Visualization, Maps, Custom charts, Lookups Team Collaboration Content & Project Management Analysis & Mashup Dashboards Data Analysis, Reference Tools Translation, Definitions, Data Mashups Workflow Document Approval, Dictionary, Help, Research Expenses Forms & Legal Forms, Content Authoring & Doc builders, Print services Reports Financial Reports Publishing Contextual Business data lookup (CRM), Content & Services Contextual forms (surveys) Workflow and Project tracking, Collaboration Coauthoring Office App in SharePoint Document Template Document Document Template Template App App App App App App App App App App App App App
- 17. demo Uso de App desde Excel y Word
- 19. Selección, Control Flexibilidad OFFICE 365 TRIAL/ PURCHASE TRIAL/ LEAD
- 20. Licenciamiento desde el Office Store
- 21. Herramientas de Desarrollo Visual Studio 2012 Blend Desarrollo para Office365 con “Napa”
- 22. demo Desarrollo de un App
Notas do Editor
- Key points (bullets refer 1:1 to the 6 sentences on the slide).Develop different development approach for client and server, different tools, different languages, different development approach for online & on-prem, on-prem you use full trust code, online you use the sandboxbroad and deep tools give developers a large surface area to learn but also the large surface area they want, this is one of the reasons we have so many developers today, approx 4m targetting Office, but it’s also something that we want to drive consistency around.Deployclient – simply getting new bits on a desktop can be hard, if not impossible, in a corporate environment. difficult to control user installing add-ins to office, hard to manage them when they’re installed, next to impossible to monitor them. This makes support hard, it makes upgrade hard (add-ins break on upgrade or break upgrade) and it makes IT governance very hard.server – on-prem custom solution deployment is almost always full-trust, which requires farm admin rights to install and the code has full access to the farm. Online custom solution deployment can ONLY be in the sandbox, which is limited in functionality and not widely adopted since it was introduced in SharePoint 2010. Both of these limit options for custom code, both online and on-premUsewe have 1000+ SharePoint 2010 isvs solutions today, there is no way to centrally discover, purchase and install them, office has thousands of add-ins, there is no way to centrally discover, purchase and install them. when users do find and install them in many cases for office client it’s without it’s knowledge, for sharepoint they’re just stuck, even if they find a tool or solution that will solve their problem they have to talk to IT and get them to approve 3rd party full-trust code, this usually take a while…office add-ins can crash or degrade the office experience because they run in-process with the application, as do SharePoint solutions. A bad add-in or SharePoint solution can bring the app or server to a halt. this makes for painful support calls as generally users will blame the application (like Outlook) and not connect the add-in they just installed with the issue, it makes for a bad user experience all round. In the case of SharePoint bad code can degrade the service for everyone. You might have experienced Outlook just hanging there doing nothing, because an add-in is working away on your email and the add-in is running in the same process as Outlook, so the core application cannot proceed.
- Use this slide to land how this architecture allows us to think cross-device because there is no footprint on the machine/client. Just like a web page. For example, a com add-in requires local install which is not conducive to platforms such as iOS. This new architecture is fully conducive to those devices.
- Establish how the model works across Office and SharePoint.
- 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.
- 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.