Hmm, I just updated to Slideme 3.41, keeps FC while loading catalogue. I un-installed and installed it again, same. I'm on Modaco 3.2.
Based on the forum posts on slideme, it looks as though they had a bad update about 5 days ago. This update doesn't work on Android 1.5 devices, and a number of 2.x ones as well. On some other devices that it still works on, a lot of missing apps. I'm not sure when or if they will issue a fix.
The problem is related to a 1.5 issue.
There is no FC on 2.x
sisbell is simply personally attacking us as an ex team member. Ironically, he was involved with this product in the past and we've been fixing all his mess.
We will patch this as soon as we finish our testing, most likely tomorrow.
re: catalog updates, apps populate as they're being fetched when you enter each category.
If you need a version today, you can get the 3.4 also from site.
Excuse that we did not test thoroughly on 1.5's before a release.
I fail to see how this is a personal attack. I'm just giving a user a quick rehash of what I picked up on the forums and twitter. If SlideME is not testing its releases, how is that my fault?
For anyone who is interested on the issues, here are some relevant links:
Android 1.5 - Crashes
http://slideme.org/application/slideme-marketplace#comment-783
Android 1.6 - listings out of date
http://slideme.org/forum/developer-discussion/device-listings-way-out-date
Android 2.x - compatibility problems
http://slideme.org/forum/general-discussion/application-compatibility
You're definitely monitoring anything mentioned about us and first to post a negative comment anywhere on the web - and you claiming you're not personally attacking or just wanting to damage..? How did you manage to post here? When was the last time you posted on XDA? When was the last time you used your twitter, http://twitter.com/sisbell ?
It seems you got nothing better to do, than follow what we do or what is mentioned about us.
Not to mention that most of the issues are due to your own crappy code you left behind, being cleaned up.
I think we have better things to do and I hope you have too as a grown up.
SlideME said:
You're definitely monitoring anything mentioned about us and first to post a negative comment anywhere on the web - and you claiming you're not personally attacking or just wanting to damage..? How did you manage to post here? When was the last time you posted on XDA? When was the last time you used your twitter, http://twitter.com/sisbell ?
It seems you got nothing better to do, than follow what we do or what is mentioned about us.
Not to mention that most of the issues are due to your own crappy code you left behind, being cleaned up.
I think we have better things to do and I hope you have too as a grown up.
Click to expand...
Click to collapse
Wow, I was just answering someone's question, I didn't expect to get hit by a troll. Don't bothering trying to bait me, this is my last post on this thread.
Hi there!
I opened up this thread to discuss the pros and contras of making up some bad press for Samsung on the s3 and, this is very important, to get clear about what they clearly did wrong with this community.
This isn't to be about what you may wish but what would really make sense and isn't their.
So let me go into detail about my knowledge that forced me to open this thread (correct me if I'm wrong, please!!)
- there should have be a very huge step in performance and ui response from ICS to JB on the s3 like happed on nexus
- also their are quiet a few things missing to bring project butter online on CM10:
codeworkx said:
What do we need?
We need sources for (sorted by priority):
- omx plugins (ICS compatible codecs for use with MFC5.X)
- camera module (camera.exynos4.so)
- audio modules (audio.primary.exynos4.so, audio_policy.exynos4.so)
- RIL header files (.h files)
- GPS header files (.h files)
- hwcomposer or at least the header files (hwcomposer.exynos4.so)
- sensor module (sensors.exynos4.so)
- gralloc and ump (gralloc.exynos4.so, libUMP.so)
If it's not possible to release some sources because of NDA's, then at least header files, interface documentation or instructions how to use Samsung proprietary files (binarys) with AOSP.
Now someone has to start a petition and advertise it. I'll not do because this will steal more of my non existing freetime.
Click to expand...
Click to collapse
my thoughts on this (fell free to comment that): My theory is, that Samsung was lazy to implement PB into their ROMs and because of this there is simply some lag of documentation because it is simply missing. So IF WE could show that there is no improvement on the official roms which should have come with PB, it could force Samsung to finally bring PB online. From that point it would be no big thing for Samsung to give us the missing documentation and sources.
As I wrote above to do this we need some hard facts. And this facts must be as simple as possible that also NONDEVs would understand it.
I heard some rumors about an video which show exactly that. That would be nice!!
Beside that every legit evidence is appreciated!!
AFTER ALL:
Some person, I could to that (did that before with origin), would set up a facebook-site which shows this whole evidence. After that all the only thing we would have to do is to get as much likes as possible and confront Samsung with that.
What do you think??
PS: As you may have noticed I'm not an english native ... so please if we do this at least get the language right!
Why not contribute to this thread: http://forum.xda-developers.com/showthread.php?t=1925709
Instead of opening a new one for the exact same thing.
I searched for project butter! for me it wasn't clear, still not is, that your thread is about the same reason! Also, as you may already have noticed, there are some big differences with this two threads...
I'm not about having my own thread but I also wanna make sure that my goal here is clear. A site to like will give the community a big number! This is way more impressive as to write down support tickets as suggested in the other thread.
There is only one 'official' test JB release so if you are not from Poland I don't think you can talk about JB on the s3 with Samsung. Also there is already ongoing initiative to get Exynos documentation and this can put any progress in risk as we are starting to spam for every thing that bothers us.
It's all in your head basically.
ICS to JB stock is not the same as ICS+Touchwiz to JB+touchwiz. For example, If Samsung didn't make any changes to the Touhwiz UX, then it could easily be touchwiz slowing JB down and not Samsung not incorporating it.
In fact, since project butter is in the JB framework, it would actually cost more money and take more time for their software engineers to disable it or create an ICS/JB hybrid. Like what would they do exactly? lock at 50fps instead of 60fps? Double buffer instead of triple buffer? Why would they possibly do that? If they did that then they might as well not use JB at all.
So moral of the story. YOU BE TRIPPING and should just get a Nexus device.
It honestly sounds like people do not like how many animations Touchwiz has and want to blame something so they blame Samsung for not incorporating project butter when there is no reason why they wouldn't.
?? OP - there is no official JB release for you to moan about just yet.
My polish release version is running fine.
I have a nexus S running official JB...believe me it flies on our new SGS3 in comparison.
I think you need something more important to start a major campaign about...I'm convinced Snicker bars don't contain as many nuts as they used to for example
mossy1963 said:
I'm convinced Snicker bars don't contain as many nuts as they used to for example
Click to expand...
Click to collapse
Jeez, and I just bought a multipack over the weekend... sneaky bastards!!!!
Frostfree said:
Jeez, and I just bought a multipack over the weekend... sneaky bastards!!!!
Click to expand...
Click to collapse
count 'em...I did...its nut theft by stealth
mossy1963 said:
?? OP - there is no official JB release for you to moan about just yet.
My polish release version is running fine.
I have a nexus S running official JB...believe me it flies on our new SGS3 in comparison.
I think you need something more important to start a major campaign about...I'm convinced Snicker bars don't contain as many nuts as they used to for example
Click to expand...
Click to collapse
Frostfree said:
Jeez, and I just bought a multipack over the weekend... sneaky bastards!!!!
Click to expand...
Click to collapse
mossy1963 said:
count 'em...I did...its nut theft by stealth
Click to expand...
Click to collapse
Typical on xda forums, satirical and cynical answers when you could give normal ones. I am not surprised that people from another forums do not like to come to this one.
Regarding the op post, I have not yet installed the official jelly bean rom but I've been reading people saying that it really seems like there is no improving reading smoothness when comparing ics and jellybean and they do blame touchwiz. If that's true I have to agree with the op even though I do not believe samsung will care about our demands.
We already have a thread discussing getting samsung to release the documentation
We do not need another one. Thread closed
Hi,
I'd like to get some very important info from Remix OS dev team.
Users unrelated to the dev team or with no android-x86 OS dev experience, please DO NOT attempt to answer these questions.
Could you please make a thorough guide on how to report bugs, suggestions, feature requests and hardware incompatibilites?
Which tools should we use to report bugs or hardware problems - be precise please. Current feedback form seems very modest and inefficient.
Except for bug description and device info should we provide a full logcat, dmesg, per-app logcat - please point out the most effective way to report this stuff.
Where should we post feature requests or suggestions?
I personally think, that e-mails or forum threads are really inefficient for this. I'd recommend using Uservoice service (https://uservoice.com) or something familiar . Example of uservoice usage in practice: https://touchpal.uservoice.com/ There are plenty of web services like these and they are very powerful and efficient.
Perhaps there is a web service that would help making an official list of supported hardware?
Remix OS, Android-x86 and Phoenix OS all base pretty much on the same ground here, so they could share same list, but none of these actually has a nice, neat tool to report supported hardware. Except for a list of officially supported devices, it's a total mess.
I know that ChromeOS with android apps support and upcoming Android releases may be groundbreaking for whole Android-x86 related projects, but if we mobilize ourselfs and use all resources efficiently, I'm pretty sure Remix OS can become very popular and liked. Devs - help us, users, help you achieve that.
Right now it seems like you don't really care about other devices compatibility or about what people may report. If you did, you would provide better tools for that in order to do your work more efficiently. Don't take it as offense, it's just cirtical point of view.
Please optimize that - this will help speed up the development process and community contact a ton.
Please reply Remix OS, Jide, @RemixOS_Cameron , @RemixOS_Guannan , @RemixOS_Jason , @RemixOS_Josh , @RemixOS_Joshua , @RemixOS_Valentina , @AmoraRei
Hey Ventricle,
Thanks for the message and the suggestions!
Currently:
We have the help center setup for general inquires as well as leaving technical feedback here: http://support.jide.com/hc/en-us/requests/new
We also have a google form specifically set up for Remix OS for PC users: https://docs.google.com/forms/d/1WMRbcwDqcoZ1vyUq68AJKCYvXBGvUIEvbgHhuySrUUc/viewform
On products like Remix Mini, clicking on the power options will allow you to "Report a problem" and then "Submit feedback". This will also send a user log along with the report.
We also actually read through almost every one of these threads for bug reports and feature requests. As for hardware incompatibilities, we accumulate a list based on the comments here as well as in our google group (https://groups.google.com/forum/#!forum/remix-os-for-pc). However, these incompatibilities are much trickier to tackle as the hardware configurations are so varied and diverse.
However, I will admit that the user feedback process can be better. We'll work on a more streamlined process, write up an easy to follow guide and then we'll post it here in XDA as well as other channels.
Thanks again for your comments. We clearly need the support of our user community as we grow. Sometimes, in the process of growing as a young company, processes need to keep getting better or else we fall behind. Appreciate the reminder and I'll drop you a note after we've created the guide.
Best,
Jason
@RemixOS_Jason that's great, thanks. I'm looking forward to your actions.
A little overhaul in this part of Remix development can have a powerful impact and spare so much time both for the devs and the users.
Wysłane z mojego Nexus 4 przy użyciu Tapatalka
@RemixOS_Jason I've just checked how feedback for Phoenix OS looks like and they're ahead of you! Anyway, this is what I think is better than just e-mails, forms and forums - http://www.phoenixos.com/feedback/page/1
Unfortunetly they don't have everything translated to English yet, but I hope this will change.
Just a suggestion from my side.
UPDATE:
Phoenix is definitely not ahead, so I take my words back. The feedback page is still a mess and all bushy (Chinese).
Ventricle said:
@RemixOS_Jason I've just checked how feedback for Phoenix OS looks like and they're ahead of you! Anyway, this is what I think is far better than just e-mails and forums - http://www.phoenixos.com/feedback/page/1
Unfortunetly they don't have everything translated to English yet, but I hope this will change.
Just a suggestion from my side.
Click to expand...
Click to collapse
I fail to see how that is any better that Jide's feedback forms form1/form2 or the submit a request
That page from PhoenixOS looks just like a nonsensical mess that there team would need a crystal ball to decipher what the posters 'issues' are.
HypoTurtle said:
I fail to see how that is any better that Jide's feedback forms form1/form2 or the submit a request
That page from PhoenixOS looks just like a nonsensical mess that there team would need a crystal ball to decipher what the posters 'issues' are.
Click to expand...
Click to collapse
It's true that the page looks a bit chaotic and as if people don't suggest anything useful (technical) to devs - but THATS BECAUSE THERE ARE NO GUIDELINES. And of course it looks like alpha state feedback page which isn't even translated to English yet. The description text area in Remix feedback form is like those suggestions on Phoenix feedback page - it's simply bad, because it doesn't hint people how they should describe things and what should be mentioned.
I didn't say Phoenix feedback is perfect, I'm only suggesting what direction is good in my opinion. TouchPal uservoice page looks awesome and you can see that devs read these reports and they let you know wheter they will add something or fix it. Also it lets community decide which things should be dealth with first - by upvoting them.
The forms you mentioned seem quite inefficient to me (except the booting problems one - it's great) - you can only describe a bug or a problem, you can't attach any error files and the forms don't ask what camera, audio, bluetooth devices you have. What's important - after you send it, you will never get a notification about anything coming to life - you can only hope that the next OS release will include fixes you need.
I've spoken to few devs and they usually need logcats dmesg files and as much HW info as possible. This form is just too poor to provide nice information and a gazzilion of people can report the same thing.
Instead, I'd rather visit f.e remixos.uservoice.com search if someone has the same problem as me and then if I find it, I'd upvote it and maybe add a comment. In other case, I'd post a new "ticket" following specially written guidelines on how to report/suggest stuff.
To sum up, feedback needs:
1. Guidelines on how to report (error files, which apps to reproduce etc.)
2. Anti-redundancy filter - upvoting existing feedback reports
3. More direct contact with devs - by them replying to feedback when it's a major or very popular issue (then it's not a waste of dev team's time, because it's like replying to hundreds or thousands of people) and ITS PUBLIC.
4. After a new version of system is released, the devs should also point volunteer testers to what they should focus on in testing.
Trust me, this may seem like devs will have to focus on community instead of real work, but actually if this is better designed and more efficient, they will eventually spend way less time on it then they might now.
Also using Google Groups to get to the community is a mediocre measure in my opinion. I get that it's free, has google class stability and requires almost no time to maintain or set up, but it's hugely inefficient, chaotic and inconvenient.
Remember, I only want to help improve Remix, so I suggest what may be better. I'm on Jide's side, specially now when they have Android-x86 founder working with them.
Ventricle said:
Hi,
I'd like to get some very important info from Remix OS dev team.
Users unrelated to the dev team or with no android-x86 OS dev experience, please DO NOT attempt to answer these questions.
Could you please make a thorough guide on how to report bugs, suggestions, feature requests and hardware incompatibilites?
Which tools should we use to report bugs or hardware problems - be precise please. Current feedback form seems very modest and inefficient.
Except for bug description and device info should we provide a full logcat, dmesg, per-app logcat - please point out the most effective way to report this stuff.
Where should we post feature requests or suggestions?
I personally think, that e-mails or forum threads are really inefficient for this. I'd recommend using Uservoice service (https://uservoice.com) or something familiar . Example of uservoice usage in practice: https://touchpal.uservoice.com/ There are plenty of web services like these and they are very powerful and efficient.
Perhaps there is a web service that would help making an official list of supported hardware?
Remix OS, Android-x86 and Phoenix OS all base pretty much on the same ground here, so they could share same list, but none of these actually has a nice, neat tool to report supported hardware. Except for a list of officially supported devices, it's a total mess.
I know that ChromeOS with android apps support and upcoming Android releases may be groundbreaking for whole Android-x86 related projects, but if we mobilize ourselfs and use all resources efficiently, I'm pretty sure Remix OS can become very popular and liked. Devs - help us, users, help you achieve that.
Right now it seems like you don't really care about other devices compatibility or about what people may report. If you did, you would provide better tools for that in order to do your work more efficiently. Don't take it as offense, it's just cirtical point of view.
Please optimize that - this will help speed up the development process and community contact a ton.
Please reply Remix OS, Jide, @RemixOS_Cameron , @RemixOS_Guannan , @RemixOS_Jason , @RemixOS_Josh , @RemixOS_Joshua , @RemixOS_Valentina , @AmoraRei
Click to expand...
Click to collapse
Hey Ventricle,
Again, thanks for your comments on our communication channels. I've consolidated our feedback channels into their core functions and how one can access them. In short, we're constantly trying to improve so we'll take a step back and evaluate how this can be done better. As of now, here is the short guide on how to communicate with us most effectively:
Feedback/bugs channels
Remix OS for PC: Google form: https://docs.google.com/forms/d/e/1FAIpQLSeqaTBTPzHgjwUKtn08zUDusKTYXQtG8mLczmo7D6bDgd_17A/viewform
Remix Mini: Go to power options, select â??Report a problemâ?
Remix Ultratablet: Go to power options, select â??Report a problemâ?
Feature requests/suggestions
Help Center: http://support.jide.com/hc/en-us/requests/new
Official list of supported hardware
Remix OS for PC
Google group: https://groups.google.com/forum/#!forum/remix-os-for-pc
Thanks and I hope this helps,
Jason
Could we have a development road map somewhere please? I would like to know what the devs are working on and where we are heading. I would like to know what to expect in a future release. At least what's the plan in general terms. I feel it's a bit too quiet when we talk about future releases/versions/patches.
Still no improvement?
@RemixOS_Cameron , @RemixOS_Guannan , @RemixOS_Jason , @RemixOS_Josh , @RemixOS_Joshua , @RemixOS_Valentina , @AmoraRei
Still no improvement in how you gather feedback and still no guidelines for reporting issues and giving the feedback. Why is that? This is as important as education is for a country - no education means slow or no development.
If you invest just a little more effort and time into what I suggest, I guarantee you huge improvement in feedback value and that will result in faster development. Also this will truly involve users in the development and make them want to support the idea even more.
If you don't like the Uservoice methods then I suggest you making a seprate repository on GitHub called f.e Remix OS feature requests, Remix OS problem reports, Remix OS hardware incompatibilities etc.
In these repositories, people could make Issues that your actual devs could assign to future builds or at least they would acknowledge them - people would actually feel like devs really read their feedback!
This way, people would also be able to sign under existing issues instead of duplicating them. Just like here:
https://github.com/FortAwesome/Font-Awesome/issues/878
Look just how awesome this can be:
https://github.com/FortAwesome/Font-Awesome/issues
I honestly can't understand why you neglect this part of Remix OS.
It's beyond my imagination how a company like this uses such inefficient feedback tools.
I know you use Zendesk for feature requests, but doesn't it have an option to make requests public? It'd avoid duplication of requests. Maybe it's possible to view all reports; both feature requests and problem reports? But users just don't know about it?
It could be so much better with the tools I mentioned. Come on... use them!
Please reply and let me know what you think of my suggestions.
dag u done tagged everybody ?. I see u and I forward ur message.
Ventricle said:
@RemixOS_Cameron , @RemixOS_Guannan , @RemixOS_Jason , @RemixOS_Josh , @RemixOS_Joshua , @RemixOS_Valentina , @AmoraRei
Still no improvement in how you gather feedback and still no guidelines for reporting issues and giving the feedback. Why is that? This is as important as education is for a country - no education means slow or no development.
If you invest just a little more effort and time into what I suggest, I guarantee you huge improvement in feedback value and that will result in faster development. Also this will truly involve users in the development and make them want to support the idea even more.
If you don't like the Uservoice methods then I suggest you making a seprate repository on GitHub called f.e Remix OS feature requests, Remix OS problem reports, Remix OS hardware incompatibilities etc.
In these repositories, people could make Issues that your actual devs could assign to future builds or at least they would acknowledge them - people would actually feel like devs really read their feedback!
This way, people would also be able to sign under existing issues instead of duplicating them. Just like here:
https://github.com/FortAwesome/Font-Awesome/issues/878
Look just how awesome this can be:
https://github.com/FortAwesome/Font-Awesome/issues
I honestly can't understand why you neglect this part of Remix OS.
It's beyond my imagination how a company like this uses such inefficient feedback tools.
I know you use Zendesk for feature requests, but doesn't it have an option to make requests public? It'd avoid duplication of requests. Maybe it's possible to view all reports; both feature requests and problem reports? But users just don't know about it?
It could be so much better with the tools I mentioned. Come on... use them!
Please reply and let me know what you think of my suggestions.
Click to expand...
Click to collapse
@Ventricle - After receiving your message, I shared your suggestions with our PMs, engineering team and customer support. Long story short is, they are trying to work out the feasibility, the timing and the execution of your suggestions. Although I cannot confirm at this time if and when these changes will be made, I can tell you that it's not something they haven't thought of. It does come down to the internal planning, human resource allocation and execution. Thus, please give me a few days to reply to you about your suggestions. Thanks again for pushing us to improve!
Jason
Sure thing @RemixOS_Jason ,I understand it completely. Just you saying that gives the community the sense that improvements are coming.
I'm looking forward to your follow up on this issue.
Some high hopes there!
Cheers,
Karol
UPDATE:
Got a very informative and valuable quote from @RemixOS_Jason here:
RemixOS_Jason said:
@alz_uk - Wow! It's pretty clear you have it in your mind that we are quite an evil, greedy company! Not sure if I can make a dent in your opinion, but I thought it prudent to give you a transparent answer:
As @Vioner and other users have pointed out to us, they'd like to see a different user feedback system. However, we designed it because we in the International (meaning outside of China) PR, marketing and customer support team is two full time staff and 2 part time interns. This means that our resources are limited.
Thus, the way the system is currently designed is for us to:
1) gather feedback - this is what this form is for: https://docs.google.com/forms/d/1cZNesOmnmO2esilFpvMzFZ874rvwsiKgWIX2fo9QsDk/viewform
2) organize the feedback regularly - once a week, my colleague organizes all the feedback into topics and sections and prioritizes them based on volume of reported bugs, issues, and compatibility with specific devices. This includes issues like the audio over HDMI, black screen, Wi-Fi, Bluetooth, gaming, app specific, etc. Device specific is numerous, but consider this: currently we support roughly 65% of the PCs out in the wild. This means that there will be 35% of the PCs that just don't work for one reason or another yet. That also means that for every person with a PC that doesn't work, there are around 2 people whose PC does work. With a small dedicated engineering staff as well, we try to tackle these issues from a platform point of view. Thus, you've seen in some updates the fact that we worked on GPUs that were vendor or brand specific, rather than only tackle one specific set of hardware components in a reported device. This is where the feedback form helps us to gather data so that we focus on fixing the issues that affect the widest range of users first.
3) send the feedback to the engineers - when it reaches the devs, they tweak our prioritization order based on what's feasible and what's not in the short and long term. Thus, you can be certain that we know about outstanding audio issues (we all dogfood our prodcuts and so, there are colleagues who's Remix OS for PC machines also don't have audio coming out). However, if we haven't update with this fix, you can be certain that whatever we've tried haven't passed testing, or is in the process of testing. Thus, there are two layers of what we do with feedback: count them, and then see which ones we can actually fix.
4) The fixes we do come up with must pass internal and external testing.
5) If they do pass, they are put into updates.
The installer issue was pretty simple. Most 3rd party installer do work, but as we gathered feedback from back in Remix OS for PC based Lollipop, our product manager noticed a trend where some of the OTA issues were due to 3rd Party installers. Thus, we put out the message that we couldn't promise that 3rd party installers would work 100% to support future OTAs.
Releasing fixes take time because they need to be tested. If a fix worked for some, but might cause issues for others, we don't release that fix for a stable release. Let's take the black screen issue during installation as a case example. We gathered around 65 users' emails who had this issue during installation. When we had a fix, we sent out emails and a testing ROM just for these folks with the potential fix. After around a week, most reported that their issue was fixed and that they didn't experience any other significant issues after being able to boot Remix OS (outside of some minor app compatibility issues). Thus, after a few more days of testing internally in parallel with this tester group, we rolled into that update. If you didn't see the fix applied in an update yet, it's probably because it didn't pass testing internally, or with their related testers, meaning though some folks' issues got fixed, many did not, or it caused other significant issues.
With limited resources, we do tackle issues from a platform (CPU, GPU, broadcom wireless chip, etc.) and not focus on your device, or his device or her device specific. We also work with the patches that are given out by the Android-x86 team (of which their founder, Chih-Wei Huang actually is our tech lead on Remix OS for PC) as can be evident by the update that integrated their latest release (rc2). In fact, we are small enough as a startup that we welcome our user developers assistance. So much so that I'm trying to work on making GitHub a place where interested developers can work on projects with us (where applicable since most of Remix OS is closed source). This is how much we actually need your development help!
In the end, I beg you to consider that people in general post 4-7 times more likely if they have outstanding issues, and not because we fixed any of their issues. Thus (and I know this all too well as the manager of our forums here) it can seem like everything is terrible, that Remix OS for PC just doesn't work for anyone and that no improvement has ever been made, ever. However, I just need to remember that for every 1 person with an issue that we're still trying to resolve, there are many more where the fixes we've implemented have made a difference.
As a startup, having the amount of users we have is a blessing. As a startup, having the amount of users we have with the limited resources, I mean engineers and folks like myself who communicate with the community, has been challenging. But, I ask that instead of giving up on us or spiting us for being a "mind game" playing, evil, greedy company, that you work with us to make a difference.
It wasn't that long ago that we had users who called us out on forums and tell we needed to improve our feedback system, and they're right. I'm working on improving it to offer more transparency into the process without increasing our workload to the point where it's not sustainable. Those same users who called us out are now working with us to improve through our Ambassador program. So, the challenge is, can you help us rather than just spite us? Running a startup in the industry we're in isn't easy, but it's something we're passionate about. Clearly we can still get better. Please help us.
Thanks,
Jason Zheng
Head of International PR, and Community Management at Jide Technology
I'm also frequently on our Facebook page and Twitter page
Click to expand...
Click to collapse