This is a suggestion / request to the mods as well as an invitation to all site members to contribute any info they have on this.
At the moment there are no real viruses for windows mobile devices, only a few proofs of concept.
But I have encountered a few examples of supposedly normal commercial software that I really wouldn't want installed on my phone.
Example 1:
A while back a small company (who's name I no longer remember) sent a letter to all its customers threatening that the anti-piracy protection on their software will damage your bootloader if a cracked version of one of their apps is discovered on your phone.
Example 2:
It was reported a while back that Agile Messenger sent user names and passwords for all messenger services unencrypted through the net potentially giving anyone access to your accounts.
Example 3:
While reading the EULA for Opera Mini I discovered it sends users phone number and all their browsing data (cookies, history, cache) to the Opera ASA server basically spying on your internet activities.
Unfortunately all the threads dealing with these otherwise nice and useful apps have now moved deep in to site history so any new users or just someone who haven't been on the site for a while is likely to miss them.
My proposal is this:
Create a sticky locked thread, I think the general section would be most appropriate, so anyone visiting the site would be able to see the list of programs he might want to avoid.
Why lock the thread?
As I understand it moderators can still edit locked threads any time they want so there are two reasons to keep it locked from the general public:
1) To keep the list clear and easily readable.
I am sure many people will want to comment on the software even if it is just to say "how dare they do this?", but any comments / questions would be better off in separate threads.
2) To be fair to the software creators.
I think that anyone making a claim against a software should provide some minimum proof. Like the email quoted in example one, comm log dump or screen shots. At the very list confirmation from other users.
This site has a lot of impact on the mobile community and it would be a shame if a wrongfully accused software would suffer due to being publicized as damaging here.
Hello everyone. I've a sort of proposal for the developers here, but before I get into that let me first briefly introduce myself:
I'm a communication designer for print, user interface, and illustration that completely advocates everything Android. I've been lurking the Dream development forums here for quite some time, trying to keep up-to-date with the latest ROMs, apps, etc., etc and I fully appreciate everything that goes on here and the endeavors that you devs put yourself through. Amazing stuff, really.
One thing I've noticed is that there are a slew of third-party / beta apps all over these boards, and other places on the internet as well. More often than not, I find myself scouring the cloud just to find a link for these non-market apps, and I usually get referred to them via some obscure site through another site. Despite getting the .apk file or ROM in the end, the process can get to be a bit tedious; especially for incoming users and those new to the Android platform.
My proposal is this: A website with a simple and clean user interface that has direct and succinct navigation with the purpose of consolidating and listing third-party / beta non-market applications into an easy access database. This website database would link these applications and have them be easily downloaded and installed via the Android browser, without having to mount the device.
I've actually come up with a fully-functional concept site, did the branding and everything for it, and also registered a short domain name for quick access while on your G1 or whatever Android device.
Navigate to: http://anda.pk to see what I had in mind, and how the overall layout/concept of the site would work.
I uploaded several .apk files I had backed up as examples for you to see how the database section would function. I also took into account the resolution of most Android phones and made the .apk application database section fit perfectly in the Android browser when in portrait mode right when you the load the site to ensure the best possible user experience when installing these third party apps. When you scroll to the right, you'll see info on what the site is about, and in the footer there are links to the FAQ, the about section, contact, etc.
I had also noted in the about link in the footer that the applications hosted on the download section are in no way accredited to the site, and that credit goes to their rightful developers. My being a communication designer has had the idea of peer collaboration engrained, and as such I give credit it where credit is due.
That said, I hope you guys here and the developers collaborate with me on on this site, possibly help contribute apks, and agree to them being hosted. If anything, I do hope you just embrace the concept, which originally was just going to be a reference for myself and my friends whom I've turned away from the iPhone, S60, and WinMo in favor of Android. I figured since I know the Android community is only going to get bigger, this website concept of mine could be a decent resource to have bookmarked.
Appreciate you reading this wall of text! Do hope to hear some feedback, so let me know what you guys think. Thanks!
Cheers.
I think this is a fabulous idea...automated version control would go over very well -- i.e. yum update
you should post up bits that you need help with and have folks contact you.
also..I love the logo!
question: do you propose a rating system or a review prior to listing type of approach or something new to keep this resource trustworthy?
Been following this on SA and twitter and it's a great idea.
Having the devs here on board would be a fantastic way to get something solid on the go. It's the kind of thing that can really help android become more hackable and useable for the average user...and it just make things easier for the rest of us.
Sounds good to me.
thelilliandivide said:
the applications hosted on the download section are in no way accredited to the site
Click to expand...
Click to collapse
Credit and accreditation are different things. To be accredited is to be given credentials or official approval. I think you meant "credited".
Sounds like a GREAT idea.
My opinion: The color scheme hurts. Love the logo.
i like the logo and the idea. I think the site should be more mobile friendly, or even better, an application for android that can work like the official market. I could help with that part if an application is going to be built.
camalot said:
i like the logo and the idea. I think the site should be more mobile friendly, or even better, an application for android that can work like the official market. I could help with that part if an application is going to be built.
Click to expand...
Click to collapse
i second that.. it should also have update checks if possible
I was going to complain that I didn't like your site layout, but in portrait mode you only see the left side which lists the apps. I like it.
One thing you might have to be leary of is dealing with apps that are considered warez unless your going to spend the time to verify every app that is uploaded or there has to a method in place.
As well there should be some kind of version control in place. You know what works on 1.1 and what works on 1.5. Obviously almost everybody within the next few weeks/months should be on 1.5, but will all the older apps run on 1.5 or does it really matter or does anybody care? The downloader will care.
CBowley said:
Sounds like a GREAT idea.
My opinion: The color scheme hurts. Love the logo.
Click to expand...
Click to collapse
Seconded. The text is much too light. A darker charcoal shade would be much better.
If the site gets an apk wrapper (a la FBook) version checking would be rather easy. Set up the directory tree something like this /downloads/WiFiTether/1.2.3.apk and just have the apk compare filenames. If the file names don't match, it needs to install the update.
EDIT: Now following your progress on twitter.
Some solid input. I'll play around with the color scheme and make some changes later this evening once I get back from class. And I actually do plan on making a mobile wrapper eventually, but as it stands as far as the concept layout goes, the site is best used when in portrait mode for easiest functionality. The rest of the site is to be considered supplemental. I do however, have a lot of things I eventually want to integrate; application tags, search, possibility of user uploaded apk files, etc. But for right now, I'm trying to keep the general site as simple as possible to make the workload on my end less stressful (graduating in 2 weeks).
bahnburner said:
If the site gets an apk wrapper (a la FBook) version checking would be rather easy. Set up the directory tree something like this /downloads/WiFiTether/1.2.3.apk and just have the apk compare filenames. If the file names don't match, it needs to install the update.
EDIT: Now following your progress on twitter.
Click to expand...
Click to collapse
Did not know how that version checker worked. Thanks. I'll re-work the apk directory scheme akin to that later tonight for when I do eventually get the wrapper up.
thelilliandivide said:
Did not know how that version checker worked. Thanks. I'll re-work the apk directory scheme akin to that later tonight for when I do eventually get the wrapper up.
Click to expand...
Click to collapse
That's not necessarily how most version checks work, but that's the simplest method I could think of, and probably one of the easiest to implement.
alapapa said:
I think this is a fabulous idea...automated version control would go over very well -- i.e. yum update
you should post up bits that you need help with and have folks contact you.
also..I love the logo!
question: do you propose a rating system or a review prior to listing type of approach or something new to keep this resource trustworthy?
Click to expand...
Click to collapse
Thanks! And I feel I might need some help in the future as far as implementing the features that I want to get working. But I'm not quite sure I understand your question. Are you referring to how I choose which applications get posted onto the site?
i'm a graphic designer and web designer, i'll throw in a helping hand if you want, pm me or whatever.
(think about an android based layout to bring it to the phone like Cough*cydia*cough
very cool and much needed
Xda-dev is great, but there is alot of stuff thats not on the market and they have shown to bow down to the tmobs pressure(ie: tether app) so another place to get apps would be great, and your weppage is beautiful and looks like it would be very finger friendly on the g1, but there is a basic model in linux of repositories(which is about what ur doing) and a simple app to d/l them maybe somebody could just make a market.apk with a modded addy, depending on how much is known about the market and its inner workings... it would be nice to do it as it has been always done....but as I stated above your webdesign is very nice and would work well in the native browser(im heading there now on my g1)
bhang
not a bad idea. I think this is great for all verified apps that are pulled from market...
I really like this idea. Go for it.
Just one (stupid) remark about the logo... it's like it has a big nose and a :-| expression... sorry
apetit said:
I really like this idea. Go for it.
Just one (stupid) remark about the logo... it's like it has a big nose and a :-| expression... sorry
Click to expand...
Click to collapse
Haha, I just noticed that actually. Now it's all I see. But yeah, I'm hoping to have a few more apps to upload by the end of next week. Revisions to the site are imminent once I get out of this last class.
I love the idea. One bookmark to check up on all the good non-market apps will be much easier than having several bookmarked threads.
Some applications may benefit from having tags such as [beta], [stable], [experimental], [contains-ads], etc.
As others have mentioned once/if user uploads are implemented an app approval system will be crucial to keep the spam at bay. I can see this really taking off.
im a supporter
zgmf-x322a said:
im a supporter
Click to expand...
Click to collapse
+1 this sounds like a great idea, there was something like this for apps for the dash,mda & sda.
I found this listing while applying for a position in the consulting and finance industries and it looked like something one of the Devs here might be interested in.
I don't know if I'm allowed to do this, so if a MOD could set me a pm if not, I'll happily remove this posting so you don't have to.
ANDROID DEVELOPER needed for the development of interfaces with Web Services using Android API. The term of the project will be long term if the candidate performs well.
The rest of the posting can be found in the zip file below. There is a pdf of the posting at the University of Rochester Career search site, as well as the posting's original listing at Dice.com, which I find easier to read.
Hi!
After only being a user for a long time, I've recently begun to develop for Android as well, and I think that I have identified quite a few niches that could use better apps. However, I've never collaborated on an Open Source project, and I'm really unsure what the written and unwritten rules of the subculture are. Could anyone point me in the direction of good resources to learn about them? I know I can probably find those through Google, but I wouldn't know if I'd end up on any site owned by Stallman or Shuttleworth and I'd rather be part of the mainstream, so to speak.
To indicate what kind of questions I'd like to have answered, without requiring anyone to answer them here: What level of expertise is required? Can I just join anyone and upload to their repository, relying on them to sort out the parts they want? When can or should I fork a project? When is it considered rude to take code snippets from someone? How sure can I be that the project's owner won't change the license and steal my code? How would those questions be answered if money is involved? Is it considered reasonable to make an Open Source application that people pay for in the Play Store? How would I handle contributions to such a project? What would be the best license to ensure that I both contribute to the Open Source movement and protect myself against people stealing code? (I. e. just forking it and slapping their name on it.) And many, many more - as I said, I'm really unsure how to start out with this.
Thanks very much in advance!
Regards,
David
Maybe I can help you on a few of those points. First off, feel free to fork anything you feel like, whenever you feel like something needs to change. Also feel free to push any changes you make back to the original project. The project owner can decide what to merge in. As for lisening, please note Im NOT A LAWYER, however, I think I can offer some general knowledge. If code is under a typical open source license, the code at that particular point in time is free to be viewed by anyone. A lot of open source licenses, though not all, are considered 'copy-left', in that any code DERIVED from the liscensed code also has to follow the same license (GPL comes to mind). This helps from people 'stealing' your code at a later point under a closed license. As for taking code snippets, it depends on the license of the code. If you grab a piece of code from a GPL codebase, whatever you're using that code in also has to be GPL licensed. You are in essence taking their code, and modified it. Learning more about different open source licenses might be something to look into, depending on how far you want to delve into this As for making people pay on Play store for open source projects, its certainly acceptable. A lot of people make money from open source software by prividing some form of 'support'. Whether thats tech support, or whether its compiling, packaging, and making it available (as you might do for an android app) you are providing some sort of service aside from the actual code that people will pay for. I've seen a few projects go this route. Hope this gives you more answers than it does questions! The OSS community I've found to be a pretty easy going group of people, so long as you follow a little common courtesy, and have a bit of common sense. Cheers!
Thanks a lot for your reply! It has certainly helped me to make my mind at ease - I know that Open Source people can often be _very_ friendly and open, but it seems like you really do not want to get on their bad side if you intend to be a developer. That's also why I especially worry about being rude, not about doing something illegal - the licenses themselves seem to be quite permissive.
Quick followup question on the money thing, though - is it accepted by Google if I offer a paid app in the Play Store and at the same time free on F-Droid? Or would I have to ask someone to compile and upload it there without my official participation? Because that would kinda be the ideal model for me - Open Source, free app on F-Droid and sideloaded, "lite" and paid versions in the Play Store. Something like that would be good to know before I actually begin thinking about deploying some app.
So I am going to post this here, because the development section is ferboten to people trying to offer useful suggestions. Geez, I hope this is the right section.
Let me set it up. ANDROID IS BASED ON THE LINUX KERNEL. Everything, and I mean everything after that fact becomes android and bloat. Given this as the basis of all things android, I have a simple set of guidelines that should be used to create a solid, reliable, bullet proof operating system for devices able to use the android operating system.
#1. Create the kernel boot section of the basic platform that supports the very basic hardware features, including touch screen, radios, power/charging/battery management, wifi, bluetooth, nearfield, audio, microphone, s-pen,etc. Basics only. Root access is standard and can be turnd on/off just like developwer functions. No special tricks or addon hoops to jump through.
#2 At this point STOP. Every single process or service to be run on the device from this point forward should be able to be individually selectable - or not. Yes, I understand that individual services or apps may have dependancies to other processes and that thouse need to be functional in order for a particular app to work. That is why, each additional service or app must list the dependencies and in the selection process, the installion will be required to verify you have the proper services installed and functioning, if not to list them and allow you to make the decision to proceed. Viola, we have NO MORE BLOAT WARE.
#3 Make selecting additional services/apps selection process a menu driven, tag selectable process. Make the unselection process smart to verify and identify the other apps dependant on the item you are killing/removing.
#4 Allow a built in snapshot option to capture the entire system as you have customized it for yourself and allow it to be backed up to external memory with the ability to bring it back, AT WILL. With no big hassles.
Those 4 items are a good start. By themselves alone, it would put all of us in the drivers seat of controlling and living with our devices.
I am aware that such a system is not for everyone. It does require some basic technical understanding of the process. But for the vast majority of users, I am certain, that an a la carte system is far superior to the bloated monstrosities being forced down our devices.
I would appreciate any refinements to my suggestions.
The silence is deafening. It has been days. Kind of says something, don't you think?
I am so very happy (not) that these boards a compartmentalized to the point where you can't get through.
Pretty much a waste of my valuable time, especially considering the fact that if my suggestions where applied, people would be clamoring for an installation with those features. I guess there is not much true "developer" in xdadevelopers anymore.
Funny guys, with the pay to remove ads spam here. Really? Why? For what.
I leave here disappointed. Not angry. Just sad.
I'm not a developer so I have nothing valuable to contribute to your suggestions in your original post but I can offer an observation regarding your perception of the level of contribution to your thread and that is the fact that is particular area of the forums probably isn't the ideal spot to have a discussion such as this. You figured that out already so sure you can call me Capt. Obvious if you wish but I'm just pointing out that yes the forums are compartmentalized (as you've stated) in such a way that development for each device is separated out. This development is centered around AOSP based ROMs or "stock" ROMs (using manufacturer released source) so if you're looking to have higher level discussions about what AOSP should look like then deep down at this device specific level probably isn't where you want to be. So there's that . . . then there's the fact that for this particular device you can basically hear a pin drop in the sub-forums as it is since nothing much is going on by way of development.
Where specifically such a discussion would see more input I'm not sure, perhaps the main general discussion section?
Thank you for your sobering reply. I get frustrated. Already had my post bounced out of "wrong" forum while trying to speak directly to "developers" (i wanted air quotes because the term does not accuratly describe its target) So I tried this. The note pro 12.0 is still the best hardware giving the ipad a run for its money. The problem its monkeyshines kiddie software running it, or not running, or barely running it. ANDROID, indian word for crappy wannabe software, developed by clueless kids.
Again, thanks for the gentle nudge. I appreciate someone willing to conduct a conversation
Are you looking for an Ubuntu or SUSE type of setup?
I think what you are looking for is similar to apt-get type of installs, I could be wrong of course. This might be helpful for many "users". I think one of the barriers is that there are slight differences between the models of tablets, and creating the logic to put in for the sub-dependencies might prove problematic. You might get more answers to this possibility by asking one of the developers directly and sharing with them. Not a developer myself.