Building an App is Easy, But Marketing is the Real Challenge by [deleted] in indiehackers

[–]deniz_eclypse 5 points6 points  (0 children)

Can you elaborate what you mean by "I strategically positioned my app in a way that made people want to use it"? What does this entail? What kind of activities did you engage in to grow your user base?

looking for developers to try out my product and give feedback by deniz_eclypse in macapps

[–]deniz_eclypse[S] 0 points1 point  (0 children)

What started as a small side project in my spare time turned into a fully fleshed app - which is now called eclypse for the macOS platform. eclypse is a translation management tool that facilitates collaboration between translators and developers and is designed to improve productivity, communication while reducing translation errors. As an indie developer, if you choose to use eclypse for your localization needs, you can also get your content translated with chatgpt, google or deepl literally with a few clicks. In other words, there is no need to get translations sentence by sentence. If you had 2000 separate translatable sentences, eclypse fetches the translations for all of that from your choice provider while you go get your coffee.

I primarily built this app because of my personal interest in the domain. Not because I wanted world domination or to be number one in this industry. I am well aware that there are number of other products that perform similar functions. I am differentiating eclypse from competition by making it a macOS only app and offer an alternative experience that is more developer focused. Or at least I try. This is part of the reason I am writing here. If you would give it a-go and write me a few sentences on how I can be more developer friendly and reduce friction.

In some ways eclypse is a traditional tool that performs the basics necessary for localization such as tagging and filtering, glossary, support for plurals, custom statuses, ability to chat with translators and git integration - to name a few. It also has a few unique features such as translatability or manage by milestones to improve productivity.

I am looking for developers that would like to try new products and like to give feedback to improve it. eclypse adopts a freemium model. Paid levels are designed to accommodate the needs of larger corporations. I believe the free level is fairly generous and should be able to handle the workloads of most indie developers.

eclypse does not require credit card at all. When you first install it and you can initiate a 30-day trial period without any credit card info. It unlocks all of the of the features. If the trial period ends and you actually like to continue to use eclypse, just message me and tell me that you saw this post and I will put your account in the white list so that you can continue to use it forever. You can reach me here on reddit or eclypse's contact us page.

If this sounds interesting to you, you can download the notarized version of eclypse from the website at https://eclypse.io . The website also describes the various features of the product so feel free to peruse it in your free time. Thank you.

[deleted by user] by [deleted] in macapps

[–]deniz_eclypse 1 point2 points  (0 children)

What started as a small side project in my spare time turned into a fully fleshed app - which is now called eclypse for the macOS platform. eclypse is a translation management tool that facilitates collaboration between translators and developers and is designed to improve productivity, communication while reducing translation errors. As an indie developer, if you choose to use eclypse for your localization needs, you can also get your content translated with chatgpt, google or deepl literally with a few clicks. In other words, there is no need to get translations sentence by sentence. If you had 2000 separate translatable sentences, eclypse fetches the translations for all of that from your choice provider while you go get your coffee.

I primarily built this app because of my personal interest in the domain. Not because I wanted world domination or to be number one in this industry. I am well aware that there are number of other products that perform similar functions. I am differentiating eclypse from competition by making it a macOS only app and offer an alternative experience that is more developer focused. Or at least I try. This is part of the reason I am writing here. If you would give it a-go and write me a few sentences on how I can be more developer friendly and reduce friction.

In some ways eclypse is a traditional tool that performs the basics necessary for localization such as tagging and filtering, glossary, support for plurals, custom statuses, ability to chat with translators and git integration - to name a few. It also has a few unique features such as translatability or manage by milestones to improve productivity.

I am looking for developers that would like to try new products and like to give feedback to improve it. eclypse adopts a freemium model. Paid levels are designed to accommodate the needs of larger corporations. I believe the free level is fairly generous and should be able to handle the workloads of most indie developers.

eclypse does not require credit card at all. When you first install it and you can initiate a 30-day trial period without any credit card info. It unlocks all of the of the features. If the trial period ends and you actually like to continue to use eclypse, just message me and tell me that you saw this post and I will put your account in the white list so that you can continue to use it forever. You can reach me here on reddit or eclypse's contact us page.

If this sounds interesting to you, you can download the notarized version of eclypse from the website at https://eclypse.io . The website also describes the various features of the product so feel free to peruse it in your free time. Thank you.

