Case: I have an app for Android, Android Tablet, iPhone, iPad. Server has a backend to upload image (not the app). App user can browse these server side uploaded images on their phones.
The images which are uploaded from a server backend can be of square and rectangle dimension.
Note that I support all iOS devices and all Android devices. The simples way of doing it is serving one big image for all the devices.
Qustions:
What display size should be reference for the image dimension being uploaded?
Which sizes should be created on the server from the uploaded image?
you have to upload high dimension images only.In server side there is a magic view funtionality you have to implement.In App side when you got image url from server side then check your device resolution type and then set resolution size for that image in application.
You could resize the images at the time of request depending on what is most important, the speed of the request or the memory footprint.
This post gives a clear example on how to resize images.
Related
I'm trying to implement an Android app that uploads an image taken by the user to an API which removes the image's background, and sends it back to the Users device.
Here is the API for more info. I'm trying to send a jpeg image and receive the image as a jpeg aswell.
The API docs state that the POST request has to be multipart/form. I don't have any experience on making API calls using Volley and was wondering if any one could help me figure out how to do it. Thanks in advance.
One of our core system has been integrated with a mobile app recently where we need to share images which are kept in our repository to Mobile app which is residing in another server in the same network. When we analysed solution
Send image as byte[] over the api which is getting used to call
Host image in one of the container we are running and share the image url over api
Which one is the right approach to go on with, or is there any other approach on which we can have a better solution ?
1.Upload image into server using mutipart.
2.Save image into server and make the path of it.
3.You can use then anywhere this byte of path.
Hope it helps
I want to take an image from raspberry and recive it on and Android App (this is the problem). I already have a Java project that create an image and store it in a predefined location. I don't know how to create a server on Android app, and how to upload my image on the server. I think i will create a post webservice on raspberry to upload the image on my phone app.The image from rpi must be displayed on the phone (like notification or something). I need help on Android app, I don't know how to recive the image on the phone/how to send it from rpi location/how to show the notification when the image was send it/ how to show the image on the phone.
I have an ArrayList of Serialization objects on my handheld.
I found a solution to send it to my wearable device.
Can I send custom objects to Android Wear?
In my Object I have the URL of an image and in my handheld I am using Picasso to download the image from the URL (es in a ImageView).
Can I download the image in the wearable? (I think no).
Should I download all the images of the ArrayList in the handheld and send it putting them as assets in a DataMap?
You can't download images directly from the Wear as there's no direct internet access.
However you're on the right path by downloading images on mobile (e.g. using Picasso), then transferring them to the Wear via an Asset.
There's a tutorial with all the code required on how to send an image using an Asset in the Android training section:
https://developer.android.com/training/wearables/data-layer/assets.html
I am trying to developer an Android application which allows to capture pictures with the camera, and send the pictures to a Java server.
I don't need the picture after, so I do not need to store it in the phone locally.
I was able to successfully to transfer simple text from client to server, but I'm having problems with images.
What do I need to do to be able to send images from the Android client, and should anything special be made in the server apart from what it is doing now?
Solution is to use http request with MultipartEntity.