A while back someone asked which phones the Windows Mobile team uses. While I will end up answering that question, in typical form, I’m going to be really verbose about it.
In Windows Mobile, we’re very strong proponents of what we call, “Eating our own dogfood.” What this means is that we use the code we’re developing on our primary phones. If you’ve ever been on a “Beta test,” you know that beta code isn’t always very stable or bug free. Well, we frequently use builds that aren’t even up to beta quality. When internal people complain about this, my response tends to be, “They don’t call it dogfood because it tastes good.” We dogfood (it’s a verb too to find bugs. Better it be unstable for us than for you….
Here is the whole article
http://blogs.msdn.com/windowsmobile/archive/2007/05/04/dogfood-doesn-t-always-taste-good.aspx
I am starting this thread in the hope we can discuss the Google Plus service. There are some other threads out there, but are slammed full of invite requests, and no discussion is actually occurring, so please, no invite requests of any kind.
I personally love this service so far, I think it will be a [email protected] killer in very short order. I especially like the way Circles is set up.
Since it's a closed beta atm, there's no one that I know personally with an account. This means all the great things I used Facespace for I can't play around with yet. I guess I can set up my profile and keep looking around for the next three weeks.
People that got accounts are already getting bored of it because their friends can't join. It's like being the only person with a cell phone - who are you going to call? You log in and click around for ten minutes, then you log back out. No point in posting anything - nobody can see it. Nothing to read, yet, either.
If Google doesn't open it up soon, it's going to die like Wave did. The early adopters will use it for a few days and move back to Facebook where their friends are. People will gradually get invited in, only to find the ghost town left after the early adopters abandoned it. Time will pass and people will forget that they were waiting to be invited.
This Google-coined idea of the "invite-only" service worked for gmail because you didn't need a community to use email - you could still message hotmail and msn email users. It doesn't work for anything that requires community (like social networking definitely does).
Se7enLC said:
People that got accounts are already getting bored of it because their friends can't join. It's like being the only person with a cell phone - who are you going to call? You log in and click around for ten minutes, then you log back out. No point in posting anything - nobody can see it. Nothing to read, yet, either.
If Google doesn't open it up soon, it's going to die like Wave did. The early adopters will use it for a few days and move back to Facebook where their friends are. People will gradually get invited in, only to find the ghost town left after the early adopters abandoned it. Time will pass and people will forget that they were waiting to be invited.
This Google-coined idea of the "invite-only" service worked for gmail because you didn't need a community to use email - you could still message hotmail and msn email users. It doesn't work for anything that requires community (like social networking definitely does).
Click to expand...
Click to collapse
+1 Couldn't agree more. If Google don't get a move on this will die faster than than a Sinclair C5
I like Google+ ... I like the concept of Friend circle .. It has good potential
It's a beta, not open to public. It is this way, for testing purposes, and for bug reporting. It has numerous bugs, and basically, annoying things that it does.
I'm sure when it's polished, it'll be released to the masses. I'm pretty sure those with it are thankful for having a new toy to play with, even if it is limited.
With the above said;
It's fantastic in concept. The ability to have group chats, group voice/video with chosen circles, etc, is a Facebook killer.
A bunch of my friends and I are on g+, and it's all we've been toying around with. Hangout and Huddle are probably the best features.
Since not many people use the service, we've been treating g+ like twitter where we follow complete strangers with interesting posts just to occupy the stream..
Se7enLC said:
People that got accounts are already getting bored of it because their friends can't join. It's like being the only person with a cell phone - who are you going to call? You log in and click around for ten minutes, then you log back out. No point in posting anything - nobody can see it. Nothing to read, yet, either.
If Google doesn't open it up soon, it's going to die like Wave did. The early adopters will use it for a few days and move back to Facebook where their friends are. People will gradually get invited in, only to find the ghost town left after the early adopters abandoned it. Time will pass and people will forget that they were waiting to be invited.
This Google-coined idea of the "invite-only" service worked for gmail because you didn't need a community to use email - you could still message hotmail and msn email users. It doesn't work for anything that requires community (like social networking definitely does).
Click to expand...
Click to collapse
+2. I've been in for about a week but can't get anyone else in. so I set up my profile. play around with it but without guides or others to interact with I'm already beyond bored with it.
Also since I don't have any friends on it, I disabled the account sync feature in the system setting but whenever I come back in an hour or so, it auto enabled itself? SOB! I deleted the app.
I really want to use group chat on here, but my friends aren't on this service...I hope it grows.
romedundun said:
Since not many people use the service, we've been treating g+ like twitter where we follow complete strangers with interesting posts just to occupy the stream..
Click to expand...
Click to collapse
how do I even find other peoples posts? The only thing I can find it my failed invite attempts on my stream.
Youll see others ppls posts that are directed to the circle they have you in. If you see nothing, you either have no friends, or they have not shared anything with you.
For instance, I have many circles (groups of ppl), when I post an article/status, I can choose which group(s) to post it to, or indeed, post it publicly. A certain person can be a member of multiple groups, as well.
Perhaps take a look at "sparks" for people/sites to follow.
As said prior though, this IS a closed beta. It has not been released at this stage as a replacement for your favourite social sites. If indeed youve been lucky enough to get an invite, then treat it for what it is. A testbed.
Sent from my Dell Streak using XDA App
So far I am liking g+. I think it has a lot of potential, but like others have said it wont show its full capabilities until everyone can join at will. I don't even want to try adding any non-techie friends because I'm worried that the crappy invite system would annoy them and scare them off. The circles are an awesome idea, but my favorite part so far is the ability to have it upload my pics and videos automatically from my phone. Not only does it make it extremely easy to post them anytime you want, it also works like a cloud service to back them up and you can access them from your computer too.
Sent from my GSB Eris
The group chat seems to have a lot of potential.. I been wanting something like bbm but nothing was really all that known to other ppl. Hangout looks good too. I cant wait.. Google needs to hurry up and release this.
Sent from my demonSPEED! Glacier using XDA App
check out socialstatistics.com if you wanna follow people..
This is still a beta test so its a little slow, once Google feels that most of the kinks are hammered out they will make it public.
That's when the flood will open.
I think Google will start packaging G+ as a stock Google-app that will be on all newer android devices. since there are a reported 500,000 android activations daily which means that's 15 million new people in a month. Compared to facebooks 750 million current users its not much, but at that 500k rate could dominate facebook in 4 years.
I have this feeling that G+ may be ready to go public in August
Engadget Article
It turns out that Google will boot all non public profiles after July 31
Facebook just announced group chat, and video chat. http://on.fb.me/pKBugz
Competition is indeed a good thing. No matter who wins the battle of supremacy, we'll all come out winners
Edit: This is a pretty decent review of Google+;
http://bit.ly/qfNrcX
Sent from my Dell Streak using XDA App
I have been using G+ for only 3 days. I think the circle setup is very nice, and the huddle service is a huge jump from facebook. However, I do think that we have to wait until there is a huge increase in the number of user of google+ to see how it compares with facebook. I have only 20 people in my circles. My friends are all reluctant to move over.
I have a feeling that this might become a part of stock android ui as it integrates into your contacts pretty deeply...
Sent from my HTC Sensation Z710e using XDA App
Anyone having issues with notifications when Google+ unloads itself from the memory? Notifications won't pop up until you open Google+ again. Not an issue with regular notifications since I get an email notification on those. But with Huddle, it kind of defeats the purpose.
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.
I have an HTML 5 app built with Sencha Touch + Cordova. The app works ok and is already in production, but I want more in terms of performance for the future, so I'm thinking about rewriting it in another framework.
On propertycross.com some of the most used cross-platform frameworks have been compared... I went through all of them and for me the winner is with no doubt NeoMAD. The approach seems the right one: write in one language (Java) and have the native app generated for each platform.
I saw no difference in terms of performance between the native one and the one built with NeoMAD, also the app was only a bit larger (1.2mb the native one, 1.9mb the one built with NeoMAD), with Titanium and Xamarin I get an app 10 times bigger, not to mention the increased startup time.
By doing some research on the web though, NeoMAD doesn't seem much used... on stackoverflow I get only 5 questions with the neomad tag.
So why so few people use this framework? Seems to me the perfect one... Does anyone have any experience with it?
Hello Emanuele,
First of all, as one of the NeoMAD founders I was very happy to read your post!
To answer your question, I think there are 3 explanations:
1/ NeoMAD is available on the market since 2012 only and this is a first objective reason why we do not have a lot of users at the moment.
2/ Neomades is a small company with limited marketing resources compared to our main competitors.
3/ The Neomades team is mainly a tech one and we have not been so efficient until now in business dev.
However, NeoMAD is used for mobile developments by major french organizations such as CROUS, L'Oréal and TNS Sofres / WPP Group. Some of these applications are available on the app stores, you can find more information about it in the References section of our website.
We hope that comments like yours will catch the community's attention and increase the visibility of NeoMAD… without users and the developer community we will not succeed !
Fill free to contact us for any questions a [email protected]
Best regards.
Hey @memanuele
First of all, you need to choose the framework according to your specific project needs. It's really hard to name the one-fits-all framework. If you're in no hurry, you can spend some time trying different ones and thus deciding what will be the best variant for you.
If you don't have time, you can get initial information from the blogs, for example, here or here, to name a few. Google it, there's alot of interesting going on.
Edit: Ddamn, just noticed the date of the initial post...
Good news for the open source crowd.
Google's Android developers head to the blog today to let us know it has migrated the AOSP issue tracking system to use its own Issue Tracker software.
Issue Tracker is the tool Google uses internally while building and maintaining all the various stuff it does. It's also the public facing bug tracker for many of its other products, including the Android O Developer Preview. The new system looks and feels very much like Google Groups, and Google says this makes it easier for everyone to be on the same page when it comes to finding and killing bugs.
We are hoping to facilitate a better collaboration between our developers and our Android product teams by using a tool we use internally at Google to track bugs and feature requests during product development.
Issue Tracker also uses standard Google terms of service, so be sure to read what you are agreeing to the first time you use the service.
For most end users this has zero impact. But know that the people developing Android and fixing the inevitable bugs should now be able to better communicate. Everything works better when everyone involved knows what's up.
We don't need copy/pasted articles here, with no credits or source. That's called plagiarism. :good:
Thread Closed.