Related
Is this just another Siri clone or is it closer to "AI" (define as you will). Is anyone here involved in this?
http://www.kickstarter.com/projects/cogcode/silvia-for-android
I searched "silvia" and "silvia for android" before posting this thread. If this question or topic has been posted before, or if this is in the wrong place, I apologize.
MichaelHaley said:
Is this just another Siri clone or is it closer to "AI" (define as you will). Is anyone here involved in this?
...
I searched "silvia" and "silvia for android" before posting this thread. If this question or topic has been posted before, or if this is in the wrong place, I apologize.
Click to expand...
Click to collapse
Hi Michael,
Prior to our launch of our SILVIA for Android Kickstarter project this past Friday (May 25th), we have been fairly quiet about SILVIA for Android.
So, you may not find much 3rd party information on SILVIA for Android, at least for a while.
However, we will be happy to answer your questions as best we can.
First off, we think that Siri is a fine product.
Of course, we feel we have something different and unique to offer with our technology, otherwise we would not be doing what we're doing.
We think that our context sensitive conversational approach to the user experience is very compelling for many reasons, and we also think it is an important difference that our technology runs natively on mobile devices.
For developers, we are offering an SDK with a rich API, a graphical content development system, and a runtime engine that will allow developers to create new conversational applications for Android that run right on the device. For smaller developers, this is very important because there is no requirement for additional (and expensive) server infrastructure to host the AI.
We think that another important feature is the compactness and efficiency of our runtime. The average SILVIA for Android end-user application clocks in at about 7 or 8 megabytes on the device, and is efficient enough to run in the background without disrupting the performance of most other applications.
We will continue to release more details for developers over the next few weeks as our Kickstarter campaign progresses.
I hope this information helps.
Right on, looks pretty interesting, hope to see it available soon!
CogCode said:
Hi Michael,
Prior to our launch of our SILVIA for Android Kickstarter project this past Friday (May 25th), we have been fairly quiet about SILVIA for Android.
So, you may not find much 3rd party information on SILVIA for Android, at least for a while.
However, we will be happy to answer your questions as best we can.
First off, we think that Siri is a fine product.
Of course, we feel we have something different and unique to offer with our technology, otherwise we would not be doing what we're doing.
We think that our context sensitive conversational approach to the user experience is very compelling for many reasons, and we also think it is an important difference that our technology runs natively on mobile devices.
For developers, we are offering an SDK with a rich API, a graphical content development system, and a runtime engine that will allow developers to create new conversational applications for Android that run right on the device. For smaller developers, this is very important because there is no requirement for additional (and expensive) server infrastructure to host the AI.
We think that another important feature is the compactness and efficiency of our runtime. The average SILVIA for Android end-user application clocks in at about 7 or 8 megabytes on the device, and is efficient enough to run in the background without disrupting the performance of most other applications.
We will continue to release more details for developers over the next few weeks as our Kickstarter campaign progresses.
I hope this information helps.
Click to expand...
Click to collapse
We are definitely covering SILVIA and this project
http://www.androrev.com/2012/05/31/...-why-she-may-just-be-androids-answer-to-siri/
Developer Update!
Just a quick update, we have some more information for Android developers on our Kickstarter project page.
Unfortunately, due to the low post count, we can't post links yet. But a quick look at the first post in this thread should get you there.
In particular, we think there is some great opportunity for game developers, as our SILVIA Core has already been deployed as a conversational intelligence system in 3D training systems for the US Army. But even casual game and apps developers can quickly integrate SILVIA for Android into their projects.
The SILVIA for Android library can be used directly in just about any native Java or Mono for Android project, but as a bonus for you Unity 3D developers, we will be including a Unity 3D compatible version of our SILVIA for Android runtime library as part of the SDK package.
All the best,
The SILVIA for Android Team
what happened?
Sent from my GT-N7000 using Tapatalk 2
Okay, this will be more of a rant.
So on non-android linux there are about 10000000000 useful, top-notch, cutting-edge, great, perfect and all round ass-kicking programs around. You can download all sorts of crazy super cool stuff for free because the free software and open source software community is producing awesome things. In many cases the open source and/or free alternatives are much better than the proprietary ones. I can't really think of a need when I couldn't find a really great open source library or full program to do the job.
But with android it's different. On Google Play there is all sorts of crap, feature-less and expensive stuff, the free version of a program is typically unmitigated ape****, the reviews/ratings/etc are useless. There are some exceptions like the terminal emulator, or sl4a, but for gods sake where is the geek community here? With fedora/ubuntu/debian/arch/etc we didn't need a centralized crap store and fancy useless ratings/reviews/etc and everything was still wonderful and you could actually get things done. In android, not so. There isn't a single fully functional open source and free GUI for browsing webdav or files over scp, but that's just the latest frustration of mine. Whenever I think of a program I'd love to just search for, download, install and use in 5 minutes which is the norm in a usual linux environment I know in advance that 8 out of 10 cases it won't be that easy on android.
And so where did all the non-free stuff get us? Now everyone is offering crap for money, all ****ty stores incorporate this supposedly to create incentives for developers to innovate because you know, without money there is no innovation at all on the face of this Earth but let's face it, when things were open source and/or free things worked (i.e. ordinary linux) but now they don't. Seems like the model is just not working.
Why can't I have the same linux experience on my bloody phone as the one I have on my laptop and desktop?
Who screwed this up and when?
Can we still fix it?
Android was meant for consumers as an option to the iPhone. Not for people to get all techy with it.
And most Android users ARE simply consumers who want a smartphone with "app and games," internet browser, texting, email, facebook, and calling
Ask that same consumer about computers, and I can almost guarantee they think its a Mac and PC (in which they mean Windows) battle. Mention Linux, and they'll look at you puzzled.
Sent from my DROID2 using xda premium
Android isn't totally open source. Still better than apple though.
Sent from my Samsung Galaxy Exhibit 4G running Cyanogen Mod 9.
We are not limited to the Play "crap store" since we can sideload .apk files from alternative stores, or from wherever you get them. Also, I wouldn't call the Play store's reviews "useless;" I actually think they're generally helpful, and certainly better than the reviews in the Ubuntu "store."
Also, remember that Google built it's empire on selling advertising, and selling access to analytical data. The general *nix community doesn't have that. That's the difference between "open source" & "free."
-- Sent from my TouchPad using Communities
Yes, we don't need to use google play, but how many software packages are out there for android outside of google play? Not many. Certainly orders of magnitude less than ordinary free software available for desktop linux.
I see the fact that google invented android in order to make money, sell ads, etc. That's clear, so I agree with a commenter that android is not really techy from the get go. But why isn't there an ordinary linux based phone? I hear meego is dying, but why is that? Or why isn't there an alternative to meego which follows the ordinary linux philosophy, being community driven, perhaps with a corporate sponsor like redhat or canonical?
The same path that worked for the desktop is currently does not seem to be there for the phone although I'd think it's just another computing platform, not much different after all.
I honestly think we will never see a true open source phone. There are carriers that have to carry that phone and they want users to be able to have the latest and greatest when it comes to their phones and they want it to be easy for them to use. Android & IPhone both offer that experience a full functional Open Source phone would not offer that experience, you would have to build the source from scratch and flash it to your phone which wouldn't be fun for most users. Plus android has the full source code available here http://source.android.com/source/index.html which is how you get Cyanogenmod builds most of the time, they use google source to build that ROM.
tortib said:
I honestly think we will never see a true open source phone.
Click to expand...
Click to collapse
The Openmoko-Project has grown very far,
the FreeRunner is pretty cool:
> www.openmoko.org
not only the software development is open, you can already even print your case at home if you own a 3D-printer:
> projects.goldelico.com/p/gta04-main/page/CaseDesign/
This is a long shot, but I since the demise of Google Reader (which this app supported) the developer has decided to no longer continue the development of this app. A tragedy; I think we as a community should try and sway him to continue it instead, adding new back ends, both Feedly and TOR (TheOldReader) support would be great. I would love to continue using this app, as it is probably the best RSS reader I have encountered on Android. It is my hope that we can either convince him to continue the project or allow someone else to (any volunteers ?).
Flow Reader gives you an easy way to be on par with your RSS/Google Reader feeds on the go. It was built to provide a minimalist and seamless experience for offline browsing, while delivering additional features not found in similar apps.
Some of the main features include:
- A sleek and fast user interface;
- Offline item content and state caching;
- Multiple simultaneous downloads for fast content synchronization;
- Content filters that automatically mark as read the items you're not interested in;
- Sort items by state (latest/unread/starred) or author;
- Smart algorithms that remove ads and other undesirable content from items;
- No ads.
Click to expand...
Click to collapse
The Developer posted this statement in the most recent app update:
As you sure know by now, Google has discontinued the Reader service, so this app is no longer functional.
Although I am very happy with the (unexpected) success of this app, I've decided to no longer update Flow Reader. This is due to several reasons: a) I built this app "for fun" and to my very specific RSS reading needs. Although I very happy to see that a lot of other people enjoyed it, I was in no way ready for attention it received (due to multiple technical and logistic reasons); b)This app was essentially just a prototype turned into a final product. The Code is very messy right now and it's becoming harder and harder to make any further changes, let alone any major ones (like background updates). c) The app is *very* tied to Google Reader backend, which means that giving proper support to another service would require a very significant amount of effort.
I am very thankful to all my users (especially the ones who donated and gave feedback!), but I hope you can understand the reasons behind this decision - continuing to work on this app would require a major rewrite and too much time trying to (once again) and make the pieces all fit with "spit and glue".
If you are interested in any future app I might develop, you can be notified about it by sending me an e-mail using the button below. You will know beforehand of any project I might be working on (and maybe even receive an alpha/beta version of it?).
Thank you again - and hopefully this won't be the end
The Developer
Click to expand...
Click to collapse
Those who have used the app please voice your support to continue the project as I have emailed the developer the link to this thread.
(Flow Reader dev here)
Right, here's what's going on:
Personally, I'm not very happy with any of the current readers on the Play Store, so the idea of building the next iteration of Flow Reader is one that I really enjoy. Unfortunately, I simply don't have the time that I would need to keep developing it any further. I now have a full time job and not much patience to keep working on the app on my spare time.
The thing is, I have several unique ideas that I believe would greatly improve the experience of Flow Reader. Actually, some of these already graduated from just ideas, as some prototyping is already done and working. I also think there is a decent amount of money that could be made from them, so I'm not very willing to just leave them out in the open.
The fact is, though, it is very unlikely that I'll ever finish this new version of the app that I'm building. I can see two options right now:
OPTION 1 - The cooperation route:
- I will pair with another developer (or a small group of developers). Bear in mind that the code is reasonably complex, so i'd rather work with someone that feels confortable around code.
- The code of Flow Reader will remain closed, but shared with the people that want to be part of this project;
- I will take care of the things that I believe to be my greatest strength: UIX and prototyping. But I will always be open to suggestions on these areas.
- The profit of the app will be split 25% (for me) and 75% (for the other developer(s)).
OPTION 2 - The free route:
- I open up the code of Flow Reader under the condition that it will forever remain open-source and free (under an attribution, no derivatives and no commercial use licence).
- I will no longer will have any direct input or cooperation on the app.
Also, I honestly think it would be better to start the app from scratch. The code is a complete mess right now so trying to build more features upon it would just be less efficient. Still, some techniques and code used in Flow Reader could be reused to save some time.
Choices
I have been a user of Flow Reader for some time and was really sad when it stopped working and that the dev stated that there was no longer going to be updates to continue after the demise of Google Reader.
That said, I totally agree that it should be continued into the post-Google Reader era of RSS news. I originally created a post on Reddit in which I stated that for the continuality of Flow one idea would be to open source the code on a git site to allow others to progress his work further.
Understandably this poses the risk of Flow Reader loosing it's (work)Flow. All that time and effort the dev put in to creating a stunning, and above all easily functional, UIX could well be lost. On the other hand the simplicity of this RSS reader coupled with its parallel article downloading feature would live on and enrich many an Android RSS fans.
So here I am on XDA, stating my opinions for the two options presented.
For the Closed Sourced Approach:
The idea of sharing the workload will mean that whoever is chosen to work on Flow Reader will most likely have a great deal of knowledge to input in to this project. It also means that the UIX will not change without considerable thought first. This I applaud.
The fact that the developer says that the proceeds of the app will be divvied up indicates to a paid app, further indicating to (hopefully) a group of developers with the incentive to push great work "out the door".
For the Open Sourced Approach:
The hands of many a developer could make this app into something even better than it already is....
...or it could ruin it with out the guidance of the one who had the vision in the beginning.
Usually in the open source community when there is a bug and/or a missing feature, if someone with the appropriate know how can fix it, it shall be done.
A question, then, to WildMoves. Would those who have donated need to pay again once it arrives back on the play store? That is if you are going to make it a paid for only app?
Either way, with the way that Flow Reader handles feeds I honestly have never, and believe never shall, discover one better. To which I would like to say that no matter which direction the dev goes, I will support and give as much feedback as I can.
Again, great work mate and keep on coding,
Skinna a.k.a Skinnx86
Skinna said:
I originally created a post on Reddit in which I stated that for the continuality of Flow one idea would be to open source the code on a git site to allow others to progress his work further.
Click to expand...
Click to collapse
Yes, when I posted my answer I was still trying to develop the next iteration of Flow Reader. I built a prototype to test several ideas before I came to the realization that I couldn't build the full app the way I wanted to in a feasible amount of time and still... well... live. :\ So I am now receptive to offset most of the workload to a developer or group of developers (hence the 25/75 profit split).
Skinna said:
A question, then, to WildMoves. Would those who have donated need to pay again once it arrives back on the play store? That is if you are going to make it a paid for only app?
Click to expand...
Click to collapse
I have the email addresses of everyone who donated, so I could probably create a mailing list to deliver full versions of the (paid) app outside the Play Store. Assuming that I would have the approval from the other developers, it would be a good sign of gratitude to those who donated, IMO.
Reasonable Thoughts
Well a man has to live. To spend your free time developing and building something you would expect some payback of some sort. But thank you for remembering us early adaptors. I know I for one will be thankful, I can but imagine others will be too.
As much as I was appreciative of the beta's being sent to us, but in case you did not hear, Facebook updated some peoples app out side of the play store. Now Google have banned out-of-market beta testing. I believe that sending an apk to install initially will work and should update through the play store correctly.
A few weeks ago, I posted a very unfortunate Google+ post of the creator of Focal and why it was removed from the CM codebase. It was a depressing story and it really started to make you wonder about where CM is going.
This time, after reading an extremely well-written article, I've come to a similarly depressing conclusion: Android by Google is slowly becoming as locked down as iOS, but not in the sense that you think; it's not about what apps let you do what, it's the developers.
We've finally arrived at a critical flaw with the way Android is developed and these days, I can no longer claim that Android (by Google) is "open" anymore.
Feel free to give this a read (Disclaimer: I am not affiliated with Ars Technica in any way).
http://arstechnica.com/gadgets/2013...ntrolling-open-source-by-any-means-necessary/
It's not just about Amazon's version of Android; CyanogenMod is for all intents and purposes a "fork" of Android. It is designed to work without Google Apps and as we all know, we flash those seperately. But that's the problem, the answer isn't just "Well, I'll just flash the Gapps and it will work like it should". What will happen if new Play Store apps start referring to features in the framework that don't exist in a form that we can flash? What if the license to flash the Gapps gets revoked?
How will CyanogenMod start adding features to apps that were originally AOSP but are now closed source? What will happen when the open source Messaging app is abandoned and turns into a Hangouts feature? How can CM stay on top of that?
It's not as simple as "take the source we currently have and work with it", because what will happen when Google adds a killer feature to an app that depends on some API that is no longer open source?
These are some rather frightening questions to deal with. I don't know where Android is going, but I'm certainly starting to wonder what's going to happen to it.
I'd appreciate any and all input on this.
Not very continuous, but here's my thoughts about the article:
The Gapps license is meant to lock the makers of Android phones into Google, so users get locked within Google and Google can gain revenue from the users. After going to that extent to make sure Google gets to keep the device's user, what's to gain if Google users of the device who flash CM to be locked out of the system instead of keeping them "trapped" with the Google ecosystem even with a non Google ROM? Doesn't make any sense does it?
I suppose we will still have to flash them like we flash the Play Store now. Unlike Amazon, CM (for now) actually still relies on Google and doesn't "divert" revenue to another company and therefore Google would be more than happy to let their apps be used. But if CM does start going the Amazon way, I believe Google may lock CM out.
Those APIs take time to develop, take the Maps API for example - you think they spent millions, if not billions mapping the entire world and even roaming every street just to make sure you can find your way around for free? They'll need to recoup their costs somehow.
While Android is open source and contributed by Google for free, don't forget Google is a company, not a charity. They have to make money or their shareholders won't be happy. Even if their shareholders are massive fans of open source they also have thousands of employees to pay, and all that costs money. And don't forget, when a company is providing free stuff for you to use, you are not their customer - you are their product. Android will change in ways that will keep Google profitable and keep competitiors unprofitable, while keeping the users as comfortable as possible so they will continue to be their product.
cccy said:
Not very continuous, but here's my thoughts about the article:
The Gapps license is meant to lock the makers of Android phones into Google, so users get locked within Google and Google can gain revenue from the users. After going to that extent to make sure Google gets to keep the device's user, what's to gain if Google users of the device who flash CM to be locked out of the system instead of keeping them "trapped" with the Google ecosystem even with a non Google ROM? Doesn't make any sense does it?
I suppose we will still have to flash them like we flash the Play Store now. Unlike Amazon, CM (for now) actually still relies on Google and doesn't "divert" revenue to another company and therefore Google would be more than happy to let their apps be used. But if CM does start going the Amazon way, I believe Google may lock CM out.
Those APIs take time to develop, take the Maps API for example - you think they spent millions, if not billions mapping the entire world and even roaming every street just to make sure you can find your way around for free? They'll need to recoup their costs somehow.
While Android is open source and contributed by Google for free, don't forget Google is a company, not a charity. They have to make money or their shareholders won't be happy. Even if their shareholders are massive fans of open source they also have thousands of employees to pay, and all that costs money. And don't forget, when a company is providing free stuff for you to use, you are not their customer - you are their product. Android will change in ways that will keep Google profitable and keep competitiors unprofitable, while keeping the users as comfortable as possible so they will continue to be their product.
Click to expand...
Click to collapse
First, I appreciate the input! I was looking forward to intelligent discussion and it's great that the first reply is just that.
I would like to clarify though; my concern is not so much about Google making money; they are a business and deserve to make money in whatever way they see fit. We have something they want (ad clicks and search history) and as long as they provide an experience worth using, I don't mind that transaction at all.
My worries start with what the custom development scene will look like one or two years from now if the base apps that make Android useful on its own (and by extension, useful to custom developers) have been molded into Google Play apps or frameworks or APIs.
In parallel, it's also starting to make sense why Cyanogen continues to put effort into alternate applications such as Apollo and Focal; they saw this coming way before we did.
LiquidSolstice said:
First, I appreciate the input! I was looking forward to intelligent discussion and it's great that the first reply is just that.
I would like to clarify though; my concern is not so much about Google making money; they are a business and deserve to make money in whatever way they see fit. We have something they want (ad clicks and search history) and as long as they provide an experience worth using, I don't mind that transaction at all.
My worries start with what the custom development scene will look like one or two years from now if the base apps that make Android useful on its own (and by extension, useful to custom developers) have been molded into Google Play apps or frameworks or APIs.
In parallel, it's also starting to make sense why Cyanogen continues to put effort into alternate applications such as Apollo and Focal; they saw this coming way before we did.
Click to expand...
Click to collapse
I believe the custom development scene wouldn't get affected much. After all, remember the old XDA-Developers? Windows was all locked down, but the cooks still managed to make customized ROMs. What's more, Google wouldn't want to lose their "products" - Google wants us to continue to use their services so they can earn money, they wouldn't lock us out.
What competitors lack is the capability to access Google's services (Frameworks, APIs, etc) as Google has ways to block them (Which is why we had circumvents like device spoofing). If you had a device designed for Google's version of Android, I am sure Google would still enable access if you use a custom ROM. The point of locking those competitors out is to force them to embrace Google's version of Android and not use their own forks which would keep Google out of certain aspects of the user's phone, decreasing revenue. Therefore, if you could roll your own custom ROM, it makes sense for Google to continue supporting you so you still completely rely on them instead of "outsourcing" to other competitors.
CM puts effort into alternate applications because as you can see right now, CM's starting to roll their own commercial forked devices - what happens after that? If you have seen the ways of other commercial versions of Android (Amazon, China brands, etc), they start replacing certain revenue generating aspects of the phone to use their own service instead of Google's. Certainly not what Google wants.
In short, I would say, if you are a small custom ROM user, Google isn't going to come after you, they want you to use their services! But if you are a competing company, expect your devices to be locked out from Google in the hopes that they eventually force you to bow to them and convert all your users completely to Google's "products".
github.com/psaravan/JamsMusicPlayer
Jams is a free, powerful and elegant music player for Android. Jams used to be a trial/paid app on the Play Store. Due to my lack of adequate free time and other issues, I've decided that I can no longer provide the level of support and active development that paid users expect from a developer. Rather than letting Jams completely die off and abandoning my users, I've open sourced the app and hosted it on GitHub (see link above) to encourage other developers to potentially improve it, use it in their own personal projects, and re-release it to users.
I will still occasionally update this app based on my free time, but it will probably be beta quality code. If you are a developer who's interested in using Jams' current codebase, I encourage you to fork this repository and/or directly contribute to it. If you decide to launch your own fork of Jams on the Play Store, feel free to drop me a line so I can feature it on my GitHub page.
Just want to thank everyone who's supported Jams Music Player over the past year. It's been an awesome experience for me and I really enjoyed receiving feedback from everyone in this subreddit and elsewhere. The app has received a major UI overhaul over the past few weeks and I will be publishing the free version of the app on the Play Store in the next few weeks once I get any existing kinks ironed out. Hopefully I'll be able to find more time again in the near future to work on this app full-time.
Imgur links to the new UI:
i.imgur.com/2hdMFzP.jpg
i.imgur.com/tdLiCVY.jpg
Tl;dr: I no longer have enough free time to develop Jams in a way that justifies asking people to pay for it. The app is now open source and a free version will be released on Google Play in the next 3-4 weeks.
is ACEMUSIC is based on your code?
http://forum.xda-developers.com/android/apps-games/complete-material-design-acemusic-t2904994
unable to find any mention but even whole UI is same as of your code
Yeap, that player is definitely based off my codebase. The developer did mention my name in the "Special Thanks" section of their post.
JamsMusicPlayer said:
Yeap, that player is definitely based off my codebase. The developer did mention my name in the "Special Thanks" section of their post.
Click to expand...
Click to collapse
after thread block, he decided to add credit, now thread is reopened.
without any change in ui he is claiming to be Material design also...