How to AutoComplete an Address and get Lat/Long of that address in #flutter? - autocomplete

How to AutoComplete an Address and get Lat/Long of that address in #flutter?

This is nothing you can do directly with flutter. You need to call an API for that service. In a recent project I used HERE Autocomplete and HERE Geocoder for such a service, which worked quite well.
In Flutter you just need to work with the responses of those APIs. In my case the FutureBuilder was the perfect solution (there is even an example in the docs which is a good starting point).

You have to make HTTP Networking Requests in Flutter to the Place Autocomplete service that is part of the Places API Web Service.

Related

Visual REST API playground

What are some web apps that allow me to play with any REST APIs visually (by clicking) and also get some code generated (in any language) that captures what I have described visually?
Similar to Swagger or Google API Playground but allows me to talk to anything that speaks REST (assuming I have the proper auth credentials and I know what messages it understands).
Bonus points for something that can also "discover" what messages are understood, given a URL endpoint.
Microsoft has 2 that I know of
OData API explorer
The data market service explorer (requires signing in, and then you can access free data sets)
Considering that REST API's are going to follow their own conventions, terms, and have their own documentation (hopefully), this is an impossible problem. If you restrict your quest to visualizing API's that follow a "standard" form of self-documentation (see REST web service WSDL? for some hopeful scenarios) you might be able to accomplish this.
Or you can use something like http://www.programmableweb.com/ to discover tutorials, tools, examples, and mashups of various existing APIs.
You could mock an API at http://apiary.io/.
You could explore and existing one through tools (e.g. REST Console for Chrome)
What you can't have, is one-size-fits-all explorer for "every possible REST API." Some APIs follow conventions that others don't.
apigee and apihub (now part of mulesoft) are two that I frequently visit. Of the two, apigee is my preferred provider.
One of the reasons that you're not going to see a lot of websites like this is because of the same-origin policy. This means that you can't access a RESTful API located at api.google.com from a web app running at, say, www.restfiddle.com without sending all the API traffic through restfiddle.com's servers. Sites like JSFiddle can exist (and are used widely) because all the processing is done on the client side.
Browser plugins, however, are exempt from the same-origin policy. If you're using Chrome, try Postman. If your REST client doesn't need to be web-based, check out SoapUI. IntelliJ IDEA has a nice REST client as well.
Try Restlet Studio, it's the only visual API designer I've found, and seems pretty good, it imports and exports swagger & RAML.
http://studio.restlet.com/

practice web service calling from iPhone without having web service?

I want to practice Web Service Calling (both SOAP and REST) for iPhone App Development. Problem is i don't have any Web Service implemented for practicing the same.
Any mock URLs (web service) for learning? At which I can have response of all types (like strings, PDFs, images, etc).
I have only basic idea of Web Service Calling from iPhone App. So, purpose is to get good understanding of WebService calling.
I have Mac and Internet, only. Nothing else.
I know this isn't the right place to ask but I could find any help by googling it.
You can get some free opensource web services on the web for your practice. Urls for free webservices are mentioned below.
Note: I am not sure if any of these will give you PDF / IMAGE as an output response of the service.
http://free-web-services.com/
http://www.webservicex.net/ws/wscatlist.aspx
It might be helpfull
Go through the step-by-step tutorial from the below link:
http://www.devx.com/wireless/Article/43209
Create an app which uses the web service at the following link: http://www.webservicex.net/WeatherForecast.asmx?WSDL, to give the weather of a US city name entered by the user. Use the method "GetWeatherByPlaceName"

For a Single Page Application: ExpressJS or Restify or both?

I'm working with NodeJS + Mongoose, writing a Single Page Application, so I need to serve some statics and then all the interaction between frontend and backend is done via XHR. Eventually I'm thinking about writing a native mobile app accessing the same backend. Is there any pattern / best practice I should apply here?, I thought that I may need to extract the API to be exposed via Restify, and handle the requests from the webapp only with ExpressJS? or should I just put all the stuff exposed via Restify? I guess my confusion comes from not being worked with Restify before, so any explanation about how is it different from ExpressJS (specially when talking about a Single Page App) is really welcome.
I am implementing a similar solution, mobile app & website with expressjs and backbonejs. I did not use restify because i did not think i needed the extra complexity, there were not that many API endpoints so expressjs handled everything ok for me.
BTW take a look at this post on restify performance, I just saw it today and have not personally validate the contents.
Benchmarking APIs using PerfectAPI vs Express.js vs Restify.js « « PerfectAPI Blog PerfectAPI Blog http://bit.ly/xrTguB
Restify is packaging DTrace and various handlers that Express doesn't. If you just have one API endpoint and don't need DTrace, it doesn't make sense to run Restify.
Also, you might want to try express-resource

Converting SOAP to REST?

I have a web app, that also has an iPhone and Android app using the same API. It hasn't yet been made publicly available, so I wanted to look to convert from SOAP to REST.
I was only able to find a few tutorials that go into thorough explanations of how to code a REST web service, and of those I only found the MSDN one useful. The problem is I got really confused when they started using URI data types inside the object.
My question is, if you are converting SOAP to REST, do you have to recreate all the objects to add the URI? Am I not able to just have a REST entry point, then call one of the classes that retrieve the data?
Once the REST service is made it will only be used by my mobile apps, but not the website (since that can directly access the classes), which makes me not want to change the objects to add a URI. Is that a correct assumption to make, or should the web services also be called by the website?
Sorry if these are newbie questions, but I am struggling to get my head around REST, and I haven't had much experience creating the architecture of potentially high user base apps.
If anyone is able to point me to an actual code set, that would be helpful.
Edit: I am using VS2010, coding in C# and .Net 4.
Thanks a lot,
Andy
Im doing a very similar thing right now :). Rest via wcf isnt too hard, you do have to sometimes add your endpoints in the web config and give it the [webget]/[webinvoce] attributes in the refrence.cs of the web refrence when consuming though c# which is annoying.
Here is a code set i used when getting started. There are a few more on code project too.

Mini server implementation in Objective C

I'm trying to implement a little server service in order to upload files via web browser to my iOS app. An example of this feature is implemented in the following app:
http://itunes.apple.com/uy/app/files-document-reader/id294150896?mt=8
seems to be very simple, but don't know where to start.
I've been also looking for clues or some sample codes about this kind of implementation with no success, but maybe just don't know how to google the problem correctly.
Any clues, guides, links, etc...?
Thanks in advance
Here is a wrapper to embed the moongoose http server in your iphone application. Another simple http server is here. The latter one is the one I used in my application, recently.
EDIT:
There's at least a third one, too.