Web service for stats? about andlytics HOT 10 CLOSED

Thats kind of beyond the scope of the app. I mean there could certainly be an intent to share the data (#106 is all about improving getting the data in/out), but everything else would not be part of the app.

from andlytics.

Nope. Its an extension of the service. Thinking out of the box. No one
would be able to use such a web service without having the app. Would be
good for sharing the info and stats.

from andlytics.

Well, what's the point of having this on the Web if you can only use it through the app? I actually wrote something similar a while ago using the unofficial Market API. It ran fine for a while on App Engine before they blocked it. It will be relatively easy to pull the GWT-parsing and authentication code from the app, stick it in a webapp and and save stats to a database, however:

• if you have a centralized service, someone has to host it, and that generally costs money.
• If you make it self-hosted, not everyone will have the time/skills to set it up.

A much better idea, IMHO, is to use Google Docs, since it only requires a Google Account which everyone using the app already has. Sharing is also easy. Once I am done digging through Jelly Bean source code (might take a while...), I might look into implementing this.

from andlytics.

You didn't read what I wrote fully. The app already has an export feature for the stats correct? If there was a nice, well built web service/script that could read and display that info, then one could have the app automatically export on a daily basis to a folder on a server. That way one could publicly, or privately via logins, share those stats on their websites. Not everyone uses Google Docs and it isn't ideal for posting on a website.

As for the point about web hosting... First, that doesn't cost much at all...I'm paying a whopping $4/mo. And it would be a shame for a developer to not have a website for their app, as they should.

As for the point about setting it up... Again, you missed the point of someone building it so that someone could easily set it up on their own with little skill. You're making it sound harder than it is....it's pretty easy. If the data exported is in a simple format, then all this could be done with simple scripts and css. Hell, someone could even make a WordPress plugin for this.

Once everything would be set up with simple instructions, then after that everything would be automated. The android app would export and upload automatically. The web service would automatically read that file and display the stats/info.

from andlytics.

What you wrote was very short and not at all clear. I missed you points, well, because they were not there.

So you want to make a website/service that visualizes your andlytics data. Good, but that seems out of scope of the Android app. If you write one, do share it, someone else might find it useful. If you expose a usable API, someone might even hook the app into it.

BTW, this is GitHub, so if you propose something, you should be prepared to write it :)

from andlytics.

well it should have been obvious when I mentioned a web service to display stats, the exporting feature and the idea of uploading it to your server....all contained in my first post.

As for being out of scope... I'd say y'all are being closed minded to potential. If you aim to only gear the app to very narrow parameters, then that in turns limits the app's exposure and overall usefulness. If you're fine with that, then by all means. But I personally see a lot of potential in this app beyond what it currently does. Right now there really isn't a nice, clean solution for displaying ratings and comments on your site...which is good when promoting your app. The current such solutions are sloppy and pretty hacky because all they really do is scrape info from the play website for the app.

And I could do this and probably will give it a go one rainy day...but that would also depend on the format of the export data. It would have to be clean and organized.

from andlytics.

Obvious to you, maybe. Few people on public forums can read minds, so it helps to spell things out in detail.

Again, this is github. If you wait for standardization, review and design documents being written, you will probably wait forever. Take what's there, build something with it, the improve/request improvements as you go.

from andlytics.

Ughhh... please, we're all supposed to be adults here...shouldn't have to spell everything out for you in a long description. I was clear in what I said, but whatever.

Well, maybe that's how things go with this project, but that isn't true for all. Some do use basic project management to show active development. Its a key practice needed to have a successful app. In the past, this app was literally only ever updated when there was a problem...and that's it. Never any improvements or feature adds....and that was a shame. Now with a whole group of developers working on this, one would hope that it wouldn't just be business as usual. One would also hope that developers working on this project want to show an active movement with the app and would be engaged in doing so.

With that said, I think I'm done with this project. If someone can't propose a sound idea for the "scope" of the app or for the design of the app without being responded to by rudeness, then what's the point? Seriously, what's the goal of this project? Just keeping business as usual? Only working on things when something goes wrong? Never advancing the app to it's potential?

So far on nearly every sound suggestion for features or with some free UI design advice that even Google has paid for, I have been met with rudeness here. I think I'll go back to designing and developing apps whose proceeds go to help a cancer patient in need. They appreciate and welcome the free help.

from andlytics.

Well this issue seems to be over so I'll close it. Just to add, I gave you a frank assessment that building a web service was beyond the scope of an android app. Sure it could be done in the future, or you would be welcome to do it yourself, but there are lots of other smaller improvements that have and can be made which will make a bigger difference to the app with a lot less effort so are therefore a priority. If anyone has ideas that have a small usage case the answer isn't no, its not right now, but please have a go at doing it your self.

from andlytics.

Thanks everyone for the discussion. Haven't had much time recently and probably won't have before end of July.

As for all input/ideas being ditched:

• Better ICS compatibility: we implemented the new "real" ActionBar
• Remove config stuff from the main view: Done

Both things are implemented on the master but not released yet. So from my point of view we did not ditch all of your ideas but implemented some which we haven't released yet.

Edit: He deleted his user... Could have saved the time to show the progress here.... Happy coding / improving everyone! In my opinion all of you have spend a decent amount of time to push the app to this point and I personally think we made great progress!

from andlytics.