Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.javascript > #81919 > unrolled thread

Cross Dj App Download For Android Phone

Back to article view | Back to comp.lang.javascript

Contents

  Cross Dj App Download For Android Phone Ilia Zable <iliazable@gmail.com> - 2023-12-30 10:45 -0800

#81919 — Cross Dj App Download For Android Phone

This question is specifically related to a recommended architecture and people's previous experiences for cross-platform WP7, iOS, Android apps developed using C#, Monotouch and Monodroid respectively. I have researched previous questions here, here and here. They provide good answers but not quite what I'm looking for. I have also found this excellent question which does go into the cost benefit so there is some overlap.



cross dj app download for android phone

Download https://t.co/83VQHRTDTo 






I have a requirement to develop a cross-platform iPhone/iPad, WP7 and android app for a health & fitness company, which will integrate with their website. The app requires a small amount of local data storage for offline mode and synchronisation with the website when a network is available. I am a Windows (C#/C++) developer through and through and don't really want to go down the route of three Objective C, Java and C# apps, although I will if I have to. I will also be operating as tech lead and farming out some work to a team on this project.


I would like to know if anyone here has experience with cross-platform development using Monotouch, Monodroid and WP7 and to share their experience on application architecture to re-use as much code as possible. The architecture I am considering is as follows:


The authors of MonoCross (ITR Mobility) have created multiple mobile cross platform solutions for a variety of customers and have written two books on the subject one is "iPad in the Enterprise" ( ) and the upcoming "Cross-Platform Mobile Development with C#" ( ).






Based on your comments your requirements are for a cross-mobile platform that will integrate with their existing services, but also work offline. You are specifically interested in C# via Mono, however you have indicated that you are not discounting other approaches.


The situation with the mobile development is very similar to the development at the first half of the 90s. Phone have limited resources as computers had, mobile OSes are making their baby steps, hence the ecosystem is relatively small. They have own philosophy, tools and even languages. And this is a good thing, but leads to a headache for cross-platform development. As a result, there are many attempts to clear this a bit. People build frameworks, wrappers etc. which is a kind of abstraction and abstractions are leaky. This is extremely important for mobile devices not only the performance as numbers of CPU cycles, but also the performance of the battery, which is far more important for the user.


I've read about the native feature-support of Phonegap here. Clearly, it makes no mention of Bluetooth support. I've failed in finding or locating any other platform with cross-mobile platform development support. As a result, I'm currently faced with two choices.


In my experience, this is by far the least painful option, and not just for Bluetooth. The overhead of dealing with leaky cross-platform abstractions tends to outweigh the benefits by the time you get to a real, production product. Build an excellent iPhone app. Build an excellent Android app. You can share a lot of the UI design (though not all of it). You can share much of the data structure design. You can share some of the internal architecture. You can share any network protocols (particularly if you design them in JSON). But avoid code sharing and avoid shooting for the least-common-denominator. It's pretty far down....


You list iOS as one of your desired platform. On iOS, any generic Bluetooth communication (other than Bluetooth LE or communication via Gamekit, headset or keyboard) is available only to Apple MFi program licensees. To get any details about this license, you need to apply to Apple's MFi program first. AFAIK, no 3rd party or cross platform tool chain can help you with this for iOS.


If so, are the peer-to-peer Bluetooth APIs (and hardware) on say, Android or Windows Phone 8 be compatible with the one from iOS? And if they were, shouldn't passing data around by JSON be fairly straight-forward for building cross-mobile apps?


The useage of my PC would be so much easier if there was a way to copy and paste links, notes, scripts, etc to a notepad from my Android (Samsung phone) and open them on my PC with a simple click of an icon.Is there a cross-platform notepad app for Linux/Ubuntu AND Android, please?


So, per your comment, let me make a suggestion a bit more accurate and arbitrary...

If you don't have one already, you can set up a Nextcloud account at one of the Nextcloud providers (you can click on "Change provider" to see the full list).

Synchronize your Nextcloud on both your phone and PC with the Nextcloud clients.

Then on your phone, you can use the Nextcloud Notes app to edit your notes. That will be your direct icon app.

On your computer, you only have to edit text files in the /Notes path. Any text editor can make it. I like QOwnNotes for this purpose (in your case, you would have to tell QOwnNotes to use /Notes as folder path), but Joplin or even Gedit can make the job too.


The Cross device SDK provides a software abstraction layer that handles all aspects of cross-device connectivity, leveraging wireless technologies such as Bluetooth, Wi-Fi, and Ultra-wide band; our SDK does all the heavy-lifting under the hood, offering you a modular,connectivity-agnostic API that supports bi-directional communication between devices and is backward compatible to Android 8. In addition, apps will not have to declare or request Runtime Permissions for any of the underlying connectivity protocols used (such as BLUETOOTH_CONNECT, BLUETOOTH_SCAN, ACCESS_FINE_LOCATION, etc.), and the user can allow apps to connect to only the device(s) they selected.


Cross-device user behavior refers to the way in which a user may engage with a given funnel through two or more different devices at various times throughout the journey. Within the cross-device journey, the same or multiple platforms (mobile web, desktop web, etc.) or channels (social media, email, push notifications, etc.) may be used.


Subsequently, cross-device measurement refers to the process, supported by increasingly more sophisticated attribution technology, of following this fragmented user journey across devices, and uniting the various touchpoints under some form of unique user identification.


Another way of bridging the cross-device gap is via smart banners, or banners at the top of your mobile web screen that drive visitors to browse using the app. These call-to-actions often go hand-in-hand with campaigns offering promotions and deals for in-app users.


You create cross-platform mobile applications from a single codebase. The goal of cross-platform app development is to target different operating systems with one project. You create these apps using cross-platform frameworks, which use platform-specific SDKs (Android SDKs and iOS SDKs) from a unified API. This enables you to easily access the different platform SDKs and libraries.


Cross-platform mobile apps are usually compiled to use native UI elements that make the app feel native. As mentioned earlier, they provide an abstraction to the underlying platform SDKs. The exposed sensors include access to GPS, battery level, camera, and microphone.


To deploy your app on Android, you still need to have Android SDK installed and a Windows, macOS, or Linux machine. For iOS, you still need to have iOS SDK, Xcode, and exclusively a macOS machine. Below is a list of IDEs that support the cross-platform frameworks mentioned previously:


The decision to develop a native or cross-platform app is crucial. There are several scenarios that benefit native over cross-platform apps and vice-versa. Carefully considering your audience, budget, development timeline, performance and security needs, and so on will help in the decision-making process.


Some companies have higher budgets than others to develop mobile apps. For lower budgets, opt for cross-platform apps, as you only need a small team. Cross-platform development also allows you to keep costs in check by reusing your code and projects.


Whether your users are on Android or iOS operating systems, you need to ensure you create your application with security, performance, and scalability in mind. There is no one-size-fits-all solution to developing a mobile application. Neither cross-platform nor native development will be best-suited to every use case. Continually assess the unique needs of each mobile app project to determine if it is better suited for native or cross-platform, and consider the future plans for the application even when you are just getting started.


I have investigated with cross compilation for android and ios. I got things working on android (and probably ios if I can get a copy of XCode) using js_of_ocaml and cordova following instruction here:


unfortunatelly, opam-cross-android and opam-cross-ios seem outdated (see OCaml cross-toolchains and cross-packages  GitHub). Is there somewhere tools and instructions to build application with latest OCaml on multiplateform ?


If, however, you fancy something very experimental I have an outdated repository that compiled an older Multicore OCaml for the x86 iPhone simulator: GitHub - patricoferris/eios: Effects on iOS. This uses the opam-monorepo and dune-workspaces approach to cross-compilation, like Mirage 4 will. The point of this approach was to try out effect handlers for concurrency using the portable eio library with an iOS compatible backend (one that uses Dispatch (GCD) for IO and network.framework).


The name property implementation from AndroidPlatform uses the Android platform code, namely the android.os.Build dependency. This code is written in Kotlin/JVM. If you try to access java.util.Random here, this code will compile.


Create rich native apps using .NET across iOS, Android & Windows. Share code across device platforms with .NET Standard. Share UI with Xamarin.Forms and XAML for maximum code reuse. With 100% of the native APIs exposed, you have full access to device capabilities.


Share, reuse, build, deploy, and debug your cross-platform C++ mobile code. Create projects from templates for Android Native-Activity applications, or create high-performance shared libraries to include in other solutions. You can also bring your existing C++ code to mobile platforms with minimal work. Use platform specific IntelliSense, validate code without building as you type, set breakpoints, watch variables, and deploy the application to devices (ARM, x86) and emulators alike.

 35fe9a5643

[toc] | [standalone]

Back to top | Article view | comp.lang.javascript

csiph-web