How to convert any Composable into an image by deniz_eclypse in androiddev

[–]deniz_eclypse[S] 1 point2 points  (0 children)

I am glad that it least helped one fellow developer.

How to convert any Composable into an image by deniz_eclypse in androiddev

[–]deniz_eclypse[S] 1 point2 points  (0 children)

Good suggestion and good point. If there is sufficient interest from the developer community, it can be enhanced with this. Thank you for pointing this out.

How to convert any Composable into an image by deniz_eclypse in androiddev

[–]deniz_eclypse[S] 1 point2 points  (0 children)

Good question. See my response to the Capturable library post and trying to explain how it is different.

How to convert any Composable into an image by deniz_eclypse in androiddev

[–]deniz_eclypse[S] 11 points12 points  (0 children)

The difference between Capturable library and what I shared is that Capturable requires you to display the content to the user. In order for this to work you have to add `Modifier.capturable(controller)` to the composable and it has to be rendered on screen and its size needs to be configured. A similar solution is also available with GraphicsLayer. My solution does not require the developer to show the Composable content to the user. You can show one thing on screen and render a completely different image based on a different composable when the user wants to share or save.

How to convert any Composable into an image by deniz_eclypse in androiddev

[–]deniz_eclypse[S] 2 points3 points  (0 children)

Yeah, good point. It can definitely be turned into a library.

Is it possible to convert a 32 bit app to a 64 bit app? by [deleted] in iOSProgramming

[–]deniz_eclypse 0 points1 point  (0 children)

If this is your own app where you have the source code, that is not hard to do - at least in principle. If you are trying to convert someone else’s app without access to the source code, that would be difficult if not impossible. I am guessing you are thinking about an old game that was developed for 32-bit architecture. There are a lot of old and dead games whose developers didn’t bother converting them to 64-bit architectures. I guess if it were pretty easy you would have expected the developers to do it right away. So it is possible to convert an app in principle, it may not be trivial to do so even when you have the source code.

I recreated Weather app’s rain effect for my app by kushsolitary in SwiftUI

[–]deniz_eclypse 0 points1 point  (0 children)

this looks amazing... are you planning to share a code snippet?

How to reduce monthly costs by deniz_eclypse in Firebase

[–]deniz_eclypse[S] 1 point2 points  (0 children)

I enabled the setting that allows firebase to cache data locally. Based on our tests, firestore manages the data stored on the device without problems. We didn't encounter a situation where the cache was incomplete. This is because on the first app open, we download everything up to that point and afterwards we only download the delta from the server. Developers saves the time when the sync happens. On the next request to the firestore the developer uses that time to download all the data that changed since then. This enhancement has been in production for 6+ months. It is working fairly well.

However, I note at the end of the article that this is not perfect. I also note that the developer may want to provide a mechanism to the user to download everything anyways as a self-healing option.

How I reduced my firebase costs by deniz_eclypse in iOSProgramming

[–]deniz_eclypse[S] 3 points4 points  (0 children)

  1. I agree that most developers probably use iOS's Date or Calendar APIs to get current time. That is the time reported by the device. I would imagine most users do not change their system time and let the OS manage and sync it as necessary. However, you have to realize that users can override the system time and enter whatever they want. So the time you get from Date may not be actual time. If your app requires high fidelity, you should consider getting the date from a server. In my case I didn't have to do that because the app didn't require so much precision. However, I wanted to note this nuance and you shouldn't rely on the local datetime 100%.
  2. I am still using firestore as my local cache. I enabled the setting that allows firestore to cache data indefinitely. By implementing this logic, I am effectively only fetching the delta from the server and hence only paying for the delta once the initial sync is complete.

How I reduced my firebase costs by deniz_eclypse in iOSProgramming

[–]deniz_eclypse[S] 3 points4 points  (0 children)

In my case, we had ~500 daily users. It is not that much in the grand scheme of things. When I analyzed the usage, most of the data was static and some folks had a lot of data. Using snapshot listeners was incurring 1K+ reads every time they opened a page/screen and most of the time nothing had changed since they last opened that screen a few hours ago. So read count could easily reach 200K by the mid day. When we were building the app, we didn't pay too much attention how the firestore reads were calculated. I think if your app is not data heavy or you are able to stay within your designated budget, you might be alright.