The document summarizes a program for a Xamarin conference that included sessions on Xamarin Forms updates, mobile search using Google App Indexing, and mobile security. Key highlights from backstage conversations with Xamarin engineers indicated that the Xamarin Forms team primarily works with C# instead of XAML, and that Microsoft plans to move more of their mobile technologies to use Xamarin.
2. Program
18:00 Reception & Dinner
19:00 Evolve Highlights & Backstage Info from Xamarin Engineers
19:10 Mobile Search with Google App Indexing in Xamarin Forms
19:45 Coffee Break
20:00 Mobile Security
20:15 Insights Mobile Application Management
20:45 Drinks & Talks
4. Highlights
• All Xamarin SDK’s Open Sourced… including Forms
http://open.xamarin.com/
• Previews
o Visual Studio & iOS: Simulator remoting, USB remoting
o Native HTTP Handlers for speedier network operations with HttpClient
o Workbooks for REPL and training with seamless Markdown and code
• Xamarin Forms
o DataPages : automatic UI from JSON design data or cloud API’s
o Previewer for XAML
o URL Navigation
o Embedded Platform-Specific Controls
• DevOps
o Test Cloud Live: debug an issue on a specific real device in Test Cloud
https://blog.xamarin.com/xamarin-evolve-2016-recap/
5. Backstage info
Jason Smith, Lead Engineer for the Xamarin Forms team responding to a question during a presentation:
“DataPages are an just early app prototyping tool, before you publish an app you will change to viewmodels etc.”
Later I met Jason in the hallway…
Me: “If you prefer C# for Forms UI to XAML like I do, is the Xamarin Forms Previewer for XAML a reason to reconsider?”
Jason: “No. I’m on the C# side to. In the Xamarin Forms team, only one guy works on XAML. The others ignore it.”
Me: “But what if I want REPL for C# UI in Forms?”
Jason: “Because we require XAML precompilation, the Previewer will have to support compiling C# as well. So that is coming.”
Me:
I met a Xamarin engineer from the first days at the lunch table…
Me: “How will the Xamarin team and the Microsoft teams move forward? Will they move Xamarin Forms towards Universal Apps or what?”
Engineer: “Microsoft will actually be moving their mobile things over to Xamarin”
Me:
7. Why Google Does It
Mission: collect and organize the world’s data
But…. they were missing all app-only data
Two categories of search result rankings from App data:
App Packs and App Deep Links
Experimenting with non-parity app indexing solution (no web, app only)
http://searchengineland.com/app-indexing-new-frontier-seo-google-search-deep-linking-226517
8. Why You Should Do It
The average person only uses 26% of their apps daily,
while one in four apps are never used at all. App
Indexing helps you re-engage your existing app users
through Google Search, for both Android and iOS.
New competition – threat and opportunity:
• For web: app search results… lots from your app!
• For apps: autocompletion and now on tap lures
users to other apps …. yours!
https://developers.google.com/app-indexing/
31. PART II
The presentation slides for:
Mobile Security
Insights Mobile Application Management
are available at:
http://www.slideshare.net/AlbertoAguzzi/mobile-security-dutch-mobile-net-
developers
App Packs are much more like the app search results that SEOs are used to, because they link to app download pages in Google Play or the App Store, depending on the device that you are searching from. (App Packs will only show apps that are compatible with your device’s OS.)
Ranking in an App Pack (and also in the Apps Universal, under Google’s top-navigation drop-down in the mobile search results) relies heavily on the app title, description, star ratings and reviews, and it will differ greatly from the internal app store rankings, as well as in-app indexing strategies described in the rest of this article.
Deep links are different because they link to specific deep screens within an app. Google has displayed deep links in search results in a variety of ways since it started app indexing
Note: If you have an app without corresponding web-page content, and you'd like it discovered by Google Search, fill out our app-only interest form. This is currently being tested with a few developers.
Finish your users' sentences
With your Android app indexed, Google Search surfaces your content in autocompletions. This means that when a user starts typing a query that can be answered by your app, Google puts your content and services front and center.
Find users from any screen
Now on Tap suggests related content and services for anything on-screen with a simple long-hold of the home button. When you implement App Indexing, your app can be displayed as a destination in Now on Tap.
If you do not have access to the web site in Google Webmaster tools, you can use the Google Play Developer Console for your app https://play.google.com/apps/publish
Click Verify website -> emails to webmaster: does this guy also own the web site because they are going to make an app for it.
They can say yes and you get access.
When you have access to the Google Webmaster Tools for the site register the android app identifier that will be in the play store.
Then associate one or more websites with the app you just identified
Ok but how do you test indexing before you publish your app?
In Google Webmaster tools: in “Fetch as Google” upload APK before publishing in android store.
It will show all indexed deeplinks and you can preview what each link will look like in your app – in your browser!
Stored in Entitlements.plist file in iOS project
In Apple Developer Portal: enable associated domains and download your provisioning profiles because they are now modified.
Fiddler: GET https://evolve.xamarin.com/apple-app-site-association
Details: see https://developer.apple.com/library/ios/documentation/General/Conceptual/AppSearch/UniversalLinks.html
In order to avoid adding a dependency on GooglePlayServices to the Xamarin.Forms core package, we've created a new Xamarin.Forms.AppLinks nuget package that will be required for this feature to work on the Android platform.
In IOS all is built into the OS (starting from version ?)
NB Install only is enough – intent is known even when app was never started
Thumbnail can be dynamic content e.g. someone’s profile photo or a product image.
Can come in from:
Web
Spotlight Search
Google Indexing
During the session James open sourced the evolve ap that uses this. 15000 lines of code. So…