[APP] FlowReader - Save this awesome RSS reader - Android General

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.

Related

[Q] Google Wave App

I just wanted to know if anyone has developed a solid app for Google wave. I use Google wave allot, but there aren't any good ones in the market place.
If someone can give me a good app for Google wave (with notifications, and updates, like the Facebook app) that would be awesome.
If no one made one yet, this is an opportunity, I need a good Google wave app so bad that I would be willing to pay for it, and I am probably not the only one.
DROID_INC said:
I just wanted to know if anyone has developed a solid app for Google wave. I use Google wave allot, but there aren't any good ones in the market place.
If someone can give me a good app for Google wave (with notifications, and updates, like the Facebook app) that would be awesome.
If no one made one yet, this is an opportunity, I need a good Google wave app so bad that I would be willing to pay for it, and I am probably not the only one.
Click to expand...
Click to collapse
You probably are actually, google wave is very unpopular. I doubt you'll find one if i'm honest !
Good luck anyways!
edit: go to www.googlewave.com in your mobile browser, should be a mobile version? Not sure if that's any help though.
Wave Lives!
I think Wave is popular amongst certain developers (the kind that were let in early) but i'm not sure what it's future is now that Google has announced it's closure towards the end of the year.
On the one hand the whole wave-server is free to download and install on our own machines, but on the other hand, Google hasn't (and probably won't) release much of their native client. The "textual" client that was released was so basic as to not catch on for "syndication", or "federating" as it was called. I got as far as setting it all up on a VPS hosting, but wasn't up to the task of coding my own client, at least, not at the time. (thou i would've joined such a group if had found one, which i didn't)
I still see a future for Wave, or a derivative thereof, but the original Wave client would be hard to replicate if Google choose not to release it. Until we hear what Google intends to do with that "popular" client, it's really anyone's guess.
For myself, i was gearing up to code an Android client for Wave using Adobe Air once they (Adobe) have finalized the feature-set (it's still in pre-release for month or two). I would still like to do this, but getting it to the quality of the current Wave client would be large undertaking. Would prolly have to settle for something that looks and works a bit differently. (ie. more suiting Android screens for example)
As for a central server to run it on (since Google are pulling the plug) it would need to be either another central server, or at least partially shoe-horned to run on Google's App Engine, which i have also done some prep work for. (passing waves thru as a web interface, storing of waves in big-table, etc)
Along with character-by-character communication, and having compatibility with existing robots and gadgets (protocols, and everything) it's quite an involved project. Most likely a team effort, which is what Wave is actually designed for after all. ;O)
The only tricky part is getting paid to even attempt it. So even thou there's definitely some latent demand for Wave to continue, method of sponsorship is what really needs to be sorted out first. See my previous post (here on XDA) about "donation bidding" for example of what is really needed.
This is the one i meant... "Developer Bidding"
Ok, thanks guys.
I have used the mobile version but it just plainly sucks. Since I go to college, I do a lot of group projects and its easier through google wave because your group can comment attach, post, etc..., and your entire group can see and discuss. If google is pulling the plug, is there any alternative I can use for what I am doing?
Again thanks for the help.
A popular one before Wave came along was Etherpad (Etherpad.com) but as Wave was gearing up for public release Google bought the company, shut down Etherpad, and got the Etherpad team to help the Wave team improve Wave's usability.
Initially there was a public backlash, since the two services looked and worked quite differently, and many people preferred Etherpad's simplicity. Perhaps because of the growing backlash, Etherpad was then quickly released as open-source (see Etherpad.org) such that it can be downloaded and setup on your own server.
When Google announced Wave is closing, several sites promptly listed some alternatives.
http://www.techmaish.com/5-popular-google-wave-alternatives/
http://www.worldtech24.com/business/10-great-alternatives-google-wave/
Also worth noting that although Google are closing Wave, they are now planning to integrate some of the Wave's technology (whatever that means) into existing products. Think of; google mail, google buzz, google talk, and google voice, all becoming something "more collaborative" and generally more social.
Personally, i liked Wave the most (robots, gadgets, etc) so hoping to catch the timing between Air for Android releasing, and Wave closing, since my background is mainly Actionscript/Javascript, and have already coded a partial client.
Happy hunting thou!

[CLOSED] [Q] phone creeper alternative for android

Hello.,
does anybody know if there is a program for the android similar to teh phone creeper for wm6.5
the phone creeper allow easthdropping on phones, phone calls phone locating and so many other features as posted here
http://forum.xda-developers.com/showthread.php?t=527423
so ......
does this mean, nobody knows or there is no such software?
Im wondering the same thing
Sent from my HTC Vision using XDA App
What does "easthdropping" mean?
By the way the MIUI Phone.apk is able to geo-localize the calls, even if it works in China only (AFAIK)
I'm the developer for the phone creeper and will be launching the android version very soon, however it will be very different. The problem with and hurdle for creating the same functionality on android devices is that (at least that i'm aware) there is no way to completely hide an SMS message from phones. You can instantly read it and delete it as with windows mobile, however there will still be an sms arrived alert in the status bar.
To get around this hurdle i've created a website with a database and webpage front end that will allow for all communications to happen with a combo of SQL and Android Cloud to Device Messaging (C2DM). This will allow for a small footprint quick silent communications. However this also means I need to support a website and database.
This basically adds a large level of complexity and creates various pluses and minuses for everybody. The program will still be free as it has always been, however some of the features and those who want to have viewing and controlling capabilities through the web will be charged a slim fee.
The program will still be completely functional and useful without paying a dime but hopefully enough people will want the extra goodies to pay for the web hosting.
As I said it's mostly complete now and hopefully I'll have a release published here shortly and allow for free web viewing trial also.
chetstriker said:
I'm the developer for the phone creeper and will be launching the android version very soon, however it will be very different. The problem with and hurdle for creating the same functionality on android devices is that (at least that i'm aware) there is no way to completely hide an SMS message from phones. You can instantly read it and delete it as with windows mobile, however there will still be an sms arrived alert in the status bar.
To get around this hurdle i've created a website with a database and webpage front end that will allow for all communications to happen with a combo of SQL and Android Cloud to Device Messaging (C2DM). This will allow for a small footprint quick silent communications. However this also means I need to support a website and database.
This basically adds a large level of complexity and creates various pluses and minuses for everybody. The program will still be free as it has always been, however some of the features and those who want to have viewing and controlling capabilities through the web will be charged a slim fee.
The program will still be completely functional and useful without paying a dime but hopefully enough people will want the extra goodies to pay for the web hosting.
As I said it's mostly complete now and hopefully I'll have a release published here shortly and allow for free web viewing trial also.
Click to expand...
Click to collapse
this is great news, let me know if you need testers
also can we have links to the site,
i'm a web designer and php programmer, i can give you feedback if you need
smartechno said:
this is great news, let me know if you need testers
also can we have links to the site,
i'm a web designer and php programmer, i can give you feedback if you need
Click to expand...
Click to collapse
That would be wonderful, I usually only create desktop and mobile applications. I don't have that great of an artistic eye and have rarely created any web sites. Currently I'm also using PHP for the website and will probably have to switch from godaddy hosting since they seem VERY slow at hosting any web pages containing scripts.
Maybe you can help me figure out why the logo seems to get cut off in IE6 (looks fine in other browsers.) it appears that displaying the bars are cutting it off since if I disable them it looks fine.
The link is xxxxxx Mod Edit: Link removed.
Whow, talking about privacy and espionage here
In general, Software like this is greatly coded, and requires alot of skill.
But on the other hand, if you use this App to watch / control somebody elses phone, is really awkward... I would be scared to know that a program like this exists and could be activated silently on my phone...
Just my 2 cents, but respect to the one who is able to program such a tool!
how about totalcare?
http://forum.xda-developers.com/showthread.php?t=835603
badai said:
how about totalcare?
http://forum.xda-developers.com/showthread.php?t=835603
Click to expand...
Click to collapse
totalcare is a nice project, but the main differences are:
OverVi3w can be controlled via a webpage or sms.
Overvi3w has many more features
Overvi3w is actually stealthy, unless something is different about totalcare since last time i'd seen it. The message may be instantly deleted, however when you look at the sms history it would still show that it arrived even if you couldn't open it. although you still could see the command and from who is sent.
Overvi3w allows the phone to be controlled from ANY other phone or from the web console. It still uses a password for protection during sms control and to use the web interface it requires the imei (gsm phones) or meid (cdma phones) for extra security.
Anyway, I should be accepting alpha users later this week.
wow it's already have a name. OverVi3w. can't wait. total care just doesn't work on both my phone (gingerbread and froyo).
your phone creeper really great. works even after flashing new rom.
you misspell register on your website.
badai said:
you misspell register on your website.
Click to expand...
Click to collapse
Thanks.. how embarrassing for me.
I've created a new thread on XDA for anyone interested in becoming an Alpha tester.
http://forum.xda-developers.com/showthread.php?p=14113648#post14113648
The predecessor to phone creeper on windows mobile 5 or 6 years ago
Hi you asked foraan phond creeper program for win mobile 3.5 look for phone creeper or espionage suite .cab and if that cant be found look up phone leash for android and if nothing there is appealing look up blooover.cab its a java thing and works well with winmobile and theres newer **** for other platforms.
chetstriker said:
I'm the developer for the phone creeper and will be launching the android version very soon, however it will be very different. The problem with and hurdle for creating the same functionality on android devices is that (at least that i'm aware) there is no way to completely hide an SMS message from phones. You can instantly read it and delete it as with windows mobile, however there will still be an sms arrived alert in the status bar.
To get around this hurdle i've created a website with a database and webpage front end that will allow for all communications to happen with a combo of SQL and Android Cloud to Device Messaging (C2DM). This will allow for a small footprint quick silent communications. However this also means I need to support a website and database.
This basically adds a large level of complexity and creates various pluses and minuses for everybody. The program will still be free as it has always been, however some of the features and those who want to have viewing and controlling capabilities through the web will be charged a slim fee.
The program will still be completely functional and useful without paying a dime but hopefully enough people will want the extra goodies to pay for the web hosting.
Click to expand...
Click to collapse
chetstriker said:
As I said it's mostly complete now and hopefully I'll have a release published here shortly and allow for free web viewing trial also.
Click to expand...
Click to collapse
i would be happy to donate and help out where do i go to donate and how long do you think until the program is ready.
where do i go to donate
MOD ACTION:
Thread closed since it violates Rule 16 just like the linked thread in the OP which has also been closed.
@cindyloulou
Do you realise that this is a 12 year old thread with the last post in 2014? And please do not create multiple posts within a short time, instead edit your previous post if you need to add some info.

