IDC MarketScape: Worldwide Cloud Professional Services 2014 Vendor Analysis

IDC MarketScape: Worldwide Cloud Professional Services 2014 Vendor Analysis

IDC and Microsoft – Successful Cloud Partners eBook (4)_1

Advertisements

Vuforia Beginner Tutorial

Vuforia Beginner Tutorial

 

This is a very basic tutorial to get the Vuforia AR samples running on your iPhone..

Requirements:

  • Latest edition iPhone
  • Apple MacBook or Mac with latest High Sierra
  • Xcode installed

 

  1. Update your Apple Mac and iPhone
  2. Download and install Xcode from App Store on your MacBook Pro
  3. Create account on https://developer.vuforia.com/
  4. Download the iOS SDK – https://developer.vuforia.com/downloads/sdk#downloadModal
  5. Download the Samples – https://developer.vuforia.com/downloads/samples#downloadModal
  6. Extract the SDK files
  7. Extract the Samples files
  8. Select and Copy VoforiaSample into Voforia-SDK-ios…\samples folder
  9. Connect your iPhone into your MacBook pro via USB
  10. Open the VuforiaSamples.xcodeproj file in XCode
  11. Follow instructions here – https://library.vuforia.com/articles/Solution/Getting-Started-with-Vuforia-for-iOS-Development.html
  12. Setup Project to run on iPhone Device
  13. Change the General | Identify |Bundle Identifier – https://help.apple.com/xcode/mac/9.0/index.html?localePath=en.lproj#/deve21d0239c
  14. Change Singing to your Apple Developer account
  15. Log in to your Vuforia account and create a license key Search and find the following string: Vuforia::setInitParameters(mVuforiaInitFlags as per https://library.vuforia.com/articles/Solution/How-To-add-a-License-Key-to-your-Vuforia-App
  16. Build and Run the App
  17. On the iPhone – General | Device Management and then approve the App

Microsoft Security Technologies

Microsoft Security Technologies

 

ISM Info

ISM Info

 

Security Maturity Model Questionnaire

Security Maturity Model Questionnaire

 

Underprepared • Implement security processes with formal guidelines across all departments • Automate cybersecurity processes wherever possible • Conduct periodic reviews to fine tune security operations In Transition • Assess suppliers and contractors to ensure they fulfil information security assurances • Align business needs with security requirements to avoid competing objectives and ensure the entire organisation pursues the same goal • Implement incident response and management procedures that enable users to take immediate action Security Leaders • Automate as many cybersecurity processes as possible • Integrate threat intelligence into automated processes to help tools find threats that slipped through network defences • Align business and security needs to achieve cloud adoption and other digital transformation business objectives

 

Organisation Culture

  1. No dedicated security role with responsibilities either in the IT or other risk/compliance departments
  2. Information security is addressed within the organisation with at least employee responsible for it
  3. A CISO exists and sets security strategy for the organisation
  4. Information security is implemented throughout customer facing, operations, and support functions
  5. Suppliers and subcontractors are assessed to ensure they fulfil security assurances

Technology and Controls

  1. Standard network security tools are used (main objective = preventing network breaches)
  2. Standard network security tools are used to gain visibility of which data assets are being secured (main objective = detecting threats)
  3. Security processes are semi-automated to defend against threats; Static “normal” network behaviour and context are created to understand the status of risk profiles at a single point in time
  4. Advanced tools are used to anticipate and prepare for unknown threats
  5. The majority of security processes are automated; Leveraging threat intelligence is a business objective; Adaptive network behaviour and context are created to understand the real-time status of risk profiles

Security Operations

  1. Security practices are implemented without formal guidelines
  2. Security practices are embedded in formal guidelines to be used by IT and information security teams Guidelines and security processes are established in all IT, customer facing, operations, and support functions; Incident response procedures are defined
  3. Periodic reviews are conducted to fine-tune security operations, and incident response procedures are implemented
  4. Continuous tests of security operations are conducted, including automated incident response and management with technical, customer facing functions, operations, and support staff

People

  1. No dedicated security role with responsibilities either in the IT or other risk/compliance departments
  2. Information security is addressed within the organisation with at least employee responsible for it IT and information security teams are aware of AND carry out security practices as defined by formal guidelines; Training is received to ensure both teams are kept up to date
  3. Technical, customer facing functions, operations, and support staff receive training and education to keep up to date on information security risks
  4. Technical, customer facing functions, operations, and support staff regularly participate in incident response activities

 

Cloud Adoption

  1. No organisation-wide cloud strategy
  2. Cloud infrastructure is fully automated Cloud strategy set by IT and business units (but without security inputs) to re-set business processes to achieve desired outcomes
  3. Cloud strategy set by IT, business units and security Have optimised internal processes as a result of cloud and automated controls are enabled to allow for distributed clouds

 

 

 

 

 

ReactNative vs. Apache Cordova

ReactNative vs. Apache Cordova

Many of you may already be familiar with Apache Cordova as an open-source project that enables web developers to build mobile apps with full access to native APIs and offline support. In a Cordova app, the entire UI executes inside a full-screen WebView where you can leverage the same HTML, CSS and JS frameworks found on the web. But, since the UI is rendered in the WebView, it can be difficult if not impossible to achieve a truly native look and feel.

ReactNative apps are also written with JavaScript – or, more specifically, they are written with the React/JSX framework. But, rather than run in a Webview like Cordova, code runs in a JavaScript engine that’s bundled with the app. ReactNative then invokes native UI components (e.g. UITabBar on iOS and Drawer on Android) via JavaScript. This means that you can create native experiences that aren’t possible with Cordova.

That said, Apache Cordova is presently a more mature and stable technology that lets you write a common UI layer using web technologies, whereas ReactNative is much newer and still requires you to write distinct UI layers. If your app requires native UI and you enjoy the excitement of a rapidly evolving JavaScript platform, then ReactNative might be an option to consider.