I'm about to develop eCommerce native android app similar to ebay and flipkart but at this point have many doubts they are.
should all the data required to show in app must be fetched using
services at the background and stored in temporary memory before app
is opened or must the request to fetch data must be sent at the click
of button option. because on click of button consumes more time for
fetching images and in case of eCommerce app there will be more
images.
In eCommerce app, using sqlite to store and retrieving data is better
or using preferences or any other better alternative?
Which is the best method to develop eCommerce app i.e hard coding
everything or usi
ng RSS feed option from website or is there any other alternative?
next doubt is regarding size of apk. how to optimally reduce the size
of apk while developing such big app ( well i do know about pro-guard
and lint and remove repeated codes and other stuff but still it
doesn't reduce to that extreme level). i have developed an app
similar to facebook but the size of apk is 16MB which is really very
huge. as per my prediction this eCommerce app might take 20MB but
when checked with flipkart(6.3MB), OLX(4.96MB), Jabong(5.1MB) how is
this possible... the basic helloworld app takes nearly 1MB...
How to optimally reduce the number of server client request to reduce
the hit count in server.
Any advice and help from experienced people will be of great help.
sorry for long post and thanks
Related
i have app , i need connect app with database but i dont know if firebase database good for my app instead of using the server
please advise about this and what is different both and do i can rely as main database for my app
FYI - phrase my app shopping online simple
Firebase is a really nice option for starting as
It help new developers with higher compatibility with the app
Firebase manages mostly all server side scripting and things you might need in the future
It is free for small scale apps and user can choose to pay as they use over the quota
I will suggest you to go for firebase if you are not dealing files (pictures, videos, pdfs, other) as it only offers 5GB cloud storage for free
If your app deals with lots of users and lots of files, firebase will be expensive for you in the long run
I'm going to build a third-party app that reads ranking data from a Unity-based game. It seems there is an app with a similar feature, Hearthstone Deck Tracker. Hearthstone is a Unity-based game, and Deck Tracker reads data like cards, logs, results, etc. I'm curious about how can I read data from the app without actual permission because It's a third-party app. I want to make it read a JSON file from the app in background mode, then load it in when it starts.
Hearthstone Deck Tracker (PC) is open source, and you can find it on GitHub:
https://github.com/HearthSim/Hearthstone-Deck-Tracker
The app has gotten quite big over the years, so you can check one of the oldest commits, where the core functionality still exists, but in a way simpler form.
Version 0.1.1
Apparently, Hearthstone logs most of its game actions, and the tracker just reads them. I assume it works similarily on Android.
So unless the game you're trying to build an app for logs data like HS, I'm afraid it will be very difficult to do.
I work in a Company and I got the task to check if it is possible to transform the current native app we are using into a Processing Web Application.
The main reason for developing a PWA is because of its offline functionality and because it will be accessible on every device (smartphone, tablet, desktop).
Native App:
The Application is about providing news, articles and different products to customers. Every customer (user) has his own profile and is only allowed to see certain products. Each product has at least one picture and at least as many documents for download.
Question:
Because there are alot of products, pictures and documents I am not sure till which point the PWA will be able to let the user see and download the pictures and documents of the products.
In best case every product will be displayed offline. Due to the large amount of products and images, it is probably not possible.
What would be a realistic amount of content that would be available offline?
When may the transformation of a native app into a pwa become problematic?
It looks like your main bottleneck will be offline storage. The limitations consist in 2 things there: The amount of data you can store and the persistency.
Regarding the amount, the limitations are the following at the moment:
Chrome <6% of free space
Firefox <10% of free space
Safari <50MB
IE10 <250MB
Edge Dependent on volume size
https://developers.google.com/web/fundamentals/instant-and-offline/web-storage/offline-for-pwa
(Check as well the section below:Current and future offline storage work)
This is actually not a lot when it comes to images. You could however store a lower resolution of them offline and use the original resolution only when there is a connection.
Regarding persistency, the handling is not the same on different platforms, but generally vague. While chrome you meanwhile can ask for persistent storage (only the user can clear the storage, but not the system), in Safari the system can wipe your storage after a while.
https://developers.google.com/web/updates/2016/06/persistent-storage
See also: Is IndexedDB on Safari guaranteed to be persistent?
What I want to develop: Crude Overview?
Suppose 10 web links present on my (native/web) app, and user will scroll through links. And when user clicks on any of the link, it will open that website. And user might wish to close this website and again views the list of those URLs on my app and the cycle may go on as per his wish. Also, user can create custom list of those links. Also, these lists will be updated regularly, may be on monthly basis. Which I guess I just need to update data files and not app.
No, it is not similar to browser bookmarks but in very crude terms you can relate it. Anyways, I will accessing user's bookmarks with his permission which I guess can be easily done with the APIs available.
Right now, technologies in my mind.
1) Phonegap ( to be precise, its phonegap build - as I don't have MAC) with JQuery mobile and deploy as native app,or
2) SenchaTouch and deploy as web app or native app using sencha cmd.
3) I want to use MongoDB along with above 1st or 2nd option. Is it required or JSON can suffice? Also, I may need some security by encrypting this data while storage at user's mobile and also while collecting user's custom lists.
4) In future, I would also need Node.js for the purpose of collecting MongoDB or JSON data files in above 3rd point. Is there any other way so that it can be integrated with phonegap or senchaTouch.
Please suggest things if existing resources can help me develop my idea and guide me what to use!
Note: All technologies I am picking up are focused on single code base with minimal focus on platform specific changes-iOS/android/Windows/Blackberry.
I want to go for Native app rather than web app. Why?
1) I feel that it would perform faster if I deploy my idea as android/iOS/Windows app rather than web application.
2) My cost of hosting the application on server will go to null because I am using local storage of the user's mobile.
3) Since I want a feature in my app which stores user custom settings so it would be better if I deploy it as mobile app rather than web app so that I don't have to maintain user specific settings which may make my DataBase hosted on server to grow immense in future.
4) Also,I feel that there is no sense in hosting this application on a dedicated server because there would be less user interaction with my backend. But later I would plan a feature to collect data/settings done by user to improve feed for which I think I need to use Node.js. But then also there is no requirement of hosting frontend to a dedicated server. Hence, I can use dedicated server to serve my own purpose of analytics to improve feed rather than service user's purpose of unnecessary access to my web application always through the server and fetching lists of links which are maintained on server in custom manner for him.
My dilemma!
My above points are valid to prefer deploying as native app over rather than web app. But I feel what if I keep my app as offline web app which runs on the default browser of the user but loads the jquery and other data and scripts from the storage in mobile. Is this possible? I am unaware of this.
If this is available then it is the best thing for me to adopt as my application redirects to other websites. Because, if I am deploying my app as native app then it would ruin user experience of opening my app and selecting an option whose URL opens up in default user's mobile browser which is a different app and then there are many chances that user will switch back to my app and then again he would be redirected to that mobile browser. And obviously I cannot develop my own browser in my app as I would have to develop several things from security and other perspective which would be a cumbersome task. So, having my offline web app will be opened in user's default browser itself without annoying him to switch back and forth between my app and browser as in previous case and thus creating seamless experience.
Also, I am not sure whether we can create offline inbuilt browser plugins as we can do in chrome browser on desktop. If so, then I think I would have to concentrate differently on different mobile browsers Safari, Chrome, mozilla which I feel is not worthy. Please throw some light on this for me.
I have no idea why people are downvoting my question as I feel that it is kind of unique question.
Here is what I found more and with the help of my friend
1) I don't have to use MongoDB as my application is not much complex. So simple JSON will suffice.
2) I'll be using Phonegap for android and windows phone and phonegap build for iOS along with jQMobile. So the app will be in the native form only.
3) I'll be using inApp browser for seamless experience although it is not as perfect as having my idea as web app.
4) No need for senchaTouch as it is heavier than phonegap and not required for me idea.
5) My next look forward is comparing the above points with offline web app built using JQMobile and JSON and finally whatever I decide I will share.
EDIT:
I am finally going with phonegap for native deploy rather than offline web app or web app hosted on server for reasons that I found on several blogs.
People downvoted my ques so I feel that it is not worth writing answer further but if you want the detailed reason you can always add a comment.
Thank you
You should definitely go for web. It is cross platform. If you do an android App, or iOS App, they are restricted to the specific devices. So I definitely recommend Web App
Actually I have a Client-Server based application developed on vb.net/C#.net now i want to port or publish that client-server Application on Android. I knew the tools for making it useful for my Android device. And I have also make out some important point to find out the cost of that project, but i'm newbie so i can't understand how to give assign or fix a amount for particular task in android. My Points are:
Develop a jazzy look user Interface for displaying a data.
Check and use the Device's network connection state.
Use the web service for accessing the method/functionality of
client-server application.
Also check and use the state of web service whether it is available
or not and use the functionality or fetch the data on the basis of
state.
Also the main thing is to maintain the server for storing the data
and fetching the data via web service.
Any help is appreciated for finding and assigning the cost/price/amount to the Android application.
This usually depends on the size of your target market. If you have a large target market, you can let the app go at a low price, because volume and economies of scale will kick in bringing your costs down while your revenues go up.
If you have a smaller target market, you're going to have to bump up the price of the application in order to recover costs of delivering to such a small market and move into the positive for profit loss.
For the most part, you can ignore the cost of developing your app. Development is mainly a one-time fixed cost that disappears over time. There will be some maintenance of the application itself that will cost money over time, but it isn't enough to worry about. Your server maintenance will be the brunt of your costs, but provided you're able to outsource most of the storage and bandwidth onto Amazon's extremely cheap pay as you go servers, you're running costs will be relatively low as well.
The greatest majority of your budget will be spent on marketing (depending on the type of app you are developing). Should you get a shoe in with the press, or market through ads on mobile, Facebook and the like. This is where most of your money will be going. Make sure to offset the cost of conversion with the revenue generated by conversion.
If you gave me more details, I could get more specific and help you out some more, but with what I have to go on, I have to stay broad. I wish you the best of luck with your venture.