Ars: Google’s iron grip on Android: Controlling open source by any means necessary

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".

[APP] Looking for Android alpha testers for a money tracking application I created.

My main goal for this project was to keep the application simple, yet effective. I don't like cluttered applications, however, I like ones which get things done! My new application "Simple Register" for lack of a better name, is just that (in my opinion.)
It functions similar to a checkbook register, where you can easily track your money. You can set an initial starting balance if different than $0, and from there credit money or debit money from the account. There is no linking to bank accounts or anything of that sort. I wanted to keep this simple.
I am looking for some Alpha testers who track their expenses and who are willing to give good feedback in order to improve the application. It is definitely not complete in terms of features, which is part of the reason I am here. I know there are things which can be added, that don't make the application too complex, yet can improve the overall experience.
The UI is currently not the best as I have tried to devote more time to functionality and have not had a chance to get around to making it look "pretty" yet. I will say, however, it is not by any means ugly. It is simple looking, which should make it extremely easy for someone of any skill level to use!
With that being said, I want to reach out (with this post) to get a few Alpha testers. I have an Alpha community setup through Google+ at the moment which will give you access to the Alpha version of the application through the Google Play Store.
If you are interested, please join the following Google+ community, which will provide the link to sign up for the Alpha testing (through google) and allow you to download the application. Membership will be limited (so that I do not get overwhelmed with users and feedback) so if you do not get in right away, please be patient.
Simple Register Alpha - Google+ Communities
In the future, I plan for there to be a paid version of the application (this may change.) Currently I am limiting the number of accounts someone is able to create, and there are a few more features I am planning which would be in the paid version. Those who have helped test the application, will be provided the paid version free of charge.
Thanks in advance!

