About AngularJS performance with large application specifically an ERP application - angularjs

Our team want to choose a technical architecture for our future ERP web application. We have fixed the choice for the back-end layer, actually we'll use Spring Data JPA/Hibernate and CXF web service to develop the service layer.
Right now we're a little confused about the font-end framework to use so as to develop the client layer. Can anyone give me his viewpoint about AngularsJS framework, is it possible use it to develop all the front-end layer including soap and rest web service calls? Will it fit with our ERP application? I mean from a performance standpoint? because there is a lot of data that will be saved in the client side? Working with Javascript in the client layer? Doesn't it slow down the treatment inside the application?

Hey we are developing a hybrid application for data logistics which is connected through webservices and a Database with the ERP System.
We are using angularJs / Ionic Framework / Cordova
For saving data on the ClientSide we decided to use Localstorage / our own setter/getter Service and WebSql since we are doing offline Functionality too.
Our app is growing big and we have no Performance issues what so ever currently we have about 80 different views.
Hope this helps you

Related

Where do I keep the application logic in an offline-first web app?

I'm trying to build an offline first web application using couchdb and pouchdb as the backend/frontend databases, AngularJS as the frontend framework and expressjs/nodejs as the backend server. The problem is that what I'm used to is the backend-MVC mindset of building web apps, and not to SPAs, offline-first design, or having only json apis on the application server.
The problem I see with the design I'm considering is that I don't see any role of the nodejs server except serving static files. The frontend would get data from the pouchdb database which would sync with the couchdb database backend. I need an offline-first application capable of working locally when there's no connectivity and syncing when connectivity is available, so this is important.
But where do I implement the important bits of application logic that I need in the backend, like form input validation or user access control? I found some ways to embed logic in couchdb databases (like using filters as shown here) but somehow writing application logic in the database doesn't feel right.
What part of the big picture am I missing here?

IndexedDB vs SQlite for HTML5 Cordova Hybrid Mobile Application

We are developing a hybrid mobile(ios/android) app(AngularJS,HTML5,Ionic) for an already existing cloud-based CRM. We want to have extensive offline data management capabilities which might include storing of large amount of data locally on the app itself. Also there will be periodic as well as on-demand syncing of data from the server to keep the local data up-to-date. My question is what kind of storage framework should be used at the mobile client side in this situation. Thanks in advance!

Synchronise a mobile light database with ASP.NET Web API 2

I am building a mobile application targeting iOS, Android and WP with Ionic/Cordova. And using ASP.NET Web API 2 REST APIs backend.
I have the requirement that the mobile application can collect data and synchronise it with the APIs and if the mobile is offline, the sync will happen when it is online. The data size is small and any light DB would do including the localStorage one. The required sync is only needed one way, mobile to APIs. Also, once a record is synchronised, it can be deleted from the mobile.
I was looking at Couchbase mobile, but I found it is a Mobile DB to DB sort of a solution.
Can you recommend a mobile DB to REST/Web API sync solution?
With the native Couchbase Mobile solution for Android/iOS coupled with the REST APIs you are able to get data from Mobile device to your backend. Then delete any documents off your device once you get back a 200 status.
For Windows Phone, you can explore using PouchDB or going with the javascript browser based solution across all platforms since WP is not currently supported.
For the replication or sync to occur when your device is online again, you would require your backend to use Couchbase Server and implement the replication class methods in your native mobile app to have the push feature. Or you can use the REST API with logic detection when you are online again to POST to your backend.

use existing spring, spring security, JPA backend in mobile application

I have one project (Web) in which I am using
HTML,JSTL,JS .., JAVA, spring MVC, spring security, JPA and mySQL
Everything is working fine in this project.
Now my client is asking to create a mobile application (Android and IOS) for this project.
My question is:
What approach I should choose to use the same back end in my mobile application with minimal changes.
I do not want to write all the stuff again for back end.
Can some one share any example as well. (may be a small demo or so).
Its better you take advantage of web services here. RESTful webservices come with many handy features to address this issue saving us from re-writing the whole code for mobile applications.
We work for an eCommerce client, our mobile apps access the back end through apis which is primarily written in Oracle ATG Commerce. By this approach back end is completely decoupled from front end and this facilitates the view technology (web or mobile) to be independent. Our APIs are hosted on cloud container APIGEE. Soon, we are planning to dump the old jsp views in favor of Mustache templates to support responsive websites(unique view across all the devices).
Refer this page Restful API for Mobility Solutions. It might give you a peripheral idea.

What is the best backend for a jquery mobile web app?

i want to know what is the best backend (database) for a jquery mobile web app and if you have any tutorials and tips that i could use? What is the best database to support a jquery mobile web app?
Thanks
Backends for mobile apps is a completely different concept altogether when it comes to the context of market. There's a new revolution of mBaaS providers - mobile Backend as a Service. Instead of having your own backend, writing your own web services and exposing them to your app, I would suggest trying a mBaaS, unless the situation is demanding to go by the traditional ways.

Resources