So, I and a few other people are working a project where one part of the group is doing an Progressive Web App and the other part is doing an iOS app. Our back-end API is in .NET Core C#. We have decided to use SignalR so we can make the apps real-time.
I have done a small research on SignalR and there is not much available information on how to use it with Swift. Could any of you give any recommendations/suggestions on how should I proceed and how I can combine Swift and SignalR?
Related
I want to know basic difference between Cascades, Core and WebWorks apps. Can WebWorks-based apps interact with device apps? Or they can simply run on web end? Please somebody clear it for me.
Thanks in advance.
I'm no expert, but in short
WebWorks - it is web based, but you can use some core APIs. Take a look here. I'm not sure, but if I remember correctly you can even write your own libraries in core, to access more
Cascades - it's front-end (QML part) and back-end (QT). It has a lot more access to core then WebWorks. Very simple to make good looking apps, and good functionality
Core - I think it's mostly used for games, and app ports, but has big access to system functions.
I need to build a mobile app which should run on both iOs and android.I'm not interested to make my app as native app rather a hybrid one(my app may/maynot includes native code of iOs & android in few areas).Please help me on these queries.
which one should be the best technology to initiate my project.
Can I use MVP pattern in GWTMobile?
Which one requires less developing cost(factors: time,manpower) and less developing overhead(factor:less boilerplate code).
Which one have great look and feel in their widgets.
my app requires some of the features of phoneGap too, which one is gives great support to GWTPhoneGap. I'm prefering GWT-RPC for server communication and HTML5-Database support for local storage and offline service. Please give me answer with explanation to each point. Thanks in advance
don't know
in mgwt: yes
features requires cost. Both are more or less widget and framework components. I don' think they wil be really different.
compare them: http://mobilegwt.appspot.com/showcase/ http://demo.gwtmobile.com/
gwt-rpc isa bad idea for phonegap apps. It will work, but you must ensure, that clientcode (packaged inside the app) and the server must be in the exact same version, because of th serialization-policies.
I am planning to create a cross-platform mobile app that has native-like versions for most mobile platforms, maybe Windows Phone, Android, iOS. It's supposed to store data in DB on server, and the mobile app is mostly for visualizing that (numerical) data.
Basic usage scenario
User opens the app
App data is refreshed via internet connection
User inputs new data
New data is sent to server, handled and DB updated
User's app data is updated according to DB data (ANIMATION!)
User updates settings on his app that alters it's behaviour.
I'm a noob when it comes to designing and programming mobile apps + web services alone, so I'm hoping you could help me with the following questions. Technologies I'm most familiar with: Java EE, Python, HTML/CSS/JS, MySQL, Graphics. Maybe I should go for PhoneGap? Thanks a lot!
1) What cross-platform mobile technology you would recommend?
2) What kind of solution would be most suitable for server/app server? (Estimated code lines < 5000)
3) What's a good place to start learning scoring algorithms?
Please respond if you have answers to any of the questions asked.
EDIT: found a similar question: Cross-Platform Mobile Application Solution
#thevangelist: It's a very good question you have raised, all mobile developers face the same problem when we start writing an app. Today there are multiple Open Source Frameworks available in market which are trying to solve the same problem but in different manner.
Based on my research and experience, I would like to recommend below technologies which we can consider while building an mobile apps.
View: View is an important part of any mobile apps. When we start building UI/UX we also have consider it's platform design principles. Looking these points I would like to recommend React Native for the same.
React Native: It is a Facebook, and Instagram developed JavaScript library used in creating native mobile applications. It allows us to write iOS and Android applications using JSX, a known HTML look-a-like code, and JavaScript. It is based on “Learn once, write anywhere” methodology.
Pros
Renders native views with a native behavior and interaction … you’ll end up with a real native application
Has a paradigm of “Learn once, write anywhere” where developers only need React and JavaScript to create better application for Andoroid, iOS.
Uses native architecture and concept
It does not require a WebView
CSS Flexbox is used for layout design
Cons
Code abstraction leads to bugs and memory leaks
Cannot work without the API, which is provided by React Native, technically there’s no fallback like with classic hybrid mobile apps
When creating proper native applications, a developer will have more power and control regarding performance tuning
React Native is still a new framework so we can’t predict possible problems and downsides
These cons are somewhat negligible, especially if we consider that React Native is empowering more and more native applications with each passing day.
Data in Transit: If your app sync data from web services, then there are multiple frameworks available in the market to make our job easier. Please find below some of the most popular JavaScript RESTful Frameworks:
ACTIONHERO, StrongLoop
Data at Rest: You would also be needing offline storage for the sync data. Since we do not have direct support for native SQLite in JavaScript, we need to use some of the React Native SQLite Plugins. Please find below plugins which are available in the market:
almost, andpor, jbrodriguez, ramsundark5, remobile
For Data at Transit/Data at Rest, I would like to recommend Siminov Framework which is available on all the major platforms (Android, iOS, Windows). It also supports hybrid technologies such as React Native, Cordova, Xamarin.
Pros
Available on all the major platforms (Android, iOS and Windows)
Easy to configure, it provides standard xml based structure using we can easily configure our app database
It allows developers to bind ORM with remote RESTFul web services too
Also have support for SQLCipher on all the platforms
Cons
Lack of community: Recently they have launched their products on all the major platforms, not many people are using it.
Since the configuration is based on XML structure which looks pretty old to me. But based on their documentation it was done to support all the major platforms
Algorithm: I have found this link nurlybayevaAMS9 related to algorithm, hope this may help you.
Try avoid writing cross platform application. It is doable using HTML5+jQuery. But you can never get the same look and feel as native app. secondly windows, ios and android have their own look and feel and will come up with their own elements. You can never cater to all three having same code base. Better is to code using native sdks.
1) Never used PhoneGap, although aware of it, but don't forget to consider a simple HTML5 application. If possible, this would save you lots of work and maximize compatibility.
2) You can develop great RESTful webservices with both Java EE (see JAX-RS/Spring) and Python (see django). The choice is really more a matter of personal taste.
I'm about to develop an app for iPhone, Android, and for web too. I think there must be some "standard" way for doing this, in order to reuse as much code as possible.
Which is the best way for doing that? Webservices? (only if the app uses internet) Maybe an API? Another way?
Just for the record, the web application will probably be developed in Ruby On Rails 3.
Thanks!
There are a few cross platform development tools out there that let you write once and compile for multiple platforms. I know I've seen questions on both tool here on SO, so others might have some good advice on these specific products.
PhoneGap
http://www.phonegap.com/
Appcelerator
http://www.appcelerator.com/
Barring that, if you are looking at doing native development on each platform, the web services APIs are a good way to go. I've built an App that is heavily data driven, and I built out RESTful services over JSON that do the heavy lifting for the iPhone, Android and Web versions.
There still is quite a bit of work that goes into implementing a feature on each platform, but once I architect code on one platform the hard, creative work is done and it's just porting it to the next platform (Same applies, mostly, to the graphics as well). Since I am coding for each platform individually I do try to take advantage of both code and UI conventions for that platform to give the user a native experience (say building menus for the menu button on Android, something not supported on iPhone). To me that's a benefit of developing for each platform individually, however, it also greatly increases time to market for each version.
Since you're looking at Objective-C, Java and Ruby, 3 completely different languages, there's not an easy way to develop a shared library without using a intermediary layer like those linked above.
Well, all three are different languages, so anything you write for one won't work for the other. An API on a server may be able to get you the same data to all, but its highly unlikely that you'll get any reusable code. I'm doing the same thing, and realize that, so I am just sharing common things such as UI and code-design between them.
I've been digging around for this one. I understand that there two possible ways to develop for the iPhone.
via web kit frameworks, such as jqtouch and iwebkit, and
using the iPhone's api
I notice quite a few people using web kit frameworks, especially jqtouch. What are the benefits of using a webkit framework versus using the iPhone's api directly?
One point that springs into mind, is the fact that using a web kit framework makes it accessible through other smart phones? Not just the iPhone?
Are there any differences in terms of graphic enhancements? i.e. will transitions or animation look different?
I am a web developer by heart. It will be an advantage if I can develop an iPhone app with knowledge that I already know, that being the Ruby on Rails web framework.
I have also read this slideshow, which seems pretty detailed on various web kits.
Your suggestions / feedback is appreciated.
Just came across the following by Oreilly which seems to answer a good detail of differences between a native and web app development for the iPhone.