I am trying to creating an android dictionary app. But instead of using a database of words I am trying to leverage on the Google Custom Search API. so when the user of my android native app enters a search word in english. My native android app goes to the web and uses the Google Custom Searhc Api to get the result. But I dont know how to communicate with Google Custom Search API from an android app. Please any link. I have been search but not gotten any use one
https://developers.google.com/custom-search/json-api/v1/using_rest
I believe, this can be a good start for you. You need to use asynctasks to do your request, and the rest is up to your imagination and skills.
Related
Hi I'm developing an application which accesses script.google.com to create google sheet and mail the sheet link to my employees makes them a way to update daily reports from home which I'll fetch using TableTop. But I'm currently stuck on Publish to web option which is a mandatory thing on tabletop. Publish to web is quite easy using a PC(in a computer browser) but I don't know how to do the same in Google Sheets Android app. I'm preferring android app as most of my employees don't have a proper pc. or it would be nice if there is a way to Publish to web from script.google.com. Please help me!!
Not possible as of the moment. even the official help center Make Google Docs, Sheets, Slides & Forms public directs users to use the web interface via browser to publish docs.
My client has a requirement of making native android and ios app for the e-commerce store based in opencart cms.
My question is, how can I dynamically load the main screen content in the app like banners, sliders etc which are subject to change every day.
I am new in the app development. Please suggest any ready to use CMS for delivering dynamic content to the app. Otherwise, please guide me on how should I approach with building this app.
P.s. I am an experienced web developer with basic android app building knowledge.
I'm not that experienced with android but here are some wild ideas, maybe it will be useful.
You can build a REST API which would return JSON, for example:
[
{
"sliderIMG":"http://yourwebsite.com/image.png",
"sliderTITLE":"Your title!"
},
{
"bannerIMG":"http://yourwebsite.com/image.png",
"bannerTITLE":"Your title!"
}
]
And then your mobile app upon launch would connect by using some REST API Library (Volley or Retrofit) and scrape data as well as display it.
You could make a mobile version for website and just iframe it in the app by using webClient. (However if you already are capable of this, using an app to open a website kinda defeats the purpose of having mobile app in the first place)
I am working on an Application for Android TV and I have implemented in-app search using online API. Is that possible to make Android TV Home screen search/Global search using restful API and display data in the search result rows.
It seems Youtube and Hulu is returning search result which is coming from the feed and not from the data stored by the application. (I am not really sure but seems like it. )
If that is possible, any help would be appreciated.
I have created a WebView app for my android device, but I have come to a brick wall. Can anyone help.
I am trying to get Google search results from the Google search widget, passed into my Webview ?. so basically making my Webview app the native browser for my phone. is this possible ? can anyone point me in the right direction
(image of Google search widget)
I have searched all over the web, but all I can find is,
making links stay inside the Webview. But I have already done this.
How to create a Google query
I have already done these (with succession) all I need to know now is, pass Google widget results
into my Webview. fairly new to app development, but I'm learning.
You need to use google Data APIs or GDATA api.
Check this link. Select the proper api you need and read its documentation on how to use it.
You can also check the google api - java client for android or gdata -java - client
The documentation for google web search can be found here.
Hope this helps.
Use this api from google to get results
http://google.com/complete/search?output=toolbar&q=football
I am planning to create an application in android which has following features
Show Source to Destination Route
Show Reverse Route
Show Traffic Data
Show alternate Route
Store user data
apart from that i want to use some android native controls such as image button , textbox , dialog over the map.
Now after reviewing this link i am bit confuse in choosing the approach among
Google Maps API V3 in the Browser
Google Maps API V3 in a Browser Embedded in a Native Application
Native Google Maps APIs
Can anyone please help me out in choosing the right approach ?
Well, there's no simple answer to that. Every approach has its pros and cons.
Now let me state few insights that might help you in your decision (based on the idea that you want the map as a part of a native android app, not just a html5 app - correct me if I'm wrong):
You need to store user data.
If you want to store the data in the app, then I guess you can leave out the first solution. It would be very difficult (or even impossible) for you to properly maintain your data with map in a browser. The best way to maintain data is then to directly communicate with a server from the webpage and store data on the server (so you need a server backend). You can also pass some data from the webpage to an activity by registering an intent filter for your own url schema.
You don't have such problems using approach 2 and 3, where you can use android code (if you are embedding the map in a webview you can access android code by binding javascript code to android code).
You want to use android native controls.
Now you can also leave out the 1st solution, you are using browser controls there. In the 2nd solution, you can use both (the map needn't fill the entire screen and you can also place controls over the webview).
Google Maps API v3 is frequently updated and currently much more comfortable than native API. Native API wasn't much updated (not sure if it was updated at all) since Android 1.6.
From these 3 points I would prefer embedding Google Maps API V3 in a webview. Of course, I might have missed some important features of your app.