I'm implementing a cleaner app, and one of its utilities is to keep tracking of applications' - which are installed by App Store - updates. That's fine. But I want to update the apps programmatically without interference from App Store.
Unfortunately I can't find any API to macOS App Store concerning this.
P.S: This is actually implemented in a famous cleaner app. If you would say this is not feasible.
Related
We have a website, and a react-native based iOS and Android apps that present that website in a mobile app (with push notifications). If we have the website send the messages through a single G- measurement id, in GA dashboard it shows web as the platform 100% of the time. Is the best way to manage the platform value to create multiple streams? We have different apps for different audiences, so it would be hard to maintain that many new multiple streams for each app. Is there a way to populate Platform in a different way?
I see when we are in the app, the browser value is like Safari (in-app) or Android Webview. But that doesn't tell us app or if the website is in a social media app. I am thinking the best way to proceed is to make a custom dimension for knowing if the user is inside the app. Is that the best way forward for us?
I'm currently starting a project on shopify to make an app and I've noticed that they have released Shopify App Bridge but also I have the option to select Embed in shopify when the app is created. Is this one in the same or two different ways to display the app in the users store? If so what are the main differences to help eme select which to use?
App Bridge is a replacement to the EASDK. It's the future of Shopify App development. You would use App Bridge to develop your embedded apps instead of EASDK and your existing EASDK apps now use App Bridge under the hood. EASDK will eventually be deprecated but for the foreseeable future will still work as it always has. I encourage you to give App Bridge a try.
Full disclosure, I work on the App Bridge team at Shopify.
I thinking about real technical advantages of creating React Native app over web SPA. I figured out that only 1 advantage could be - it's saving and loading data in phone store. Another things like, for example, access to GPS, camera, etc are also available in JavaScript Web. So, that is real technical advantage of using React Native over Web?
Overall, it really depends on what your application is for...
If your Application will be used by mobile users only, then React Native is a perfect solution. However, if you want an application with a Web presence, so users can use it on Desktops etc - then it wouldn't really be suitable unless you did both a Web SPA and a mobile app.
For example, if I were to create an accounting app - which will be used by users on Mobiles and Desktop, then perhaps I'd consider building a SPA which is mobile friendly or both SPA and an App with an API for both.
If you were building a tracking app, which will only be available for mobile - then go for it.
If your users will be using desktop, then you can build it perhaps in React and when you get to React Native you know the react library!
React Native in itself builds both iOS and Android Apps, so instead of creating a 'hybrid' app (which includes webviews) or a native App in both iOS and Android - you only create one code base and build it to your chosen OS. This saves alot of development time. As the community is open source, alot of upgrades happen and there is alot of help online if you encounter an issue.
I am at the moment researching about the new features of progressive web apps and they are pretty amazing and allow building web apps which are feeling very native. In particular, I'm considering at the moment to build a purely web based, installable calling app. Most features for something like that exist already:
Audio and video calls are very simple to do with WebRTC.
Using service workers and the push API, it is possible to send push notifications to a web app which is not even opened currently: https://developer.mozilla.org/de/docs/Web/API/Push_API
Web apps are becoming installable and can add themselves to your home screen: https://developer.mozilla.org/en-US/Apps/Progressive/Installable
Nevertheless, for building a serious calling app working on a mobile phone, it is necessary to be able to unlock/wakeup the screen of the phone in case of an incoming call. I unfortunately couldn't find anything out about a possibility for doing that; even not with features which are at the moment still considered as "experimental". Does anybody know if it is possible to do that at the moment, just using web technologies? And if not, if in the near future there are plans in browser technologies to allow something like that?
In my opinion, this is something which should be possible (at least in the future), since this would enable developers to build progressive web apps which are having more features and are even closer to native apps.
Currently there is no API that fit your requirement, the best thing you can do is to send notification continuously when someone call you (which I have seen in many other apps).
The most recently feature a web page can do when the phone is sleeping is to play background music or control the volume (MediaSession). But that is only in experiment stage.
I'm not sure allowing a webpage to "wake up" the phone from sleeping state is a good idea. The web move forward but there are things that should be handled by native apps.
I'd like to use branch smart banner because it can open app if it was installed. But i've understood how it work. I need install ios sdk in my app and use setIdentity?
Alex from Branch.io here: the smart banner actually doesn't require the SDK to be integrated. setIdentity is a completely separate method used for tracking individual users, and isn't used at all for the smart banner.
However, integrating the SDK is definitely the easiest way to get things working, because even without it you would still need to set up a Branch account, configure all your link routing rules in the Branch dashboard, and then enable Universal Links in your app (if it's iOS). Since that is 90% of the SDK set up process, you might as well do the whole thing so you can also take advantage of things like install attribution and analytics!