I have noticed some difference in the google maps simulator and on-device rendering of googlemaps. Going through the beatiful featured apps like Travel2gether and Paltel app, are the maps used in this apps native because I noticed they come with the + - sign and they even show more places mapped wheres on the normal GoogleMapComponent those places don't show.
Any clarifications for this?
Regards
Paltel uses native maps which you can install via the extensions menu.
You can read about using it here.
Travel2gether uses the old maps with the Google provider instead of open street maps.
Each has its advantages/limits but we are slowly gravitating towards the native maps approach which is probably a better choice.
Related
Has anyone tried using Dash to make a mobile app?
I found it very useful to browse the Dash page on my phone, but I don’t want to enter Urls and log in every time.
And if it’s a mobile app, whether embedded or native, there are more features that can be implemented.
From my experience with dash, its not a current feature unfortunately.
To clarify plotly and dash have two different types of interaction. The vanilla plotly graphing library allows you to hover, zoom, pan,..etc. Dash is more about complete interaction between multiple graphs.
Dash is a web app framework, so it can't be a native app as the interaction capabilities come from the web app functionality. People have built hybrid apps using dash but the requests still go through your own dedicated dash app, which is hosted through the web browser. So in my perspective you're just doing redundant work that is done by plotly. That being said dash code can be made mobile friendly so (in my humble opinion) that would be a better route. But from colleagues that have explored this route, the click, hover, select events that are what makes dash so appealing, do not work very well without the precision of a mouse cursor.
Last point, if the vanilla plotly interaction is the only degree of interaction needed then those graphs can be embedded into a native app because they are offline.
It could be done, though perhaps there not an out-of-the-box solution for that purpose. But Plotly Dash is built with ReactJS, of which the "mobile version" is React Native.
ReactJS vs React Nativeenter link description here.
Having said that, consider not using a mobile application that you have to actually download (i.e. an APK) but instead a web app suitable for mobile devices. Compare it to having the Twitter app installed vs opening Twitter.com on your device. It "feels almost the same", and you don't have to download anything.
I recommend reading about Progressive Web Apps.
Example of PWA.
has anyone worked with react and sharepoint, please tell me, if there any reference for creating a react app and deploy in sharepoint online directly, many of the references are creating react app as web part, but I cant find what I looking for. please help
It actually depends on where you want your application to show up in the SharePoint.
In addition to the WebParts, there is AppCustomizer option that allows you to show your app in one dedicated the placeholder of the sharepoint site (top or bottom):
https://learn.microsoft.com/en-us/sharepoint/dev/spfx/extensions/get-started/using-page-placeholder-with-extensions
Other that, there is "single page part" option that allows you app to occupy all the space on the page, and to be the only thing the user gets basically:
https://learn.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/single-part-app-pages?tabs=pnpposh
I am new to React Native. So here goes my scenario:
We need to create a new SDK that would be embedded into multiple technologies: React Web (JS), React Native APPs, iOS Apps (Swift and Obj-c), and Android Apps (Kotlin and Java). This SDK will offer:
APIs to get access tokens (issued by our corporate authenticator) so that the APP can talk to our API Gateway; something on the lines of getCurrentAccessToken();
Standard screens for login, Change Password, Forgot Password, OTP, etc; The UI should look and feel NATIVE to each target platform that it will be running on (Web, iOS, Android). Transitioning from a Native Screen to SDK's Screen should be smooth.
Be small (package size) and have OK/Hermes performance on both API Calls and Screen loading times (it doesn't need to be as fast as Native, as this SDK will be used once or twice every time the user starts the main APP);
I have checked boden.io (C++) but it would not work on WEB. It might still be an option (having 2 SDKs, one for WEB one for Mobile) so I didn't rule it out yet.
Is such a thing feasible in React Native? If feasible, is it a good idea?
PS: I know I would still need native binds/wrappers for each technology so that the SDK looks NATIVE to the caller, but that would be a minor issue.
Thanks
You can use go lang and gomobile to build the sdk for iOS, Android and Web.
Hi I am new to programming so please bear with me.
Basically, I want to create a map for Android devices that load markers and navigate from point A to B while avoiding the markers. It is ok if the path is not the shortest.
I have tried loading markers from geojson file using both google map and mapbox with no problems. Now, what can I do to customize navigation within the app itself? Thanks in advance.
Unfortunately, it does not appear that this feature has direct support from the API. Please see these answers for alternate suggestions:
Google API (directions) - creating routes that avoid certain points
Blacklisting specific roads from Google Maps/Mapquest?
I'm excited to learn Sencha Touch and improve my HTML5, CSS3, and JS skills in order to eventually program for all mobile platforms instead of focusing on one-off languages. But I'm having trouble getting started.
Here's my question:
What is actually the bare minimum required for an application?
Here's why I'm confused:
I started with the Hello World demo where they use new Ext.Application()
Then I looked at Getting Started with Sencha Touch where they use Ext.setup()
Then I look at the Intro to Panels screencast where Drew Neil didn't use either!
Why do there seem to be so many different ways to start building a Sencha Touch app? How should I start my apps?
Thanks for setting me straight in advance,
-- Miles
Ext.setup() is the minimum, I think. It merely creates a page for a mobile device.
In the Intro to Panels (or at least the version at http://vimeo.com/15879797), you can see Ext.setup() at 0:54 (?)
new Ext.Application() and Ext.regApplication(config) do what Ext.setup() does, but also create an Application object, which is required to take advantage of various utility methods and things Sencha has created.
From the API docs: "Sencha Applications provide in-app deep linking and history support, allowing your users both to use the back button inside your application and to refresh the page and come back to the same screen even after navigating. In-app history support relies on the Routing engine, which maps urls to controller/action pairs."
Creating an application also automatically registers a new namespace:
//this code is run internally automatically when creating the app
Ext.ns('MyApp', 'MyApp.views', 'MyApp.stores', 'MyApp.models', 'MyApp.controllers');