I'm developing an app using Flutter, which is a great cross platform tool, but I wonder if anyone has experience about consuming JMS services in Flutter? I didn't manage to find any related documentation so far.
Best regards!
I don't have any experience with Flutter other than quickly reviewing some of the documentation, but as a developer on the Apache ActiveMQ (message broker) project I can say that in order to support clients which run in mobile and browser environments brokers will typically implement STOMP. Flutter apps are written in Dart and a quick search on the Dart package website reveals a number of STOMP clients. I recommend you go with one of those.
Related
I was wondering if it's possible to run Flutter application components (such as building a specific screen) with other web apps. And if there is a good resource to learn how to do this.
We have a GWT web-app that we have been considering upgrading some components to Flutter, but I have not seen much information online on how to implement this.
I can't see documentation of this process online though. I have seen that you can insert Flutter into existing Android/IOS apps but I don't know how compatible this is with GWT.
I'm a beginning programmer that is interested in IBM Bluemix. What is the easiest way to get started with IBM Bluemix?
It really depends on what is your programming experience and your personal preference. For example if you want to begin programming with the classic Object-Oriented paradigm you should try Liberty runtime to familiarize with Java. Instead if you like the scripting languages maybe you could give a try to Python, Ruby or Go runtimes. All of them provide a sample application that you can extend as you want, and have very detailed documentation. Finally you should take a look at IBM Containers, even if probably this is not a very simple topic for a beginner. They are very interesting and powerful, and they make you able to do potentially anything with the platform.
If you are interested in learning more about Bluemix Mobile Services a good place to start would be here:
Creating Mobile Applications Using Bluemix
We cover getting started with multiple environments:
iOS
Android
As well as an introduction to our provided services:
Mobile Client Access
Push Notifications
Cloudant
I would recommend creating a HelloWorld application for the desired environment and then building on from there:
iOS-HelloWorld
Android-HelloWorld
You can get started by viewing application architectures built on IBM Bluemix. The IBM Bluemix Architecture Center provides diagrams, walk throughs and whitepapers on how to build web applications, hybrid data storage, CRM business intelligence, and data analtyics with IoT.
The walk through guides show how to manually build an application based on that architecture. A way to learn what services are available and how to connect them to do useful work. Many of the solutions can also be deployed automatically to quickly get a working application that can be used to experiment with.
Once you have seen several sample applications you will have better knowledge of which services you want to learn more about.
Don't know if it's the 'easiest way'...
There is a course on developerWorks 'Getting Started with IBM Bluemix'.
Those videos can be watched on Youtube as well if you don't want to register.
Node-RED is a GUI flow editor built on node.js, which allows users to get started very quickly on Bluemix.
There is a "boilerplate" for the IoT Foundation service which includes a sample Node-RED flow that can be used with an online simulator if you don't have a sensor device.
https://www.ng.bluemix.net/docs/#starters/IoT/iot500.html#iot500
That boilerplate will set up an IoT service, a Node-RED app and a Cloudant database. Once you deploy you can test with the online sensor simulator and you can also customize the flow your own devices.
There are so many applications, database and services there, I think you can try to create the services and play around, to see what kind of application you like and start the development works for you own.
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 saw the Google Talk Always Idle plugin [http://www.nirmaltv.com/2007/10/29/make-your-gtalk-status-always-idle/ ] and got interested in the possibility of developing similar plugins for the gtalk client. Is it possible to develop plugins for gtalk? I have searched extensively and haven't found a thing in this regard. Thanks.
Yes you can create plugins for gtalk. They use the XMPP protocol, and there are several sites on it. You can start here:
http://code.google.com/apis/talk/talk_developers_home.html
I am new to J2ME and what I have now is Netbeans 6.7.1 IDE. Is there any basic guide for developing Mobile applications in Netbeans 6.7.1? Please provide me the links.
Netbeans.org itself has great tutorials for mobile development in Netbeans. And that is what you need:
http://netbeans.org/kb/trails/mobility.html
For examples this is a very good Quick Start for Netbeans J2ME development:
http://netbeans.org/kb/docs/javame/quickstart.html
I think this book best source for J2ME with Netbeans:
Kicking Butt with MIDP and MSA: Creating Great Mobile Applications (The Java Series)
Book Description:
The release of MIDP 2.0 and the introduction of the new Mobile Service Architecture (MSA) are generating momentum for the Java ME platform. As more and more Java-enabled mobile devices become available and more service providers become open to third-party development, the demand for customized applications will grow dramatically. Now, there's a practical, realistic guide to building MIDP 2.0/MSA applications that are robust, responsive, maintainable, and fun.
Long-time Java ME author Jonathan Knudsen offers real solutions for the complex challenges of coding efficiency, application design, and usability in constrained mobile environments. Experienced Java developers will master MIDP 2.0 and MSA programming through clear, carefully designed examples. Downloadable code is available for both NetBeans Mobility Pack and the Sun Java Wireless Toolkit. Kicking Butt with MIDP and MSA's wide-ranging content covers:
Pushing MIDP's limits, and exploiting MSA's full power
Using MIDlets, Forms, commands, core classes, and invocation
Building effective mobile user interfaces
Designing graphics with the Canvas, the Game API, SVG, and 3D
Providing storage and resources: record stores, FileConnection, and PDA PIM
Internationalizing mobile applications
Networking via WMA, Bluetooth, Web services, and SIP
Parsing XML documents
Implementing audio and advanced multimedia
Securing mobile applications with SATSA and the Payment API
Building advanced location-based applications
Designing applications for multiple devices
Creating end-to-end mobile application architectures
Tell what platform you are developing on so that the tools available for you can be given.
Also, you most definitely want an emulator so that can test your applications directly on your computer (Saves time).
Honestly, can't give much more advice than to know java well and to use google + stackoverflow. Those are what I did and ended up developing a commercial app in j2me just fine.