[APP] REALTOR.ca App - The Non-Official Discussion

Hi guys,
Just curious, anyone uses REALTOR.ca app in Android here?
Because, here's the deal.... I'm actually the analyst for our app development and we're doing some major revamp to that app.
Now, a little disclaimer: the purpose of this thread is solely to discuss feedback on the app (I'm not a REALTOR(R) and will not be able to answer real estate questions), and my posts does not reflect my employer (Canadian Real Estate Association). This is a very non-official thread, so to speak.
A little background; we just rebuild our iPhone app into 2.0 and the feedback has been... lacklustre lol... Some thinks it's awesome, but others (most?) just want their old app back. Now, I personally want to engage the users more to avoid the pain with our Android app, but due to legal issues, business decisions, etc... I cannot create an "official feedback channel". So if you can somehow "forget" I'm an employee with CREA, please feel free to say what you think about the REALTOR.ca app.
Thanks folks
PS: What's in the works for now for Android 2.0
- Google Map (no more Bing Map) (this will solve all you KitKat users issue with the loading crap)(did I just say crap...? No I didn't...)
- Updated layout. More intuitive, side slides menu, better home screen, simplified filters (but advanced still there).
- Tablet support. Auto-detect device and display accordingly.
- New Near Me functions, new Open House functions, notes, notifications, etc...
- a bunch of bugs. Seriously, a lot of it. So much that we're thinking of releasing another update in the interim to address them.
PPS: If anyone in the real estate market and wants to know what I'm talking about, it's this: Play Store
PPPS: I don't think this app is "commercial", since it's free and stuff... but if I'm wrong, please feel free to delete this thread, mod. Thanks.

Categories

Resources